From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Simon Horman <horms@verge.net.au>, Julian Anastasov <ja@ssi.bg>,
Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
lvs-devel@vger.kernel.org
Subject: [net PATCH 0/2] Fixing OOPSes in seqadj code
Date: Mon, 16 Dec 2013 17:09:36 +0100 [thread overview]
Message-ID: <20131216160840.22853.39918.stgit@dragon> (raw)
In-Reply-To: <20131213214023.14478.74738.stgit@dragon>
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(-)
next prev parent reply other threads:[~2013-12-16 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 21:37 [PATCH] ipvs: avoid oops in nf_ct_seqadj_set when called from ip_vs_ftp helper Jesper Dangaard Brouer
2013-12-14 22:25 ` Julian Anastasov
2013-12-15 16:10 ` Julian Anastasov
2013-12-16 14:57 ` Jesper Dangaard Brouer
2013-12-16 21:05 ` Julian Anastasov
2013-12-16 16:09 ` Jesper Dangaard Brouer [this message]
2013-12-16 16:09 ` [net PATCH 1/2] netfilter: WARN about wrong usage of sequence number adjustments Jesper Dangaard Brouer
2013-12-16 16:09 ` [net PATCH 2/2] ipvs: correct usage/allocation of seqadj ext in ipvs Jesper Dangaard Brouer
2013-12-16 21:11 ` [net PATCH 0/2] Fixing OOPSes in seqadj code Julian Anastasov
2013-12-17 1:36 ` Simon Horman
2013-12-27 3:23 ` Simon Horman
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=20131216160840.22853.39918.stgit@dragon \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.