From: Dmitry Vyukov <dvyukov@google.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: syzbot <syzbot+ae80b790eb412884ca77@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: INFO: rcu detected stall in d_walk
Date: Tue, 4 Sep 2018 10:18:33 +0200 [thread overview]
Message-ID: <CACT4Y+Zkf-zR30E4DCxzwsn+WhfjG8uzKXmQGvqvu+7SQqWi0Q@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+YFQfrnvV7XfeCsiQBQ7UicrHE=fadiYdJdPA8=jumW3g@mail.gmail.com>
On Sat, May 19, 2018 at 8:41 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
> On Wed, Apr 25, 2018 at 1:05 PM, Tetsuo Handa
> <penguin-kernel@i-love.sakura.ne.jp> wrote:
>> OK. Patch is in vfs.git#for-next as 4fb48871409e2fcd.
>>
>> #syz fix: restore cond_resched() in shrink_dcache_parent()
>
> I see there is another patch titled "fs/dcache.c: re-add
> cond_resched() in shrink_dcache_parent()" points to this bug:
> http://lkml.iu.edu/hypermail/linux/kernel/1804.1/06252.html
It seems that that commit was pulled into linux-next and overridden
Tetsuo's fix command.
Now it's hopefully has gone from everywhere, so let's remark this with
the right commit:
#syz fix: restore cond_resched() in shrink_dcache_parent()
prev parent reply other threads:[~2018-09-04 12:42 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
2018-05-19 6:41 ` Dmitry Vyukov
2018-09-04 8:18 ` Dmitry Vyukov [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=CACT4Y+Zkf-zR30E4DCxzwsn+WhfjG8uzKXmQGvqvu+7SQqWi0Q@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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).