From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Jim McDonough <jmcd@samba.org>,
David Disseldorp <ddiss@samba.org>,
Steve French <smfrench@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Stable backport of cifs nlink workaround?
Date: Tue, 25 Feb 2014 18:49:10 +0000 [thread overview]
Message-ID: <20140225184901.GA6397@sucs.org> (raw)
In-Reply-To: <20140225094306.63cccecb@corrin.poochiereds.net>
On Tue, Feb 25, 2014 at 09:43:06AM -0800, Jeff Layton wrote:
> On Tue, 25 Feb 2014 08:11:56 -0800
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> > On Tue, Feb 25, 2014 at 03:24:43PM +0000, Sitsofe Wheeler wrote:
> > >
> > > Is there any chance that 74d290da476f672ad756634d12aa707375d3564d
> > > ([CIFS] Provide sane values for nlink) could be backported to the stable
> > > 3.2 kernel?
> >
> > Why just 3.2? What's wrong with all of the other kernels before 3.12
> > that do not have this patch in it?
>
> Yeah, you'd probably need to apply it to every stable kernel > 3.2 or
> you'd technically have a regression. I've no real objection to putting
> that fix in, but backporting to older kernels may not be trivial. There
> have been other changes in this area over the years...
There's no reason why it should only be 3.2 only - the only reason I
picked that one is because it is the current Debian stable kernel.
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-02-25 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 15:24 Stable backport of cifs nlink workaround? Sitsofe Wheeler
2014-02-25 15:29 ` Steve French
2014-02-25 16:11 ` Greg Kroah-Hartman
2014-02-25 17:43 ` Jeff Layton
2014-02-25 18:49 ` Sitsofe Wheeler [this message]
2014-03-04 19:46 ` Greg Kroah-Hartman
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=20140225184901.GA6397@sucs.org \
--to=sitsofe@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ddiss@samba.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlayton@redhat.com \
--cc=jmcd@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stable@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.