From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752621AbcGYHsx (ORCPT ); Mon, 25 Jul 2016 03:48:53 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:18683 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751127AbcGYHsq (ORCPT ); Mon, 25 Jul 2016 03:48:46 -0400 X-IBM-Helo: d06dlp03.portsmouth.uk.ibm.com X-IBM-MailFrom: ldufour@linux.vnet.ibm.com X-IBM-RcptTo: linux-fsdevel@vger.kernel.org;linux-kernel@vger.kernel.org From: Laurent Dufour Subject: About the patch " block: flush writeback dwork before detaching a bdev inode from it" To: Jan Kara Cc: Tejun Heo , Jens Axboe , Andrey Ryabinin , Alexander Viro , "linux-fsdevel@vger.kernel.org" , LKML , syzkaller , Kostya Serebryany , Alexander Potapenko , Ilya Dryomov , Dmitry Vyukov , kernel-team@fb.com, Ted Tso Date: Mon, 25 Jul 2016 09:48:37 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16072507-0020-0000-0000-00000224A8A6 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16072507-0021-0000-0000-00003D4417E2 Message-Id: <17876c16-dd1f-1f75-f41f-4e13ba7527c0@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-07-25_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607250100 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jan, 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 ? Cheers, Laurent.