From: Matthew Wilcox <willy@infradead.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: cruise k <cruise4k@gmail.com>, Dmitry Vyukov <dvyukov@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
sunhao.th@gmail.com, syzkaller <syzkaller@googlegroups.com>
Subject: Re: INFO: task hung in path_openat
Date: Tue, 11 Jan 2022 13:38:28 +0000 [thread overview]
Message-ID: <Yd2IVM1q2Mmck3fJ@casper.infradead.org> (raw)
In-Reply-To: <CANp29Y5tjwYLk3WdfjmsQy3qXbk6V8vW1vERRSTHsAhpzzMGpg@mail.gmail.com>
On Tue, Jan 11, 2022 at 10:38:02AM +0100, Aleksandr Nogikh wrote:
> Hi Matthew,
>
> That report was not sent by syzbot, rather by someone else. syzbot tries to
> be much more careful with the INFO: reports.
>
> During the past couple of weeks there has been some outburst of similar
> reports from various senders - this is the third different sender I see,
> probably there are also much more.
Right. Perhaps syzcaller could *not* call sched_setscheduler() by
default. Require an --i-know-what-im-doing-and-wont-submit-bogus-reports
flag to be specified by the user in order to call that syscall?
next prev parent reply other threads:[~2022-01-11 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 2:15 INFO: task hung in path_openat cruise k
2022-01-11 3:39 ` Matthew Wilcox
[not found] ` <CANp29Y5tjwYLk3WdfjmsQy3qXbk6V8vW1vERRSTHsAhpzzMGpg@mail.gmail.com>
2022-01-11 13:38 ` Matthew Wilcox [this message]
2022-01-11 13:29 ` KCSAN: data-race in step_into / vfs_unlink Kaia Yadira
2022-01-11 14:10 ` KCSAN: data-race in task_mem / unmap_region Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2022-01-11 13:56 Kaia Yadira
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=Yd2IVM1q2Mmck3fJ@casper.infradead.org \
--to=willy@infradead.org \
--cc=cruise4k@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=sunhao.th@gmail.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;
as well as URLs for NNTP newsgroup(s).