From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Li Zefan <lizefan@huawei.com>
Cc: stable <stable@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [STABLE] find missing bug fixes in a stable kernel
Date: Tue, 14 Jan 2014 20:06:42 -0800 [thread overview]
Message-ID: <20140115040642.GA16810@kroah.com> (raw)
In-Reply-To: <52D494D2.7000908@huawei.com>
On Tue, Jan 14, 2014 at 09:37:22AM +0800, Li Zefan wrote:
> On 2014/1/13 23:57, Greg Kroah-Hartman wrote:
> > On Mon, Jan 13, 2014 at 03:28:11PM +0800, Li Zefan wrote:
> >> We have several long-term and extended stable kernels, and it's possible
> >> that a bug fix is in some stable versions but is missing in some other
> >> versions, so I've written a script to find out those fixes.
> >>
> >> Take 3.4.xx and 3.2.xx for example. If a bug fix was merged into upstream
> >> kernel after 3.4, and then it was backported to 3.2.xx, then it probably
> >> needs to be backported to 3.4.xx.
> >
> > I agree.
> >
> >> The result is, there're ~430 bug fixes in 3.2.xx that probably need to be
> >> backported to 3.4.xx. Given there're about 4500 commits in 3.2.xx, that
> >> is ~10%, which is quite a big number for stable kernels.
> >
> > That's a really big number, how am I missing so many patches for the 3.4
> > kernel? Is it because people are doing backports to 3.2 for patches
> > that didn't apply to 3.4? Or are these patches being applied that do
> > not have -stable markings on them? Or something else?
> >
>
> I guess the biggest reason is, most people tag a patch with stable without
> specifying kernel versions, and if this patch can't be applied to 3.4, it
> will be dropped silently. I guess Ben has been checking this kind of patches
> manually.
>
> >> We (our team in Huawei) are going to go through the whole list to filter
> >> out fixes that're applicable for 3.4.xx.
Please do this, I don't have the resources at the moment to be able to
go through all of these git ids to see if they really are relevant or
not right now. Any help that you can provide with this for 3.4 or 3.10
would be most appreciated.
thanks,
greg k-h
prev parent reply other threads:[~2014-01-15 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 7:28 [STABLE] find missing bug fixes in a stable kernel Li Zefan
2014-01-13 9:38 ` Jack Wang
2014-01-14 1:45 ` Li Zefan
2014-01-13 15:57 ` Greg Kroah-Hartman
2014-01-14 1:37 ` Li Zefan
2014-01-15 4:06 ` Greg Kroah-Hartman [this message]
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=20140115040642.GA16810@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).