All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Steve French <smfrench@gmail.com>
Cc: Jeff Layton <jlayton@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"linux-cifs-client@lists.samba.org" 
	<linux-cifs-client@lists.samba.org>
Subject: Re: third patch
Date: Sun, 16 Nov 2008 21:56:03 -0800	[thread overview]
Message-ID: <20081117055603.GA1381@kroah.com> (raw)
In-Reply-To: <524f69650811161918i738ba50frd87666a58640b76f@mail.gmail.com>

On Sun, Nov 16, 2008 at 09:18:43PM -0600, Steve French wrote:
> Jeff and I have worked on a series of patches to fix the oopses,
> memory corruption and mount failures due to races in various linked
> list handling relating to socket, session and tree connection when
> using the reproducer detailed here:
> 
> https://bugzilla.samba.org/show_bug.cgi?id=5720
> 
> The fix series is now merged into cifs-2.6.git

Are these patches going to be sent to Linus for the 2.6.28 release?
Should they be also added to the 2.6.27-stable tree when they get to
Linus's tree?  If so, what are their git commit ids?

thanks,

greg k-h

  reply	other threads:[~2008-11-17  6:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081114185039.1f3af842@tleilax.poochiereds.net>
     [not found] ` <524f69650811141609n63f3631bn6493e2be76b1bed6@mail.gmail.com>
     [not found]   ` <20081115063641.26003498@tleilax.poochiereds.net>
2008-11-17  3:18     ` third patch Steve French
2008-11-17  5:56       ` Greg KH [this message]
2008-11-17 23:06         ` Steve French
2008-11-17 23:38           ` Greg KH
2008-11-18 20:23             ` Steve French
2008-11-21  7:21             ` [linux-cifs-client] " Suresh Jayaraman

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=20081117055603.GA1381@kroah.com \
    --to=greg@kroah.com \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.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 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.