The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Chris Frey <cdfrey@foursquare.net>,
	chrisw@sous-sol.org, linux-kernel@vger.kernel.org,
	smfrench@gmail.com
Subject: Re: fs/cifs/connect.c fix missing in latest stable
Date: Mon, 27 Apr 2009 19:44:41 -0400	[thread overview]
Message-ID: <20090427194441.10bac23d@tleilax.poochiereds.net> (raw)
In-Reply-To: <20090427221121.GD3036@sequoia.sous-sol.org>

On Mon, 27 Apr 2009 15:11:21 -0700
Chris Wright <chrisw@sous-sol.org> wrote:

> * Chris Frey (cdfrey@foursquare.net) wrote:
> > Hi Chris,
> > 
> > The latest stable release 2.6.29.2 appears to be missing Jeff Layton's
> > fix in commit f083def68f84b04fe3f97312498911afce79609e (in Linus's tree).
> > 
> > I'm not the expert... I just noticed that this was mentioned on
> > full-disclosure: http://marc.info/?l=full-disclosure&m=123936563230145&w=2
> > (near the end of Andreas's post)
> 
> Yes, I think cifs developers are still doing cleanups in that area.
> Jeff?
> 

Yes, we are but they're pretty close. Some have already gone in and
some are still outstanding. Suresh J. has done the bulk of the work,
but there are a few additional fixes for other areas too.

I've been traveling for the last week, and took today off. My plan is
to get with Steve French tomorrow and finalize a set of fixes for his
tree that he can push to mainline and stable.

-- 
Jeff Layton <jlayton@redhat.com>

  reply	other threads:[~2009-04-27 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 20:57 fs/cifs/connect.c fix missing in latest stable Chris Frey
2009-04-27 22:11 ` Chris Wright
2009-04-27 23:44   ` Jeff Layton [this message]
2009-04-27 23:47     ` Chris Wright
2009-04-27 23:48     ` Steve French

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=20090427194441.10bac23d@tleilax.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=cdfrey@foursquare.net \
    --cc=chrisw@sous-sol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox