Fixing OOPSes in seqadj code
Get series with b4
b4 am 20131216160840.22853.39918.stgit@dragonVersions newest first
- v1 Latest2 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | netfilter: WARN about wrong usage of sequence number adjustmentsnet/ | +5 | 0 replies | |
| 2/2 | ipvs: correct usage/allocation of seqadj ext in ipvsnet/ | +6 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Julian Anastasov |
|---|---|
| Series | A-b |
| 1/2 | |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [net PATCH 0/2] Fixing OOPSes in seqadj code
The following series address issues with netfilter conntrack sequence number adjustments, introduced with commit 41d73ec053d2 (netfilter:nf_conntrack: make sequence number adjustments usuable without NAT).
Patch1: give us a WARN splash when using seqadj incorrectly
Patch2: fixes a wrong usage of seqadj in IPVS code
I'm not sure, which maintainer will take these fixes?!?
---
Jesper Dangaard Brouer (2):
ipvs: correct usage/allocation of seqadj ext in ipvs
netfilter: WARN about wrong usage of sequence number adjustments
net/netfilter/ipvs/ip_vs_nfct.c | 6 ++++++ net/netfilter/nf_conntrack_seqadj.c | 5 +++++ 2 files changed, 11 insertions(+), 0 deletions(-)