linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikado <mikado4vn@yahoo.com>
To: linux-kernel@vger.kernel.org, linux-c-programming@vger.kernel.org
Subject: How to obtain process ID that created a packet
Date: Mon, 26 Dec 2005 08:22:18 -0800 (PST)	[thread overview]
Message-ID: <20051226162218.78162.qmail@web53704.mail.yahoo.com> (raw)

Hi,

Is there any way to catch REAL pid that generated a packet from 'struct sk_buff', 'struct sock',
'struct socket',
'struct file' or etc... ? direct/indirect ways are accepted.

Thank you!


	
		
__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/

             reply	other threads:[~2005-12-26 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 16:22 Mikado [this message]
2005-12-26 22:36 ` How to obtain process ID that created a packet Jan Engelhardt
2005-12-27  1:47   ` Mikado
2005-12-27  8:26     ` Jan Engelhardt
2005-12-27 10:55       ` Michael Tokarev
2005-12-27 18:03         ` Jan Engelhardt

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=20051226162218.78162.qmail@web53704.mail.yahoo.com \
    --to=mikado4vn@yahoo.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=linux-kernel@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).