All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	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>
Subject: Re: INFO: rcu detected stall in corrupted (3)
Date: Mon, 1 Apr 2019 08:42:08 +0200	[thread overview]
Message-ID: <20190401064208.GH29508@localhost.localdomain> (raw)
In-Reply-To: <20190330110933.GC5935@zn.tnic>

Hi,

On 30/03/19 12:09, Borislav Petkov wrote:
> On Sat, Mar 30, 2019 at 07:57:50PM +0900, Tetsuo Handa wrote:
> > Yes. But what such threshold be? 0.1 second? 1 second? 10 seconds?
> > Can we find a threshold where everyone can agree on?
> 
> This is what we do all day on lkml: discussing changes so that (almost)
> everyone is happy with them.

Looks like this is the same problem we discussed a while ago [1], but
couldn't reach an agreement on what's best to do about it.

I'll need to go back and refresh memory.

Thanks,

- Juri

1 - https://lore.kernel.org/lkml/000000000000a4ee200578172fde@google.com/

      parent reply	other threads:[~2019-04-01  6:42 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
2019-04-01  6:42             ` Juri Lelli [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=20190401064208.GH29508@localhost.localdomain \
    --to=juri.lelli@redhat.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.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.