Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Dec 2020 10:48:29 -0500
From:      Mark Johnston <markj@freebsd.org>
To:        Kyle Evans <kevans@freebsd.org>
Cc:        Peter Holm <pho@freebsd.org>, current <current@freebsd.org>
Subject:   Re: panic: general protection fault from uipc_sockaddr+0x4c
Message-ID:  <X8%2BgTfsqOCxld3yl@raichu>
In-Reply-To: <CACNAnaG_8iSUqc3pnmV-DMFQ_%2BQ%2BbSDbYA8X3pz743rRGUtT9A@mail.gmail.com>
References:  <20201208114718.GA33199@x8.osted.lan> <X8%2BcIUFKzzOSnl4L@raichu> <CACNAnaG_8iSUqc3pnmV-DMFQ_%2BQ%2BbSDbYA8X3pz743rRGUtT9A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 08, 2020 at 09:39:05AM -0600, Kyle Evans wrote:
> On Tue, Dec 8, 2020 at 9:30 AM Mark Johnston <markj@freebsd.org> wrote:
> > kern_proc_filedesc_out() holds the fdtable shared lock thoughout all of
> > this, which is supposed to prevent the table entry from being freed
> > since that requires the exclusive lock.
> >
> 
> export_file_to_sb drops the lock without it or kern_proc_filedesc_out
> holding the file it's about to look at, though.

Yes, but that's after it calls fo_fill_kinfo().  At that point it has
already collected the to-be-exported info in an sbuf.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X8%2BgTfsqOCxld3yl>