From: "Ted Ts'o" <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Stefan Bader <stefan.bader@canonical.com>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, stable-review@kernel.org,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
stable@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [Stable-review] [stable] [116/165] ext4: dont return to userspace after freezing the fs with a mutex held
Date: Wed, 11 Aug 2010 08:34:25 -0400 [thread overview]
Message-ID: <20100811123425.GP3635@thunk.org> (raw)
In-Reply-To: <4C6295A7.4030106@redhat.com>
On Wed, Aug 11, 2010 at 08:20:55AM -0400, Eric Sandeen wrote:
>
> 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....
Agreed.
I do plan to be uploading stable updates for 2.6.35.x that include the
changes that got pulled for 2.6.35-rc1, and I'll update 2.6.34 and
2.6.32, as well, with 2.6.34 including the updates that somehow didn't
all make it to stable last time. (I'm thinking about also including
an ftp upload since for some reason some mail server between me at
stable@kernel.org seems to be dropping mail messages when they get
blasted out using git send-email. :-/ )
I'm at Linuxcon this week though, so I probably won't get to it until
sometime next week.
- Ted
next prev parent reply other threads:[~2010-08-11 12:34 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
2010-08-11 12:34 ` Ted Ts'o [this message]
2018-07-05 16:25 ` 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=20100811123425.GP3635@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--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 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.