From: David Miller <davem@davemloft.net>
To: lk-netdev@lk-netdev.nosense.org
Cc: netdev@vger.kernel.org, pekkas@netcore.fi, yoshfuji@linux-ipv6.org
Subject: Re: [patch] ipv6: correct return on ipv6_rcv() packet drop
Date: Mon, 06 Jul 2009 18:09:45 -0700 (PDT) [thread overview]
Message-ID: <20090706.180945.113737445.davem@davemloft.net> (raw)
In-Reply-To: <20090707065624.ee55809e.lk-netdev@lk-netdev.nosense.org>
From: Mark Smith <lk-netdev@lk-netdev.nosense.org>
Date: Tue, 7 Jul 2009 06:56:24 +0930
> The routine ipv6_rcv() uses magic number 0 for a return when it drops a
> packet. This corresponds to NET_RX_SUCCESS, which is obviously
> incorrect. Correct this by using NET_RX_DROP instead.
>
> ps. It isn't exactly clear who the IPv6 maintainers are, apologies if
> I've missed any.
>
> Signed-off-by: Mark Smith <markzzzsmith@yahoo.com.au>
Applied.
next prev parent reply other threads:[~2009-07-07 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 21:26 [patch] ipv6: correct return on ipv6_rcv() packet drop Mark Smith
2009-07-07 1:09 ` David Miller [this message]
2009-07-07 9:20 ` Mark Smith
2009-07-07 15:52 ` David Miller
2009-07-07 21:04 ` Mark Smith
2009-07-08 1:34 ` David Miller
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=20090706.180945.113737445.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lk-netdev@lk-netdev.nosense.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.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).