From: Nick Hay <nickjhay@hotmail.com>
To: netfilter-devel@lists.netfilter.org
Subject: Extending LOG target to display pid
Date: Wed, 06 Jul 2005 04:05:54 +1200 [thread overview]
Message-ID: <42CAAFE2.3050606@hotmail.com> (raw)
What I hoped to be an easy hack quickly ran into problems. I planned to
add an extra printk() in dump_packet() to output the pid, and perhaps
the program executable number. Since the owner module had access to the
pid, I assumed there would be some way to get this information to the
LOG module. After a frustrating search through source code and
documentation, I have the following questions:
1. For the owner module, where/how is the struct ipt_owner_info filled
in for each packet? In general, how is the ipt_entry_match/target data
field filled in?
2. Any ideas on how I can get the pid of a local packet's creator in the
log module? I couldn't find any structures connected to the sk_buff
that might contain it, and couldn't think of where the data would
originally come from.
Actually... would current->pid work?
I'm still curious about question 1, though!
-- Nick Hay
next reply other threads:[~2005-07-05 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 16:05 Nick Hay [this message]
2005-07-05 17:28 ` Extending LOG target to display pid Tobias DiPasquale
2005-07-05 18:05 ` Juha Heljoranta
-- strict thread matches above, loose matches on Subject: below --
2005-07-05 23:56 Nick Hay
2005-07-07 6:32 ` Jonas Berlin
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=42CAAFE2.3050606@hotmail.com \
--to=nickjhay@hotmail.com \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.