All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.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	[thread overview]
Message-ID: <bug-203947-201763-A5Yvtlh7W1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203947-201763@https.bugzilla.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.

  parent reply	other threads:[~2019-07-12  4:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21  8:32 [Bug 203947] New: [xfstests generic/475]: general protection fault: 0000 [#1] RIP: 0010:xfs_setfilesize_ioend+0xb1/0x220 [xfs] bugzilla-daemon
2019-06-27  8:35 ` [Bug 203947] " bugzilla-daemon
2019-06-27 18:35 ` bugzilla-daemon
2019-06-27 18:35 ` bugzilla-daemon
2019-06-29  3:30 ` bugzilla-daemon
2019-06-29  3:46 ` bugzilla-daemon
2019-06-29  3:48 ` bugzilla-daemon
2019-06-29 16:07 ` bugzilla-daemon
2019-06-29 17:31 ` bugzilla-daemon
2019-06-29 17:35 ` bugzilla-daemon
2019-06-30 13:52 ` bugzilla-daemon
2019-07-09  4:30 ` bugzilla-daemon
2019-07-11 22:59 ` bugzilla-daemon
2019-07-12  4:27 ` bugzilla-daemon [this message]
2019-07-12 13:18 ` bugzilla-daemon

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=bug-203947-201763-A5Yvtlh7W1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.