All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Petr Mladek <pmladek@suse.com>
Cc: syzbot <syzbot+fc1da0f1a577d15b64fc@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: possible deadlock in console_trylock_spinning
Date: Tue, 25 Jun 2019 18:52:36 +0900	[thread overview]
Message-ID: <8999365f-9de0-c850-087e-be9a7eb04547@i-love.sakura.ne.jp> (raw)
In-Reply-To: <0000000000007b0e26058c2215d3@google.com>

On 2019/06/25 17:55, syzbot wrote:
> syzbot has bisected this bug to:
> 
> commit e80b18599a39a625bc8b2e39ba3004a62f78805a
> Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date:   Fri Apr 12 11:04:54 2019 +0000
> 
>     tomoyo: Add a kernel config option for fuzzing testing.
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=156e43cea00000
> start commit:   abf02e29 Merge tag 'pm-5.2-rc6' of git://git.kernel.org/pu..
> git tree:       upstream
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=176e43cea00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=136e43cea00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=28ec3437a5394ee0
> dashboard link: https://syzkaller.appspot.com/bug?extid=fc1da0f1a577d15b64fc
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1357add6a00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1611ac89a00000
> 
> Reported-by: syzbot+fc1da0f1a577d15b64fc@syzkaller.appspotmail.com
> Fixes: e80b18599a39 ("tomoyo: Add a kernel config option for fuzzing testing.")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 

This is not a TOMOYO's problem because that commit simply confused inject_fault(4)
by adding memory allocation from TOMOYO's hook. Anyway, this bug should be sent to
printk() people.


      reply	other threads:[~2019-06-25  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 13:17 possible deadlock in console_trylock_spinning syzbot
2019-06-22 13:55 ` syzbot
2019-06-25  8:55 ` syzbot
2019-06-25  9:52   ` Tetsuo Handa [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=8999365f-9de0-c850-087e-be9a7eb04547@i-love.sakura.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=syzbot+fc1da0f1a577d15b64fc@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 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.