From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Backporting stacked security patch
Date: Tue, 30 Oct 2018 17:17:45 -0400 [thread overview]
Message-ID: <101273.1540934265@turing-police.cc.vt.edu> (raw)
In-Reply-To: <33839821540923548@myt3-c573aa6fc782.qloud-c.yandex.net>
On Tue, 30 Oct 2018 21:19:08 +0300, Lev Olshvang said:
> As I stated, I have no option to come to customer and ask to upgrade his
> kernel, but I will try to put his attention to mentioned by you cease of
> security updates.
If you can't get him to upgrade the installed kernel, it's not worth your effort
to backport patches. And just updating the patches to the 4.2 level doesn't
do your customer any favors, as there's been a lot of security patches
between 4.2 and 4.19.
And many of the important ones do *NOT* apply to the security/ branch of
the tree - it's stuff like the Spectre fixes that show up elsewhere in the tree,
networking fixes that resolve "packet of death" issues, and so on.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181030/70f0f4ef/attachment.sig>
next prev parent reply other threads:[~2018-10-30 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 11:43 Backporting stacked security patch Lev Olshvang
2018-10-30 14:33 ` Greg KH
2018-10-30 18:19 ` Lev Olshvang
2018-10-30 21:17 ` valdis.kletnieks at vt.edu [this message]
2018-10-31 6:50 ` Greg KH
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=101273.1540934265@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).