From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: viro@zeniv.linux.org.uk, Michal Hocko <mhocko@suse.com>
Cc: syzbot <syzbot+5a170e19c963a2e0df79@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, linux-mm <linux-mm@kvack.org>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: WARNING in kill_block_super
Date: Wed, 4 Apr 2018 19:53:07 +0900 [thread overview]
Message-ID: <6c95e826-4b9f-fb21-b311-830411e58480@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <001a114043bcfab6ab05689518f9@google.com>
Al and Michal, are you OK with this patch?
next parent reply other threads:[~2018-04-04 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a114043bcfab6ab05689518f9@google.com>
2018-04-04 10:53 ` Tetsuo Handa [this message]
2018-04-06 8:09 ` Michal Hocko
2018-04-07 5:55 ` Tetsuo Handa
2018-04-11 0:59 ` Al Viro
2018-04-11 1:28 ` Tetsuo Handa
2018-04-11 1:38 ` Al Viro
2018-04-11 10:09 ` 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=6c95e826-4b9f-fb21-b311-830411e58480@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=syzbot+5a170e19c963a2e0df79@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