All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH 0/5] xfs: quota deadlock fixes
Date: Mon, 20 Feb 2017 11:52:56 +0800	[thread overview]
Message-ID: <20170220035256.GH24562@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170217175454.GA20429@bfoster.bfoster>

[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]

On Fri, Feb 17, 2017 at 12:54:54PM -0500, Brian Foster wrote:
> On Fri, Feb 17, 2017 at 02:53:15PM +0800, Eryu Guan wrote:
> > On Wed, Feb 15, 2017 at 10:40:42AM -0500, Brian Foster wrote:
> > > Hi all,
> > > 
> > > This is a collection of several quota related deadlock fixes for
> > > problems that have been reported to the list recently.
> > > 
> > > Patch 1 fixes the low memory quotacheck problem reported by Martin[1].
> > > Dave is CC'd as he had comments on this particular thread that started a
> > > discussion, but I hadn't heard anything back since my last response.
> > > 
> > > Patch 2 fixes a separate problem I ran into while attempting to
> > > reproduce Eryu's xfs/305 hang report[2]. 
> > > 
> > > Patches 3-5 fix the actual problem reported by Eryu, which is a quotaoff
> > > deadlock reproduced by xfs/305.
> > > 
> > > Further details are included in the individual commit log descriptions.
> > > Thoughts, reviews, flames appreciated.
> > > 
> > > Eryu,
> > > 
> > > I've run several hundred iterations of this on your reproducer system
> > > without reproducing the hang. I have reproduced a reset overnight but
> > > still haven't been able to grab a stack trace from that occurrence (I'll
> > > try again today/tonight with better console logging). I suspect this is
> > 
> > I hit a NULL pointer dereference while testing your fix, I was running
> > xfs/305 for 1000 iterations and host crashed at the 639th run. Not sure
> > if it's the same issue you've met here. I posted dmesg log at the end of
> > mail. I haven't tried to see if I can reproduce it on stock linus tree
> > yet.
> > 
> 
> Interesting, thanks. I don't know for sure because I didn't hit anything
> on my second overnight run, but I wouldn't be surprised if it's the
> same, particularly if you hit this again. This does look like an
> independent problem to me, though. A kdump might be nice, if possible,
> given the difficulty to reproduce...

Unfortunately, my second round of 1000 iteration run hit hang too, at
the 824th loop.  Test configuration is all default, crc enabled XFS with
4k block size, no rmapbt no reflink no finobt no sparse inode.

I attached the dmesg log and sysrq-w output. I also left the host in the
hang state, you can login and take a look if you have interest.

Thanks,
Eryu

[-- Attachment #2: upstream-4.10-rc4-xfs-305-testpatch-sysrq-w.log.bz2 --]
[-- Type: application/x-bzip2, Size: 22771 bytes --]

  reply	other threads:[~2017-02-20  3:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 15:40 [PATCH 0/5] xfs: quota deadlock fixes Brian Foster
2017-02-15 15:40 ` [PATCH 1/5] xfs: bypass dquot reclaim to avoid quotacheck deadlock Brian Foster
2017-02-16 22:37   ` Dave Chinner
2017-02-17 18:30     ` Brian Foster
2017-02-17 23:12       ` Dave Chinner
2017-02-18 12:55         ` Brian Foster
2017-02-15 15:40 ` [PATCH 2/5] xfs: allocate quotaoff transactions up front to avoid log deadlock Brian Foster
2017-04-26 21:23   ` Darrick J. Wong
2017-04-27 12:03     ` Brian Foster
2017-04-27 15:47       ` Darrick J. Wong
2017-02-15 15:40 ` [PATCH 3/5] xfs: support ability to wait on new inodes Brian Foster
2017-04-27 21:15   ` Darrick J. Wong
2017-02-15 15:40 ` [PATCH 4/5] xfs: update ag iterator to support " Brian Foster
2017-04-27 21:17   ` Darrick J. Wong
2017-02-15 15:40 ` [PATCH 5/5] xfs: wait on new inodes during quotaoff dquot release Brian Foster
2017-04-27 21:17   ` Darrick J. Wong
2017-02-16  7:42 ` [PATCH 0/5] xfs: quota deadlock fixes Eryu Guan
2017-02-16 12:01   ` Brian Foster
2017-02-17  6:53 ` Eryu Guan
2017-02-17 17:54   ` Brian Foster
2017-02-20  3:52     ` Eryu Guan [this message]
2017-02-20 13:25       ` Brian Foster
2017-02-22 15:35         ` Brian Foster

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=20170220035256.GH24562@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --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.