From: Matthew Wilcox <willy@infradead.org>
To: "Gong, Sishuai" <sishuai@purdue.edu>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: PROBLEM: potential concurrency bug between do_vfs_ioctl() and do_readv()
Date: Wed, 2 Dec 2020 04:02:00 +0000 [thread overview]
Message-ID: <20201202040200.GE11935@casper.infradead.org> (raw)
In-Reply-To: <DFE6D155-3123-488D-B6E3-02E8757A7585@purdue.edu>
On Wed, Dec 02, 2020 at 03:18:26AM +0000, Gong, Sishuai wrote:
> We want to report another error message we saw which might be related to this bug.
https://syzkaller.appspot.com/upstream
There are over a thousand open bugs already. Why are the extra bugs
being found by your group useful?
prev parent reply other threads:[~2020-12-02 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 14:44 PROBLEM: potential concurrency bug between do_vfs_ioctl() and do_readv() Gong, Sishuai
2020-12-02 3:18 ` Gong, Sishuai
2020-12-02 4:02 ` Matthew Wilcox [this message]
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=20201202040200.GE11935@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sishuai@purdue.edu \
/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;
as well as URLs for NNTP newsgroup(s).