From: David Miller <davem@davemloft.net>
To: alex.williamson@hp.com
Cc: maxk@qualcomm.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] tun: Fix unicast filter overflow
Date: Sun, 08 Feb 2009 17:48:54 -0800 (PST) [thread overview]
Message-ID: <20090208.174854.51245719.davem@davemloft.net> (raw)
In-Reply-To: <1234143837.20601.11.camel@2710p.home>
From: Alex Williamson <alex.williamson@hp.com>
Date: Sun, 08 Feb 2009 18:43:57 -0700
> Sure, that's another option, but we'd then need to figure out what to do
> with TUN_FLT_ALLMULTI. Unicast would almost needs it's own hash list if
> we want to support an allmulti mode that's less than promiscuous. The
> return value of the ioctl is the number of exact filters, so the user
> will know what happened.
Oh so that's what the return value means.
Ok, I guess for now your patch is fine, I'll apply it and
queue it up for -stable, thanks!
prev parent reply other threads:[~2009-02-09 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 17:45 [PATCH] tun: Fix unicast filter overflow Alex Williamson
2009-02-09 1:06 ` David Miller
2009-02-09 1:43 ` Alex Williamson
2009-02-09 1:48 ` David Miller [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=20090208.174854.51245719.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.williamson@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=netdev@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).