From: Patrick McHardy <kaber@trash.net>
To: Rami Rosen <ramirose@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-2.6] [NETFILTER] Misc Cleanups.
Date: Mon, 02 Jun 2008 13:18:50 +0200 [thread overview]
Message-ID: <4843D71A.5090107@trash.net> (raw)
In-Reply-To: <eb3ff54b0806020411p16531d2chb05061a6d209b406@mail.gmail.com>
Rami Rosen wrote:
> Hi,
> - Thanks for your comments; I was not aware that this issues occur
> in other places too; attached here is another patch, fixing where
> applicable in ip6_queue and nfnetlink_queue.
>
> 1) in net/ipv6/netfilter/ip6_queue.c
> - No need to perform data_len = 0 in the switch command, since data_len
> is initialized to 0 in the beginning of the
> ipq_build_packet_message() method
> - We can reach nlmsg_failure only from one place; skb is sure to be NULL
> when getting there; since skb is NULL, there is no need to check this fact
> and call kfree_skb().
>
> 2) in net/netfilter/nfnetlink_queue.c:
> - No need to perform data_len = 0 in the switch command, since data_len
> is initialized to 0 in the beginning of the
> nfqnl_build_packet_message() method
>
> (Note: here, as opposed to previous patch, nlmsg_failure must check
> skb and free it if it is not NULL, so the call to kfree_skb() is
> needed , so it is not removed)
I've queued this patch and the previous one (without the procfs
bits) as one combined patch for 2.6.27, thanks.
prev parent reply other threads:[~2008-06-02 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 6:45 Fw: [PATCH net-2.6 1/2] [IPV4] [NETFILTER] Misc Cleanups David Miller
2008-06-02 9:46 ` Patrick McHardy
2008-06-02 11:11 ` [PATCH net-2.6] " Rami Rosen
2008-06-02 11:18 ` Patrick McHardy [this message]
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=4843D71A.5090107@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ramirose@gmail.com \
/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.