[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d0b24d6d5dd15d80be5b1dcd724560bc5a016c08.camel@kernel.org>
Date: Fri, 21 Jul 2023 08:11:10 -0400
From: Jeff Layton <jlayton@...nel.org>
To: Will Shiu <Will.Shiu@...iatek.com>,
Chuck Lever <chuck.lever@...cle.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] Fix BUG: KASAN: use-after-free in
trace_event_raw_event_filelock_lock
On Fri, 2023-07-21 at 06:34 -0400, Jeff Layton wrote:
>
> Could you send along the entire KASAN log message? I'm not sure I see
> how this is being tripped. The lock we're passing in here is "request"
> and that shouldn't be freed since it's allocated and owned by the
> caller.
>
Nevermind. I see how this could happen, and have gone ahead and merged
the patch. It should make v6.6.
Cheers,
--
Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists