From: Greg KH <greg@kroah.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Eric Sandeen <sandeen@redhat.com>,
Stefan Bader <stefan.bader@canonical.com>,
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: Fri, 6 Aug 2010 22:15:09 -0700 [thread overview]
Message-ID: <20100807051509.GA25191@kroah.com> (raw)
In-Reply-To: <20100807040732.GB16342@khazad-dum.debian.net>
On Sat, Aug 07, 2010 at 01:07:32AM -0300, 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?
Nope :(
next prev parent reply other threads:[~2010-08-07 5:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 17:15 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 [this message]
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 ` [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=20100807051509.GA25191@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome