From: Greg KH <greg@kroah.com>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Alex Elder <aelder@sgi.com>, Mark Lord <kernel@teksavvy.com>,
stable@kernel.org
Subject: Re: [stable] [GIT PULL] XFS update for 2.6.38-rc3
Date: Wed, 16 Feb 2011 13:50:02 -0800 [thread overview]
Message-ID: <20110216215002.GJ5027@kroah.com> (raw)
In-Reply-To: <201102032302.31780.a.miskiewicz@gmail.com>
On Thu, Feb 03, 2011 at 11:02:31PM +0100, Arkadiusz Miskiewicz wrote:
> 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:
Now queued up (it will make .2, sorry, not .1)
thanks,
greg k-h
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org,
Mark Lord <kernel@teksavvy.com>,
Dave Chinner <david@fromorbit.com>,
stable@kernel.org, Alex Elder <aelder@sgi.com>
Subject: Re: [stable] [GIT PULL] XFS update for 2.6.38-rc3
Date: Wed, 16 Feb 2011 13:50:02 -0800 [thread overview]
Message-ID: <20110216215002.GJ5027@kroah.com> (raw)
In-Reply-To: <201102032302.31780.a.miskiewicz@gmail.com>
On Thu, Feb 03, 2011 at 11:02:31PM +0100, Arkadiusz Miskiewicz wrote:
> 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:
Now queued up (it will make .2, sorry, not .1)
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-16 21:57 UTC|newest]
Thread overview: 10+ 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-01-31 16:42 ` Alex Elder
2011-02-01 16:00 ` Mark Lord
2011-02-01 16:00 ` Mark Lord
2011-02-03 0:07 ` Dave Chinner
2011-02-03 0:07 ` Dave Chinner
2011-02-03 22:02 ` Arkadiusz Miskiewicz
2011-02-03 22:02 ` Arkadiusz Miskiewicz
2011-02-16 21:50 ` Greg KH [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=20110216215002.GJ5027@kroah.com \
--to=greg@kroah.com \
--cc=a.miskiewicz@gmail.com \
--cc=aelder@sgi.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 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.