linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+5751b57c82cd229ffbee@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com
Cc: akpm@linux-foundation.org, amir73il@gmail.com,
	darrick.wong@oracle.com, david@fromorbit.com, hannes@cmpxchg.org,
	jrdr.linux@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, willy@infradead.org
Subject: Re: INFO: rcu detected stall in sys_mount (2)
Date: Thu, 13 Dec 2018 06:01:05 +0900	[thread overview]
Message-ID: <240fff25-0288-a0e6-a018-2e1593afc228@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <0000000000004a25cc057cd65aad@google.com>

Stalling inside __getblk_gfp()...

#syz dup: INFO: rcu detected stall in sys_creat

      reply	other threads:[~2018-12-12 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 17:16 syzbot
2018-12-12 21:01 ` 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=240fff25-0288-a0e6-a018-2e1593afc228@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hannes@cmpxchg.org \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+5751b57c82cd229ffbee@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox