linux-kernel - Re: INFO: task hung in path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <Yd2IVM1q2Mmck3fJ@casper.infradead.org>
Date:   Tue, 11 Jan 2022 13:38:28 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Aleksandr Nogikh <nogikh@...gle.com>
Cc:     cruise k <cruise4k@...il.com>, Dmitry Vyukov <dvyukov@...gle.com>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        sunhao.th@...il.com, syzkaller <syzkaller@...glegroups.com>
Subject: Re: INFO: task hung in path_openat

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?