From: Alexander Lochmann <alexander.lochmann@tu-dortmund.de>
To: systemtap@sourceware.org
Subject: Blacklist regex is too general
Date: Tue, 12 Apr 2016 09:12:00 -0000 [thread overview]
Message-ID: <570CBC09.2080608@tu-dortmund.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 740 bytes --]
Hi folks!
I've wanted to measure the impact of packet duplication due to a raw socket.
To do so, I have to probe the kernel function 'raw_v4_input' in
net/ipv4/raw.c.
Unfortunately, the function name matches the regex defined at
dwflpp:4324, which is: blfn += "|raw_.*";.
On my opinion, the regex is too general, and there is no reason why it
shouldn't be allowed to probe 'raw_v4_input'.
It therefore might be necessary to rephrase the mentioned regex. :)
Cheers,
Alex
--
Technische Universität Dortmund
Alexander Lochmann PGP key: 0xBC3EF6FD
Otto-Hahn-Str. 16 phone: +49.231.7556141
D-44227 Dortmund fax: +49.231.7556116
http://ess.cs.tu-dortmund.de/Staff/al
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-04-12 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 9:12 Alexander Lochmann [this message]
2016-04-12 15:42 ` David Smith
2016-04-12 15:46 ` Alexander Lochmann
2016-04-13 15:13 ` David Smith
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=570CBC09.2080608@tu-dortmund.de \
--to=alexander.lochmann@tu-dortmund.de \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).