From: Dave Jones <davej@redhat.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH trinity] net: add generation of semi-random BPF filters
Date: Thu, 16 May 2013 12:26:19 -0400 [thread overview]
Message-ID: <20130516162619.GA22510@redhat.com> (raw)
In-Reply-To: <51950355.7090602@redhat.com>
On Thu, May 16, 2013 at 06:03:33PM +0200, Daniel Borkmann wrote:
> On 05/16/2013 03:55 PM, Dave Jones wrote:
> > On Thu, May 16, 2013 at 11:54:16AM +0200, Daniel Borkmann wrote:
> > > BPF filters are used in networking and in application sand-boxing
> > > and even have a arch-dependant JIT compiler in the kernel, so add
> > > a more detailed semi-random BPF generator.
> > >
> > > Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
> > > ---
> > > Compile-tested only!
> >
> > Very nice.
> >
> > merged and pushed.
>
> Thanks, just for the record, in case someone might need this e.g. when
> trinity hits here ... in the kernel source tree under tools/net/ is a
> BPF JIT disassembler.
Hmm, I suppose at some point I should add some way of dumping page_rand too.
Given that can be changed by multiple processes at the same time though,
it's a bit of a mess. Also it would be spamming the hell out of the logs.
Perhaps instead of page_rand, the bpf code should do it's own allocation
and then we have a pre-do-syscall hook to do hexdumping of allocations.
This is another case where we really need some post-syscall cleanup operations
too, to free the allocation. (There are a few of these, grep for leak in syscalls/)
I'm probably going to cut a 1.2 release later this month when I get back
from vacation, because it's been a while, and things are pretty quiet right now,
and this stuff is probably going to be for after that.
Dave
prev parent reply other threads:[~2013-05-16 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 9:54 [PATCH trinity] net: add generation of semi-random BPF filters Daniel Borkmann
2013-05-16 13:55 ` Dave Jones
2013-05-16 16:03 ` Daniel Borkmann
2013-05-16 16:26 ` Dave Jones [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=20130516162619.GA22510@redhat.com \
--to=davej@redhat.com \
--cc=dborkman@redhat.com \
--cc=trinity@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