All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	syzbot <syzbot+65cecdd27b726c261799@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com, "H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@kernel.org>,
	mingo@redhat.com, x86@kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>
Subject: Re: INFO: rcu detected stall in corrupted (3)
Date: Sat, 30 Mar 2019 20:05:48 +0100	[thread overview]
Message-ID: <20190330190548.GG5935@zn.tnic> (raw)
In-Reply-To: <18f27e51-a1b2-cb17-c415-31ace2f56dc6@i-love.sakura.ne.jp>

On Sat, Mar 30, 2019 at 11:07:40PM +0900, Tetsuo Handa wrote:
> I think that syzbot should for now refrain from testing syscalls that change
> scheduling related attributes,

And how would we know about problems there, otherwise?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2019-03-30 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 22:34 INFO: rcu detected stall in corrupted (3) syzbot
2019-03-30  0:13 ` Tetsuo Handa
2019-03-30  7:46   ` Thomas Gleixner
2019-03-30 10:40     ` Tetsuo Handa
2019-03-30 10:45       ` Borislav Petkov
2019-03-30 10:57         ` Tetsuo Handa
2019-03-30 11:09           ` Borislav Petkov
2019-03-30 14:07             ` Tetsuo Handa
2019-03-30 19:05               ` Borislav Petkov [this message]
2019-04-01  6:42             ` Juri Lelli

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=20190330190548.GG5935@zn.tnic \
    --to=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.org \
    --cc=syzbot+65cecdd27b726c261799@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.