All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matt <jackdachef@gmail.com>
Cc: 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: Sat, 6 Sep 2014 20:18:14 -0700	[thread overview]
Message-ID: <20140907031814.GA961@kroah.com> (raw)
In-Reply-To: <CAG-aW04YvZVxKBhSAYqhr5OBFovA3HHHWgdfEQU_jXKzQK7QdA@mail.gmail.com>

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.

thanks,

greg k-h

  reply	other threads:[~2014-09-07  3:18 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 [this message]
2014-09-11  4:29             ` Jeff Mahoney
2014-09-12 21:29               ` 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=20140907031814.GA961@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jackdachef@gmail.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 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.