From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Petr Mladek <pmladek@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [syzbot? printk?] no WARN_ON() messages printed before "Kernel panic - not syncing: panic_on_warn set ..."
Date: Thu, 9 May 2019 19:18:30 +0900 [thread overview]
Message-ID: <20190509101830.GB23572@jagdpanzerIV> (raw)
In-Reply-To: <20190509095823.GA23572@jagdpanzerIV>
On (05/09/19 18:58), Sergey Senozhatsky wrote:
> On (05/08/19 19:31), Tetsuo Handa wrote:
> [..]
> > We are again getting corrupted reports where message from WARN() is missing.
> > For example, https://syzkaller.appspot.com/text?tag=CrashLog&x=1720cac8a00000 was
> > titled as "WARNING in cgroup_exit" because the
> > "WARNING: CPU: 0 PID: 7870 at kernel/cgroup/cgroup.c:6008 cgroup_exit+0x51a/0x5d0"
> > line is there but https://syzkaller.appspot.com/text?tag=CrashLog&x=1670a602a00000
> > was titled as "corrupted report (2)" because the
> > "WARNING: CPU: 0 PID: 10223 at kernel/cgroup/cgroup.c:6008 cgroup_exit+0x51a/0x5d0"
> > line is missing. Also, it is unlikely that there was no printk() for a few minutes.
> > Thus, I suspect something is again suppressing console output.
>
> Hmm... That's interesting...
What are these lines right before the kernel panic output?
TTY writes (user space logging)?
03:54:05 executing program 5:
syz_mount_image$xfs(&(0x7f0000000000)='xfs\x00', &(0x7f0000000040)='./file0\x00', 0x0, 0x0, 0x0, 0xe003, &(0x7f00000005c0)={[{@nolargeio='nolargeio'}]})
03:54:06 executing program 2:
syz_emit_ethernet(0x66, &(0x7f0000000080)={@local, @random="029cce98941b", [], {@ipv6={0x86dd, {0x0, 0x6, 'v`Q', 0x30, 0x3a, 0xffffffffffffffff, @remote={0xfe, 0x80, [0x29c, 0x0, 0x700, 0x5], 0xffffffffffffffff}, @mcast2={0xff, 0x2, [0x0, 0xfffffffffffff000]}, {[], @icmpv6=@dest_unreach={0xffffff86, 0x0, 0x0, 0x0, [0x7], {0x0, 0x6, "c5961e", 0x0, 0x0, 0x0, @mcast1={0xff, 0x1, [0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x3, 0x3, 0x0, 0x0, 0x8906], 0x8200}, @mcast2}}}}}}}, 0x0)
[ 2396.035331][T10223] Kernel panic - not syncing: panic_on_warn set ...
[ 2396.042217][T10223] CPU: 0 PID: 10223 Comm: syz-executor.1 Not tainted 5.1.0-next-20190507 #2
Hmm... Dunno... Don't really have any explanations yet...
Can you add
if (oops_in_progress)
return IRQ_HANDLED;
to you console driver's IRQ handler (xmit TX/RX path)? Just to
check if this will change anything...
-ss
next prev parent reply other threads:[~2019-05-09 10:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 2:09 [syzbot? printk?] no WARN_ON() messages printed before "Kernel panic - not syncing: panic_on_warn set ..." Tetsuo Handa
2019-03-16 9:11 ` Dmitry Vyukov
2019-03-16 10:18 ` Tetsuo Handa
2019-03-16 14:14 ` Sergey Senozhatsky
2019-03-16 14:16 ` Dmitry Vyukov
2019-03-16 14:40 ` Sergey Senozhatsky
2019-03-16 14:53 ` Tetsuo Handa
2019-03-16 14:57 ` Dmitry Vyukov
2019-03-16 15:02 ` Tetsuo Handa
2019-03-16 15:10 ` Dmitry Vyukov
2019-03-18 5:27 ` Tetsuo Handa
2019-03-18 12:07 ` Dmitry Vyukov
2019-03-18 12:32 ` Dmitry Vyukov
2019-03-18 12:39 ` Dmitry Vyukov
2019-03-19 0:41 ` Tetsuo Handa
2019-03-18 12:50 ` Sergey Senozhatsky
2019-03-18 13:42 ` Dmitry Vyukov
2019-03-18 14:09 ` Sergey Senozhatsky
2019-03-19 8:10 ` Dmitry Vyukov
2019-03-19 12:35 ` Sergey Senozhatsky
2019-03-19 13:35 ` Dmitry Vyukov
2019-05-08 10:31 ` Tetsuo Handa
2019-05-09 9:58 ` Sergey Senozhatsky
2019-05-09 10:18 ` Sergey Senozhatsky [this message]
2019-05-09 10:40 ` Tetsuo Handa
2019-05-09 10:26 ` Tetsuo Handa
2019-05-09 10:36 ` Sergey Senozhatsky
2019-05-10 14:12 ` Petr Mladek
2019-05-10 14:53 ` Tetsuo Handa
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=20190509101830.GB23572@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=syzkaller@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