From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Jan Kara <jack@suse.cz>, Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
syzbot <syzbot+9933e4476f365f5d5a1b@syzkaller.appspotmail.com>,
linux-mm@kvack.org, mgorman@techsingularity.net,
Michal Hocko <mhocko@kernel.org>,
ak@linux.intel.com, jlayton@redhat.com,
linux-kernel@vger.kernel.org, mawilcox@microsoft.com,
syzkaller-bugs@googlegroups.com, tim.c.chen@linux.intel.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: INFO: task hung in generic_file_write_iter
Date: Mon, 20 Aug 2018 23:12:10 +0900 [thread overview]
Message-ID: <e51a7822-3fdc-3f7a-25bd-5d8d8df44749@i-love.sakura.ne.jp> (raw)
In-Reply-To: <8248f4e9-3567-b8f5-4751-8b38c1807eff@i-love.sakura.ne.jp>
On 2018/08/06 20:56, Tetsuo Handa wrote:
> On 2018/08/06 19:09, Jan Kara wrote:
>> Looks like some kind of a race where device block size gets changed while
>> getblk() runs (and creates buffers for underlying page). I don't have time
>> to nail it down at this moment can have a look into it later unless someone
>> beats me to it.
>>
>
> It seems that loop device is relevant to this problem.
Speak of loop device, I'm waiting for Jens for three months
http://lkml.kernel.org/r/1527297408-4428-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp
but Jens is too busy to come up with an alternative. Since that is a big patch, I wish we can
start testing that patch before Jan starts writing a patch for fixing getblk() race problem.
next prev parent reply other threads:[~2018-08-20 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 8:58 INFO: task hung in generic_file_write_iter syzbot
2018-07-18 10:28 ` Tetsuo Handa
2018-07-18 10:36 ` Dmitry Vyukov
2018-07-20 10:36 ` Tetsuo Handa
2018-07-20 20:06 ` Andrew Morton
2018-07-30 15:07 ` Tetsuo Handa
2018-08-06 10:09 ` Jan Kara
2018-08-06 11:56 ` Tetsuo Handa
2018-08-20 14:12 ` Tetsuo Handa [this message]
2018-12-28 13:34 ` Tetsuo Handa
2019-01-02 14:40 ` Jan Kara
2019-01-02 14:46 ` Dmitry Vyukov
2019-01-02 16:07 ` Tetsuo Handa
2019-01-02 17:26 ` Jan Kara
2019-01-03 0:46 ` Tetsuo Handa
2019-01-08 10:04 ` Tetsuo Handa
2019-01-08 11:24 ` Jan Kara
2019-01-08 11:49 ` Dmitry Vyukov
2019-01-09 13:30 ` Jan Kara
2019-01-14 15:11 ` Dmitry Vyukov
2019-01-14 15:13 ` Dmitry Vyukov
2019-01-15 9:29 ` Jan Kara
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=e51a7822-3fdc-3f7a-25bd-5d8d8df44749@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=syzbot+9933e4476f365f5d5a1b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tim.c.chen@linux.intel.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).