public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Cc: Dave Chinner <david@fromorbit.com>,
	Mark Lord <kernel@teksavvy.com>, Alex Elder <aelder@sgi.com>,
	stable@kernel.org
Subject: Re: [GIT PULL] XFS update for 2.6.38-rc3
Date: Thu, 3 Feb 2011 23:02:31 +0100	[thread overview]
Message-ID: <201102032302.31780.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <20110203000757.GT11040@dastard>

On Thursday 03 of February 2011, Dave Chinner wrote:
> On Tue, Feb 01, 2011 at 11:00:33AM -0500, Mark Lord wrote:
> > On 11-01-31 11:42 AM, Alex Elder wrote:
> > > Linus, please accept the following updates for XFS, for 2.6.38-rc3
> > > (if it's not too late) or 2.6.38-rc4.
> > > 
> > > They are all fixes for bugs that have some pretty undesirable
> > > consequences. 

[...]

> > Are these bugs all new in 2.6.38, or should some of these fixes
> > also go out to -stable for earlier revisions?
> > >       xfs: fix dquot shaker deadlock
> 
> That's a regression, so maybe.

Definitely, xfs_fsr can hit this even few times a day (happened already).

Stable team, please include this one for 2.6.37.1:

commit 0fbca4d1c3932c27c4794bf5c2b5fc961cf5a54f
Author: Dave Chinner <dchinner@redhat.com>
Date:   Fri Jan 28 11:20:46 2011 +1100

    xfs: fix dquot shaker deadlock

    Commit 368e136 ("xfs: remove duplicate code from dquot reclaim") fails
    to unlock the dquot freelist when the number of loop restarts is
    exceeded in xfs_qm_dqreclaim_one(). This causes hangs in memory
    reclaim.

    Rework the loop control logic into an unwind stack that all the
    different cases jump into. This means there is only one set of code
    that processes the loop exit criteria, and simplifies the unlocking
    of all the items from different points in the loop. It also fixes a
    double increment of the restart counter from the qi_dqlist_lock
    case.

    Reported-by: Malcolm Scott <lkml@malc.org.uk>
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Alex Elder <aelder@sgi.com>


> Cheers,
> 
> Dave.


-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

  reply	other threads:[~2011-02-03 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 16:42 [GIT PULL] XFS update for 2.6.38-rc3 Alex Elder
2011-02-01 16:00 ` Mark Lord
2011-02-03  0:07   ` Dave Chinner
2011-02-03 22:02     ` Arkadiusz Miskiewicz [this message]
2011-02-16 21:50       ` [stable] " Greg KH

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=201102032302.31780.a.miskiewicz@gmail.com \
    --to=a.miskiewicz@gmail.com \
    --cc=aelder@sgi.com \
    --cc=david@fromorbit.com \
    --cc=kernel@teksavvy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=xfs@oss.sgi.com \
    /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