From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: [0/2] netfilter: ctnetlink fixes for 2.6.29-rc
Date: Tue, 27 Jan 2009 22:14:51 +0100 [thread overview]
Message-ID: <497F794B.3080302@netfilter.org> (raw)
Hi Patrick,
The following patches contains to ctnetlink fixes for 2.6.29-rc:
[1/2] netfilter: ctnetlink: allow changing NAT sequence adjustment in
creation
[2/2] netfilter: ctnetlink: fix echo if not subscribed to any multicast
group
The first patch fixes an inconsistency in the ctnetlink code, as the NAT
sequence adjustment bits may also be mangled in the creation path. The
second fixes netlink echoing if the socket is not subscribed to any
multicast group since currently the socket does not receive anything
back if NLM_F_ECHO is set.
Please, could you pass them to davem?
Thanks!
--
"Los honestos son inadaptados sociales" -- Les Luthiers
reply other threads:[~2009-01-27 21:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=497F794B.3080302@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).