From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+bcad772bbc241b4c6147@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
James Morris <jmorris@namei.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: INFO: rcu detected stall in sys_sendfile64
Date: Sat, 4 Jan 2020 20:09:00 +0900 [thread overview]
Message-ID: <bc53fe0b-2c17-4d4f-1c40-f290997d0521@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CACT4Y+YqWgZZFXdX2A2jVYEdHfY9ywGMgRRP5W4Uqdu__rA63g@mail.gmail.com>
On 2018/12/20 3:42, Dmitry Vyukov wrote:
> On Wed, Dec 19, 2018 at 11:13 AM Tetsuo Handa
> <penguin-kernel@i-love.sakura.ne.jp> wrote:
>>
>> On 2018/12/19 18:27, syzbot wrote:
>>> HEAD commit: ddfbab46539f Merge tag 'scsi-fixes' of git://git.kernel.or..
>>> git tree: upstream
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=15b87fa3400000
>>> kernel config: https://syzkaller.appspot.com/x/.config?x=861a3573f4e78ba1
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=bcad772bbc241b4c6147
>>> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13912ccd400000
>>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145781db400000
>>
>> This is not a LSM problem, for the reproducer is calling
>> sched_setattr(SCHED_DEADLINE) with very large values.
>>
>> sched_setattr(0, {size=0, sched_policy=0x6 /* SCHED_??? */, sched_flags=0, sched_nice=0, sched_priority=0, sched_runtime=2251799813724439, sched_deadline=4611686018427453437, sched_period=0}, 0) = 0
>>
>> I think that this problem is nothing but an insane sched_setattr() parameter.
>>
>> #syz invalid
>
> Note there was another one with sched_setattr, which turned out to be
> some serious problem in kernel (sched_setattr should not cause CPU
> stall for 3 minutes):
> INFO: rcu detected stall in do_idle
> https://syzkaller.appspot.com/bug?extid=385468161961cee80c31
> https://groups.google.com/forum/#!msg/syzkaller-bugs/crrfvusGtwI/IoD_zus4BgAJ
>
> Maybe it another incarnation of the same bug, that one is still not fixed.
>
Can we let syzbot blacklist sched_setattr() for now? There are many stall reports
doing sched_setattr(SCHED_RR) which makes it difficult to find stall reports not
using sched_setattr().
next prev parent reply other threads:[~2020-01-04 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 9:27 INFO: rcu detected stall in sys_sendfile64 syzbot
2018-12-19 10:11 ` Tetsuo Handa
2018-12-19 18:42 ` Dmitry Vyukov
2020-01-04 11:09 ` Tetsuo Handa [this message]
2020-01-07 13:02 ` Dmitry Vyukov
2020-01-07 13:11 ` Peter Zijlstra
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=bc53fe0b-2c17-4d4f-1c40-f290997d0521@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=dvyukov@google.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=serge@hallyn.com \
--cc=syzbot+bcad772bbc241b4c6147@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).