Messages in this thread | | | Subject | Re: [PATCH 4/4] [RFC] ipv6: Fix for possible ipv6 seqlock deadlock | From | Eric Dumazet <> | Date | Fri, 27 Sep 2013 10:51:17 -0700 |
| |
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.
Documentation/networking/netdev-FAQ.txt
Q: I see a network patch and I think it should be backported to stable. Should I request it via "stable@vger.kernel.org" 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.
| |