[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <12dca9308e5b37f5686267148ad874084610c04e.camel@mediatek.com>
Date: Thu, 27 Jul 2023 02:15:04 +0000
From: Will Shiu (許恭瑜) <Will.Shiu@...iatek.com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
"chuck.lever@...cle.com" <chuck.lever@...cle.com>,
"jlayton@...nel.org" <jlayton@...nel.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"brauner@...nel.org" <brauner@...nel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
"angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH] Fix BUG: KASAN: use-after-free in
trace_event_raw_event_filelock_lock
On Fri, 2023-07-21 at 08:11 -0400, Jeff Layton wrote:
>
> 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>
Dear Jeff,
Really thanks for your reply. we'd want to know could the patch we
delivered, which moves ftrace function ahead the removing APIs, be the
finial patch and will submit in k6.6. If yes, we would try to ask
google owner to patch back the patch in k6.1. Or is there any advice to
show us how to fix it. Thanks again.
Best Regards,
Will Shiu
Powered by blists - more mailing lists