From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Liam Howlett <liam.howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Christian Brauner <brauner@kernel.org>,
syzbot <syzbot+7170d66493145b71afd4@syzkaller.appspotmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Subject: Re: [syzbot] KASAN: use-after-free Read in mas_next_nentry
Date: Thu, 28 Apr 2022 09:23:40 +0300 [thread overview]
Message-ID: <20220428062340.GT2462@kadam> (raw)
In-Reply-To: <CACT4Y+bCyji6yxtOgJg05pkiNnqUAptW4Qdc5EAZW9uCUfjwCw@mail.gmail.com>
On Wed, Apr 27, 2022 at 05:22:31PM +0200, 'Dmitry Vyukov' via syzkaller-bugs wrote:
> On Wed, 27 Apr 2022 at 17:17, Liam Howlett <liam.howlett@oracle.com> wrote:
> >
> > * Matthew Wilcox <willy@infradead.org> [220427 10:58]:
> > > On Wed, Apr 27, 2022 at 02:55:58PM +0200, Christian Brauner wrote:
> > > > [+Cc Willy]
> > >
> > > I read fsdevel. Not sure Liam does though.
> >
> > I do not. Thank you for sending it along.
> >
> > Here is a patch that should fix the issue. I will ask AKPM to include
> > it for tomorrow.
>
> Please add the reported tag:
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+7170d66493145b71afd4@syzkaller.appspotmail.com
>
And a Fixes tag as well.
regards,
dan carpenter
next prev parent reply other threads:[~2022-04-28 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 12:43 [syzbot] KASAN: use-after-free Read in mas_next_nentry syzbot
2022-04-27 12:55 ` Christian Brauner
2022-04-27 14:58 ` Matthew Wilcox
2022-04-27 15:17 ` Liam Howlett
2022-04-27 15:22 ` Dmitry Vyukov
2022-04-28 6:23 ` Dan Carpenter [this message]
2023-01-25 22:04 ` syzbot
2023-01-26 13:14 ` Liam R. Howlett
2023-01-27 7:09 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220428062340.GT2462@kadam \
--to=dan.carpenter@oracle.com \
--cc=brauner@kernel.org \
--cc=dvyukov@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+7170d66493145b71afd4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox