From: Greg KH <greg@kroah.com>
To: Daniel Taylor <Daniel.Taylor@wdc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Future of the -longterm kernel releases (i.e. how we pick them).
Date: Wed, 24 Aug 2011 16:57:44 -0700 [thread overview]
Message-ID: <20110824235744.GA2187@kroah.com> (raw)
In-Reply-To: <25B374CC0D9DFB4698BB331F82CD0CF2E3ED78@wdscexbe08.sc.wdc.com>
On Mon, Aug 15, 2011 at 10:26:54PM -0700, Daniel Taylor wrote:
> For embedded systems, which often have multi- (not just two-) year
> warranties, it sounds like we would then be maintaining the -longterm
> ourselves. The "easy" side of this is that embedded systems don't
> (usually) have users trying to plug in the latest and greatest widget,
> except on external busses, such as USB. So back-porting drivers is
> not generally a big deal. Security patches, OTOH, are a real concern.
> Other than net and drivers/net, which are exposed to non-local attacks,
> are there other subsystems we should watch for security fixes? There
> have, for example, been a lot of security upgrades in /sys, but there's
> also been a lot of restructing for new interfaces and "arch" models,
> which would make back-porting those much more complicated.
You should watch out for all bugfixes, that's the only way to have a
chance at catching all of the issues.
good luck,
greg k-h
next prev parent reply other threads:[~2011-08-24 23:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 4:15 Future of the -longterm kernel releases (i.e. how we pick them) Greg KH
2011-08-15 6:48 ` Jörg-Volker Peetz
2011-08-15 7:06 ` david
2011-08-15 7:16 ` Teck Choon Giam
2011-08-15 7:25 ` david
2011-08-15 7:38 ` Teck Choon Giam
2011-08-15 7:57 ` Jörg-Volker Peetz
2011-08-17 11:07 ` James Courtier-Dutton
2011-08-15 7:19 ` Jörg-Volker Peetz
2011-08-15 7:21 ` david
2011-08-15 14:21 ` Greg KH
2011-08-16 2:26 ` [Stable-review] " Ben Hutchings
2011-08-16 2:56 ` [stable] " Greg KH
2011-08-16 3:31 ` Ben Hutchings
2011-08-16 5:26 ` Daniel Taylor
2011-08-24 23:57 ` Greg KH [this message]
2011-08-15 7:33 ` [Stable-review] " Willy Tarreau
2011-08-15 14:18 ` [stable] " Greg KH
2011-08-15 15:04 ` [stable] " Tim Gardner
2011-08-16 2:09 ` [Stable-review] " Ben Hutchings
2011-08-16 2:57 ` [stable] " Greg KH
2011-08-16 19:26 ` Jeremiah C. Foster
2011-08-16 22:33 ` [stable] " Greg KH
2011-08-17 10:33 ` Jeremiah Foster
2011-08-17 20:20 ` david
2011-08-24 4:47 ` Greg KH
2011-08-24 4:46 ` Greg KH
2011-08-24 13:03 ` Jeremiah Foster
2011-08-16 23:01 ` Tim Bird
2011-08-17 4:58 ` Greg KH
2011-08-17 13:21 ` Mark Brown
2011-08-17 17:33 ` Brian Swetland
2011-08-24 4:57 ` Greg KH
2011-08-25 4:49 ` Brian Swetland
2011-08-26 0:03 ` Greg KH
2011-08-18 0:33 ` [Stable-review] " Ben Hutchings
2011-08-18 11:28 ` Pasi Kärkkäinen
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=20110824235744.GA2187@kroah.com \
--to=greg@kroah.com \
--cc=Daniel.Taylor@wdc.com \
--cc=linux-kernel@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.