From: David Miller <davem@davemloft.net>
To: leonerd@leonerd.org.uk
Cc: netdev@vger.kernel.org
Subject: Re: RFC: New BGF 'LOOP' instruction
Date: Mon, 02 Aug 2010 22:13:41 -0700 (PDT) [thread overview]
Message-ID: <20100802.221341.137851732.davem@davemloft.net> (raw)
In-Reply-To: <20100802110334.GK11110@cel.leo>
From: Paul LeoNerd Evans <leonerd@leonerd.org.uk>
Date: Mon, 2 Aug 2010 12:03:34 +0100
> Any comments on this, while I proceed? Barring any major complaints,
> I'll have a hack at some code and present a patch in due course...
We're not adding loop instructions, it's just asking for trouble
since any user can attach BPF filters to a socket and it's just
way too easy to make a loop endless.
There's a reason no loop primitives were added to the original
BPF specification, perhaps you should take a look at what their
reasoning was.
It still applies now.
next prev parent reply other threads:[~2010-08-03 5:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 11:03 RFC: New BGF 'LOOP' instruction Paul LeoNerd Evans
2010-08-02 11:13 ` RFC: New BPF " Paul LeoNerd Evans
2010-08-02 20:16 ` RFC: New BGF " Hagen Paul Pfeifer
2010-08-03 5:18 ` David Miller
2010-08-03 7:07 ` Paul LeoNerd Evans
2010-08-03 7:19 ` David Miller
2010-08-03 9:10 ` Hagen Paul Pfeifer
2010-08-03 13:40 ` Paul LeoNerd Evans
2010-08-03 9:03 ` Hagen Paul Pfeifer
2010-08-03 7:18 ` RFC: New BPF " Paul LeoNerd Evans
2010-08-03 5:13 ` David Miller [this message]
2010-08-03 7:04 ` RFC: New BGF " Paul LeoNerd Evans
2010-08-03 7:18 ` David Miller
2010-08-03 12:58 ` Andi Kleen
2010-08-03 13:07 ` David Miller
2010-08-03 13:34 ` RFC: New BPF " Paul LeoNerd Evans
2010-08-03 13:42 ` Paul LeoNerd Evans
2010-08-03 14:09 ` Rémi Denis-Courmont
2010-08-03 14:13 ` Paul LeoNerd Evans
2010-08-03 14:16 ` Rémi Denis-Courmont
2010-08-03 14:19 ` Paul LeoNerd Evans
2010-08-03 15:17 ` Rémi Denis-Courmont
2010-08-03 15:27 ` Paul LeoNerd Evans
2010-08-03 14:05 ` RFC: New BGF " Andi Kleen
2010-08-03 14:11 ` Paul LeoNerd Evans
2010-08-03 14:34 ` Paul LeoNerd Evans
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=20100802.221341.137851732.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=leonerd@leonerd.org.uk \
--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).