Date: Tue, 27 Aug 2019 10:10:52 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: maksim yevmenkin <maksim.yevmenkin@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, Hans Petter Selasky <hps@selasky.org>, "mms.vanbreukelingen@gmail.com" <mms.vanbreukelingen@gmail.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Kernel-Crash when working with ubt0 Message-ID: <20190827071052.GT71821@kib.kiev.ua> In-Reply-To: <00E772F0-7231-44C4-B314-26730CC7DF21@gmail.com> References: <47509401.1440476.1566796167857.ref@mail.yahoo.com> <47509401.1440476.1566796167857@mail.yahoo.com> <5aa8faeb-5e8e-38be-4301-81f3d82c494a@selasky.org> <CANCZdfpJARVFz%2BCyvbAK9sH4E6__DPAunYQz5rxexO-mzuvsuw@mail.gmail.com> <00E772F0-7231-44C4-B314-26730CC7DF21@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 26, 2019 at 02:35:25PM -0700, maksim yevmenkin wrote: > > > > On Aug 26, 2019, at 9:14 AM, Warner Losh <imp@bsdimp.com> wrote: > > > > Is it from read_connection_list? If so I have a 'patch' that I'm using but > > haven't committed because it's just too gross: drop the lock before the > > copyout and pick it up again after... > > > > Hmm... interesting.... > > I only took a brief look at it. I suppose I can ensure user space address is wired and then copyout() can be called with mutex held No, you cannot do this, at least without making the kernel to panic. User might unmap the wired mapping at any time still. > > It’s odd that I’ve never seen this before. I’m traveling at the moment will take a closer look this later this week > > Thanks > Max > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190827071052.GT71821>