From: Matthew Wilcox <willy@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Wei Chen <harperchen1110@gmail.com>,
rpeterso@redhat.com, agruenba@redhat.com,
cluster-devel@redhat.com, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, syzkaller@googlegroups.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in gfs2_evict_inode
Date: Tue, 22 Nov 2022 06:03:53 +0000 [thread overview]
Message-ID: <Y3xmSbsjoMRnRIEd@casper.infradead.org> (raw)
In-Reply-To: <CACT4Y+Zub=+V3Yx=wSagYYeybwhbBt66COyTc=OjFAMOibybxg@mail.gmail.com>
On Fri, Nov 18, 2022 at 10:33:21AM +0100, Dmitry Vyukov wrote:
> On Fri, 18 Nov 2022 at 09:06, Wei Chen <harperchen1110@gmail.com> wrote:
> >
> > Dear Linux developers,
> >
> > The bug persists in upstream Linux v6.0-rc5.
>
> If you fix this, please also add the syzbot tag:
>
> Reported-by: syzbot+8a5fc6416c175cecea34@syzkaller.appspotmail.com
> https://lore.kernel.org/all/000000000000ab092305e268a016@google.com/
Hey Dmitri, does Wei Chen work with you? They're not responding to
requests to understand what they're doing. eg:
https://lore.kernel.org/all/YtVhVKPAfzGmHu95@casper.infradead.org/
https://lore.kernel.org/all/Y0SAT5grkUmUW045@casper.infradead.org/
I'm just ignoring their reports now.
next prev parent reply other threads:[~2022-11-22 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO4mrfd4=HRXMrcdZQUorNaFss3AFfrRxuXWMFT3uh+Dvfwb9g@mail.gmail.com>
[not found] ` <CAO4mrfdU4oGktM8PPFg66=32N0JSGx=gtG80S89-b66tS3NLVw@mail.gmail.com>
2022-11-18 8:05 ` BUG: unable to handle kernel NULL pointer dereference in gfs2_evict_inode Wei Chen
2022-11-18 9:33 ` Dmitry Vyukov
2022-11-22 6:03 ` Matthew Wilcox [this message]
2022-11-22 7:12 ` 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=Y3xmSbsjoMRnRIEd@casper.infradead.org \
--to=willy@infradead.org \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=dvyukov@google.com \
--cc=harperchen1110@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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