stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henri Rosten <henri.rosten@unikie.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, lukas.bulwahn@gmail.com
Subject: Re: Patches potentially missing from stable releases
Date: Fri, 29 May 2020 20:52:02 +0300	[thread overview]
Message-ID: <20200529175202.GA10030@buimax> (raw)
In-Reply-To: <20200529124655.GA1714108@kroah.com>

On Fri, May 29, 2020 at 02:46:55PM +0200, Greg KH wrote:
> On Fri, May 29, 2020 at 03:24:47PM +0300, Henri Rosten wrote:
> > We did some work on analyzing patches potentially missing from stable 
> > releases based on the Fixes: and Revert references in the commit 
> > messages. Our script is based on similar idea as described by Guenter 
> > Roeck in this earlier mail: 
> > https://lore.kernel.org/stable/20190827171621.GA30360@roeck-us.net/.
> > 
> > Although the list is not comprehensive, we figured it makes sense to 
> > publish it in case the results are of interest to someone else also.
> > 
> > The below list of potentially missing commits is based on 4.19, but some 
> > of the commits might also apply to 5.4 and 5.6.
> > 
> > For each potentially missing commit flagged by the script, we read the 
> > commit message and had a short look at the change. We then added 
> > comments on our own judgement if it might be stable material or not. No 
> > comments simply means the potentially missing patch appears stable 
> > material. "Based on commit" is the mainline patch that has been 
> > backported to 4.19 and is referenced by the missing commit. We did not 
> > check if the patch applies without changes, nor did we build or execute 
> > any tests.
> 
> That last sentence should have been a huge red flag when writing it and
> sending out this email...

Thank you for your comments.

This list was a byproduct of other analysis we did, I did not intent to 
ask these patches for inclusion into stable. We simply wanted to report 
this list in case it includes some patches that might have dropped off 
your radar. We are aware that such information without further work, 
e.g. backporting and testing does not add much yet.

Thanks,
-- Henri


  reply	other threads:[~2020-05-29 17:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 12:24 Patches potentially missing from stable releases Henri Rosten
2020-05-29 12:46 ` Greg KH
2020-05-29 17:52   ` Henri Rosten [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-27 17:16 Guenter Roeck
2019-08-27 18:10 ` Sasha Levin
2019-08-27 20:01   ` Guenter Roeck
2019-08-27 20:29     ` Greg Kroah-Hartman
2019-08-27 20:48       ` Guenter Roeck
2019-08-28  8:41         ` Greg Kroah-Hartman
2019-08-28 13:43           ` Guenter Roeck
2019-08-28 14:54             ` Greg Kroah-Hartman
2019-08-28 19:59               ` Guenter Roeck
2019-08-28 12:22     ` Sasha Levin
2019-08-29 11:00       ` Sasha Levin
2019-08-29 13:44         ` Guenter Roeck

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=20200529175202.GA10030@buimax \
    --to=henri.rosten@unikie.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lukas.bulwahn@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 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).