mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	stable <stable@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Missing stable commits?
Date: Mon, 05 Mar 2012 11:39:26 -0500	[thread overview]
Message-ID: <1330965566.25686.327.camel@gandalf.stny.rr.com> (raw)

As I'm going through adding commits from Thomas's latest -rt patch set
into the stable-rt tree, some of the patches conflicted. Looking at the
conflicts, it seems that mainline has patches that should probably be
added to the stable tree. Here's what I found so far:

commit 1b71fe2efa31cd18c865db474a4cd473b6ab5281
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Jul 16 23:43:58 2011 -0400

    ceph analog of cifs build_path_from_dentry() race fix
    
    ... unfortunately, cifs bug got copied.  Fix is essentially the same.
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

commit dc137bf553dbb6855bd7efc34fedcd03102455f7
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Jul 16 23:37:20 2011 -0400

    cifs: build_path_from_dentry() race fix
    
    deal with d_move() races properly; rename_lock read-retry loop,
    rcu_read_lock() held while walking to root, d_lock held over
    subtraction from namelen and copying the component to stabilize
    ->d_name.
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>


These seem appropriate for stable, don't they?

-- Steve



             reply	other threads:[~2012-03-05 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 16:39 Steven Rostedt [this message]
2012-03-05 16:43 ` Steven Rostedt

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=1330965566.25686.327.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®