From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sasha Levin <sashal@kernel.org>, Michal Hocko <mhocko@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Miaohe Lin <linmiaohe@huawei.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org
Subject: Re: 5.13.2-rc and others have many not for stable
Date: Tue, 13 Jul 2021 09:20:43 +0200 [thread overview]
Message-ID: <YO0+y+verYM2Hrts@kroah.com> (raw)
In-Reply-To: <YO0zXVX9Bx9QZCTs@kroah.com>
On Tue, Jul 13, 2021 at 08:31:57AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Jul 12, 2021 at 10:55:01PM -0700, Hugh Dickins wrote:
> > On Mon, 12 Jul 2021, Greg Kroah-Hartman wrote:
> >
> > > This is the start of the stable review cycle for the 5.13.2 release.
> > > There are 800 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Wed, 14 Jul 2021 06:02:46 +0000.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.13.2-rc1.gz
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.13.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
> > > -------------
> > > Pseudo-Shortlog of commits:
> > >
> > > Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Linux 5.13.2-rc1
> >
> > Hi Greg,
> >
> > Sorry to be making waves, but please, what's up with the 5.13.2-rc,
> > 5.12.17-rc, 5.10.50-rc, 5.4.132-rc stable release candidates?
>
> They show the problem that we currently have where maintainers wait at
> the end of the -rc cycle and keep valid fixes from being sent to Linus.
> They "bunch up" and come out only in -rc1 and so the first few stable
> releases after -rc1 comes out is huge. It's been happening for the past
> few years and only getting worse. These stable releases are proof of
> that, the 5.13.2-rc release was the largest we have ever done and it
> broke one of my scripts because of it :(
>
> I know personally I do this for my subsystems, having fixes that are
> trivial things batch up for -rc1 just because they are generally not
> worth getting into -final. But that is not the case with many other
> subsystems as you can see by these huge patch sequences.
Hm, maybe it really isn't a "problem" here, as the % overall is still
quite low of patches with fixes: and cc: stable on them compared to the
overall number of commits going in for -rc1 vs. later -rcX releases.
So it's just what it is, large numbers of changes happening, small % of
them are needed to be backported. If someone wanted to, odds are they
could get a master's thesis out of analyzing all of this stuff :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-13 7:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 5:55 5.13.2-rc and others have many not for stable Hugh Dickins
2021-07-13 6:31 ` Greg Kroah-Hartman
2021-07-13 7:20 ` Greg Kroah-Hartman [this message]
2021-07-14 1:28 ` Andrew Morton
2021-07-14 7:24 ` Jiri Slaby
2021-07-14 7:52 ` Michal Hocko
2021-07-14 15:30 ` Sasha Levin
2021-07-15 7:07 ` Michal Hocko
2021-07-15 15:57 ` Justin Forbes
2021-07-14 9:18 ` Greg Kroah-Hartman
2021-07-14 13:23 ` Greg Kroah-Hartman
2021-07-14 21:09 ` Andrew Morton
2021-07-15 10:39 ` Mel Gorman
2021-07-14 13:52 ` Sasha Levin
2021-07-14 15:35 ` Theodore Y. Ts'o
2021-07-14 15:43 ` Greg Kroah-Hartman
2021-07-14 15:46 ` Greg Kroah-Hartman
2021-07-14 17:21 ` Theodore Y. Ts'o
2021-07-14 17:34 ` Greg Kroah-Hartman
2021-07-15 9:01 ` Geert Uytterhoeven
2021-07-15 14:47 ` Theodore Y. Ts'o
2021-07-15 15:03 ` Geert Uytterhoeven
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=YO0+y+verYM2Hrts@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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