From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Jan Kara <jack@suse.cz>
Cc: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@fb.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Ilya Dryomov <idryomov@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
kernel-team@fb.com, Ted Tso <tytso@mit.edu>
Subject: Re: About the patch " block: flush writeback dwork before detaching a bdev inode from it"
Date: Mon, 25 Jul 2016 15:50:02 +0200 [thread overview]
Message-ID: <8da613c4-4100-0e2a-234f-cdfda028c343@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160725132925.GB3824@quack2.suse.cz>
On 25/07/2016 15:29, Jan Kara wrote:
> Hi!
>
> On Mon 25-07-16 09:48:37, Laurent Dufour wrote:
>> This is about the patch "block: flush writeback dwork before detaching a
>> bdev inode from it" you sent a month ago to fix a panic hit by Dimitry:
>> https://patchwork.kernel.org/patch/9187409/
>>
>> We hit the same issue on our side, and gave your patch a try, and it
>> fixed the issue.
>>
>> Is there any chance to get this patch accepted upstream ?
>
> Thanks for testing. Can I add your 'Tested-by' tag? I'll send the patch to
> Jens for inclusion.
Hi Jan,
Sure feel free to add:
Tested-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Thanks,
Laurent.
prev parent reply other threads:[~2016-07-25 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 7:48 About the patch " block: flush writeback dwork before detaching a bdev inode from it" Laurent Dufour
2016-07-25 13:29 ` Jan Kara
2016-07-25 13:50 ` Laurent Dufour [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=8da613c4-4100-0e2a-234f-cdfda028c343@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=axboe@fb.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=kcc@google.com \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
--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).