From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Matt <jackdachef@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: linux-3.16.2 queue (3.16.1+)
Date: Fri, 12 Sep 2014 14:29:18 -0700 [thread overview]
Message-ID: <20140912212918.GA9690@kroah.com> (raw)
In-Reply-To: <5411252A.1030901@suse.com>
On Thu, Sep 11, 2014 at 12:29:30AM -0400, Jeff Mahoney wrote:
> On 9/6/14, 11:18 PM, Greg KH wrote:
> > On Sun, Sep 07, 2014 at 02:47:55AM +0200, Matt wrote:
> >> On Thu, Aug 28, 2014 at 9:18 PM, Matt <jackdachef@gmail.com>
> >> wrote:
> >>> On Thu, Aug 28, 2014 at 5:32 PM, Greg KH
> >>> <gregkh@linuxfoundation.org> wrote:
> >>>> On Thu, Aug 28, 2014 at 05:27:27PM +0200, Matt wrote:
> >>>>> On Thu, Aug 28, 2014 at 5:22 PM, Greg KH
> >>>>> <gregkh@linuxfoundation.org> wrote:
> >>>>>> On Thu, Aug 28, 2014 at 05:16:58PM +0200, Matt wrote:
> >>>>>>> Hi Greg,
> >>>>>>>
> >>>>>>>
> >>>>>>> please consider adding the following 2 patches to
> >>>>>>> 3.16.2:
> >>>>>>>
> >>>>>>> Jan Kara (1): reiserfs: Fix use after free in journal
> >>>>>>> teardown
> >>>>>>>
> >>>>>>> Jeff Mahoney (1): reiserfs: fix corruption introduced
> >>>>>>> by balance_leaf refactor
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Reason/Related:
> >>>>>>>
> >>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=83121
> >>>>>>>
> >>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=83321
> >>>>>>>
> >>>>>>> http://forums.gentoo.org/viewtopic-t-998538-postdays-0-postorder-asc-start-0.html
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> Many thanks in advance
> >>>>>>
> >>>>>> I need git commit ids of these patches in Linus's tree,
> >>>>>> can you provide those please?
> >>>>>>
> >>>>>> thanks,
> >>>>>>
> >>>>>> greg k-h
> >>>>>
> >>>>>
> >>>>> Sure:
> >>>>>
> >>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=27d0e5bc85f3341b9ba66f0c23627cf9d7538c9d
> >>>>>
> >>>>>
> reiserfs: fix corruption introduced by balance_leaf refactor
> >>>>>
> >>>>>
> >>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=01777836c87081e4f68c4a43c9abe6114805f91e
> >>>>>
> >>>>>
> reiserfs: Fix use after free in journal teardown
> >>>>>
> >>>>>
> >>>>>
> >>>>> are checkpatch warnings usually also fixed within stable
> >>>>> releases ?
> >>>>
> >>>> No, not at all, please read
> >>>> Documentation/stable_kernel_patches.txt for what is
> >>>> acceptable for stable kernel patches.
> >>>>
> >>>> thanks,
> >>>>
> >>>> greg k-h
> >>>
> >>>
> >>> okay, will do
> >>>
> >>> thanks for pointing that out
> >>>
> >>>
> >>> Regards
> >>>
> >>> Matt
> >>
> >> Hi Greg,
> >>
> >> could you please add the above mentioned two patches
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=27d0e5bc85f3341b9ba66f0c23627cf9d7538c9d
> >>
> >>
> reiserfs: fix corruption introduced by balance_leaf refactor
> >>
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=01777836c87081e4f68c4a43c9abe6114805f91e
> >>
> >>
> reiserfs: Fix use after free in journal teardown
> >>
> >> in next stable (3.16.3) kernel ?
> >>
> >> more and more people seem to be affected by the data corruption
> >> introduced by the recent changes.
> >>
> >>
> >> Reading through Documentation/stable_kernel_rules.txt,
> >> http://cwe.mitre.org/data/definitions/416.html and
> >> http://www.hpenterprisesecurity.com/vulncat/en/vulncat/cpp/use_after_free.html
> >>
> >>
> >>
> both patches seem relevant enough (concerning data integrity
> >> filesystem-wise and security) to be included for the stable
> >> branch
> >
> > I'll queue this up when I get a chance, there are over 300 patches
> > pending for the stable kernels right now :(
> >
> > Also, in the future, always cc stable@vger.kernel.org for any
> > stable requests so that they don't get lost.
>
> Hi Greg -
>
> 27d0e5bc85f3341b9ba66f0c23627cf9d7538c9d
> Author: Jeff Mahoney <jeffm@suse.com>
> Date: Mon Aug 4 19:51:47 2014 -0400
>
> reiserfs: fix corruption introduced by balance_leaf refactor
>
> Commits f1f007c308e (reiserfs: balance_leaf refactor, pull out
> balance_leaf_insert_left) and cf22df182bf (reiserfs: balance_leaf
> refactor, pull out balance_leaf_paste_left) missed that the `body'
> pointer was getting repositioned. Subsequent users of the pointer
> would expect it to be repositioned, and as a result, parts of the
> tree would get overwritten. The most common observed corruption
> is indirect block pointers being overwritten.
>
> Since the body value isn't actually used anymore in the called
> routines,
> we can pass back the offset it should be shifted. We constify the body
> and ih pointers in the balance_leaf as a mostly-free preventative
> measure.
>
> Cc: <stable@vger.kernel.org> # 3.16
> Reported-and-tested-by: Jeff Chua <jeff.chua.linux@gmail.com>
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> Signed-off-by: Jan Kara <jack@suse.cz>
>
> Should there have been more? I thought it was enough to add the Cc
> tag. This one has been in the tree, with the tags and with
> "corruption" in the Subject since 13 Aug. I know you're busy but this
> seems like a pretty obvious candidate for stable inclusion.
You marked this one just fine, it's just that, again, I have over 300+
patches in the "marked for stable" queue right now, this patch is in
good company...
greg k-h
prev parent reply other threads:[~2014-09-12 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 15:16 linux-3.16.2 queue (3.16.1+) Matt
2014-08-28 15:22 ` Greg KH
2014-08-28 15:27 ` Matt
2014-08-28 15:32 ` Greg KH
2014-08-28 19:18 ` Matt
2014-09-07 0:47 ` Matt
2014-09-07 3:18 ` Greg KH
2014-09-11 4:29 ` Jeff Mahoney
2014-09-12 21:29 ` Greg KH [this message]
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=20140912212918.GA9690@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jackdachef@gmail.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.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).