[lkml]   [2013]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/4] [RFC] ipv6: Fix for possible ipv6 seqlock deadlock
On Fri, 2013-09-27 at 09:00 -0700, John Stultz wrote:

> It seems as such, so I'll add stable on my next submission.


Q: I see a network patch and I think it should be backported to stable.
Should I request it via "" like the references in
the kernel's Documentation/stable_kernel_rules.txt file say?

A: No, not for networking. Check the stable queues as per above 1st to see
if it is already queued. If not, then send a mail to netdev, listing
the upstream commit ID and why you think it should be a stable candidate.

Before you jump to go do the above, do note that the normal stable rules
in Documentation/stable_kernel_rules.txt still apply. So you need to
explicitly indicate why it is a critical fix and exactly what users are
impacted. In addition, you need to convince yourself that you _really_
think it has been overlooked, vs. having been considered and rejected.

Generally speaking, the longer it has had a chance to "soak" in mainline,
the better the odds that it is an OK candidate for stable. So scrambling
to request a commit be added the day after it appears should be avoided.

 \ /
  Last update: 2013-09-27 20:21    [W:0.065 / U:4.784 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site