From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:58886 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726610AbfGLE1K (ORCPT ); Fri, 12 Jul 2019 00:27:10 -0400 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 987BD28BAF for ; Fri, 12 Jul 2019 04:27:09 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 203947] [xfstests generic/475]: general protection fault: 0000 [#1] RIP: 0010:xfs_setfilesize_ioend+0xb1/0x220 [xfs] Date: Fri, 12 Jul 2019 04:27:08 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: linux-xfs@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=203947 --- Comment #13 from Zorro Lang (zlang@redhat.com) --- (In reply to Luis Chamberlain from comment #12) > (In reply to Zorro Lang from comment #11) > > (In reply to Zorro Lang from comment #10) > > > (In reply to Darrick J. Wong from comment #9) > > > > Zorro, > > > > > > > > If you get a chance, can you try this debugging patch, please? > > > > > > Sure, I'll give it a try. With this bug together ... they both triggered > by > > > g/475. You really write a nice case :) > > > > > > Both these two bugs are too hard to reproduce, so I only can try my best > to > > > test it, but I can't 100% verify they're fixed even if all test pass, > I'll > > > try to approach 99% :-P > > > > > > BTW, if this's a separate bug, I'd like to report a new bug to track it, > to > > > avoid confusion. > > > > > > Thanks, > > > Zorro > > > > Updata: By merging the patches in comment 2 and comment 9, I can't > reproduce > > this bug and https://bugzilla.kernel.org/show_bug.cgi?id=204031, after > > running generic/475 on six different machines 3 days. > > Can you try with just the patch in comment 2? Also it doesn't seem clear to > me yet if this is a regression or not. Did this used to work? If not sure > can you try with v4.19 and see if the issue also appears there? I didn't try to make sure if it's a regression or not. Due to 1. This bug is very hard to be reproduced. 2. The reproducer(generic/475) might easily to trigger some other issues on old kernel. Any way, I'll give it a try on v4.19, but I can't promise that I can find out if it's a regression:) -- You are receiving this mail because: You are watching the assignee of the bug.