From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: Andreas Gruenbacher <agruen@suse.de>,
Tiger Yang <tiger.yang@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH] ext3/4: fix uninitialized bs in ext3/4_xattr_set_handle()
Date: Wed, 14 May 2008 10:28:09 -0700 [thread overview]
Message-ID: <20080514102809.3fc190f0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080514160035.GD28594@kroah.com>
On Wed, 14 May 2008 09:00:36 -0700 Greg KH <greg@kroah.com> wrote:
> On Wed, May 14, 2008 at 12:56:42PM +0200, Andreas Gruenbacher wrote:
> > On Tuesday 13 May 2008 04:31:04 Tiger Yang wrote:
> > > Hi, Andrew
> > >
> > > This situation only happens we format ext3/4 with inode size more than
> > > 128 and we have put xattr entries both in ibody and block.
> > > The consequences about this bug is we will lost the xattr block which
> > > pointed by i_file_acl with all xattr entires in it. We will alloc a new
> > > xattr block and put that large value entry in it. The old xattr block
> > > will become orphan block.
> >
> > The patch looks good, and it obviously fixes the described problem. Thanks!
> >
> > Signed-off-by: Andreas Gruenbacher <agruen@suse.de>
> >
> >
> > Could it please be added to -stable?
>
> Can someone actually _send_ the patch to stable@kernel.org? I haven't
> seen it yet :)
>
> And is it in Linus's tree? We need to wait until it is there before we
> can add it to -stable.
It's in -mm and I just added the "Cc:stable" tag to it.
next prev parent reply other threads:[~2008-05-14 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 3:24 [PATCH] ext3/4: fix uninitialized bs in ext3/4_xattr_set_handle() Tiger Yang
2008-05-13 0:02 ` Andrew Morton
2008-05-13 2:31 ` Tiger Yang
2008-05-13 20:00 ` Andreas Dilger
2008-05-14 10:56 ` Andreas Gruenbacher
2008-05-14 16:00 ` [stable] " Greg KH
2008-05-14 17:28 ` Andrew Morton [this message]
2008-05-14 22:30 ` Theodore Tso
2008-05-14 22:54 ` Andrew Morton
2008-05-13 0:18 ` Eric Sandeen
2008-05-13 7:48 ` Tiger Yang
2008-05-13 12:48 ` Eric Sandeen
2008-05-13 8:48 ` Kalpak Shah
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=20080514102809.3fc190f0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agruen@suse.de \
--cc=greg@kroah.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tiger.yang@oracle.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;
as well as URLs for NNTP newsgroup(s).