From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+ae80b790eb412884ca77@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: INFO: rcu detected stall in d_walk
Date: Wed, 25 Apr 2018 20:05:46 +0900 [thread overview]
Message-ID: <46b9489e-6986-d512-1276-9da14c96999e@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000237cc60569ad11c7@google.com>
OK. Patch is in vfs.git#for-next as 4fb48871409e2fcd.
#syz fix: restore cond_resched() in shrink_dcache_parent()
next prev parent reply other threads:[~2018-04-25 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 21:02 INFO: rcu detected stall in d_walk syzbot
2018-04-25 11:05 ` Tetsuo Handa [this message]
2018-05-19 6:41 ` Dmitry Vyukov
2018-09-04 8:18 ` Dmitry Vyukov
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=46b9489e-6986-d512-1276-9da14c96999e@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ae80b790eb412884ca77@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).