linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Greg KH <greg@kroah.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	stable-review@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [stable] [Stable-review] [116/165] ext4: dont return to userspace after freezing the fs with a mutex held
Date: Wed, 11 Aug 2010 08:20:55 -0400	[thread overview]
Message-ID: <4C6295A7.4030106@redhat.com> (raw)
In-Reply-To: <4C6265BE.7090509@canonical.com>

Stefan Bader wrote:
> On 08/10/2010 10:16 PM, Greg KH wrote:
>> On Mon, Aug 09, 2010 at 11:00:43AM +0200, Stefan Bader wrote:
>>> On 08/07/2010 03:38 PM, Eric Sandeen wrote:
>>>> Henrique de Moraes Holschuh wrote:
>>>>> On Mon, 02 Aug 2010, Greg KH wrote:
>>>>>> On Mon, Aug 02, 2010 at 12:02:45PM -0500, Eric Sandeen wrote:
>>>>>>> On 08/02/2010 07:04 AM, Stefan Bader wrote:
>>>>>>>> We have reports about this patch breaking lvm snapshhots. Eric, there is a patch
>>>>>>>> mentioned which is supposed to fix things but its not upstream, yet.
>>>>>>>> Do you know what happened to that?
>>>>>>> right, patch below is needed to fix things.
>>>>>>>
>>>>>>> Ted just acked it on the list recently; Greg, I'd either drop 116/165
>>>>>>> for now, or include the patch below which should be upstream soon...
>>>>>> I can't take anything that isn't upstream yet.
>>>>>>
>>>>>> And I just released with this patch in the kernel, should I do a revert
>>>>>> and do a new release?
>>>>> Any answers on this?
>>>>>
>>>> Yes, I'd revert it for now, I'm afraid, if the other patch isn't upstream
>>>> yet.
>>>>
>>>> Sorry about that,
>>>>
>>>> -Eric
>>> Upstream as of now (same SHA1 as in linux-next):
>>>
>>> >From 437f88cc031ffe7f37f3e705367f4fe1f4be8b0f Mon Sep 17 00:00:00 2001
>>> From: Eric Sandeen <sandeen@sandeen.net>
>>> Date: Sun, 1 Aug 2010 17:33:29 -0400
>>> Subject: [PATCH] (pre-stable) ext4: fix freeze deadlock under IO
>> It looks like I can't drop the original one, as this patch builds on it.
>> So I'll just queue this one up.
>>
>> Should it also go into other -stable releases (like .35 and/or .34 -stable?)
>>
> 
> Final call would be Eric/Ted but as far as I can see:
> 
> .34: not for now (patch that causes regression not backported there (yet))
> .35: yes (offending patch has been in 2.6.35-rc1)

As long as the 2 patches go together it should be fine, I don't think there
are other significant dependencies.

It's also not really an urgent one to fix; returning to userspace w/ a lock
held is pretty icky but in practice has not been an actual problem AFAIK; most
people use lvm to freeze/unfreeze and it all gets cleaned up....

-Eric

> -Stefan
> 
>> thanks,
>>
>> greg k-h
> 


  reply	other threads:[~2010-08-11 12:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 17:15 [116/165] ext4: dont return to userspace after freezing the fs with a mutex held Greg KH
2010-08-02 12:04 ` [Stable-review] " Stefan Bader
2010-08-02 17:02   ` Eric Sandeen
2010-08-02 18:48     ` [stable] " Greg KH
2010-08-07  4:07       ` Henrique de Moraes Holschuh
2010-08-07  5:15         ` Greg KH
2010-08-07 13:38         ` Eric Sandeen
2010-08-09  9:00           ` Stefan Bader
2010-08-10 20:16             ` Greg KH
2010-08-11  8:56               ` Stefan Bader
2010-08-11 12:20                 ` Eric Sandeen [this message]
2010-08-11 12:34                   ` [Stable-review] [stable] " Ted Ts'o
2018-07-05 16:25             ` [stable] [Stable-review] " 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=4C6295A7.4030106@redhat.com \
    --to=sandeen@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-review@kernel.org \
    --cc=stable@kernel.org \
    --cc=stefan.bader@canonical.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).