From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Subject: Re: Owner match misnaming
Date: Mon, 11 Jul 2005 13:12:52 +0100 [thread overview]
Message-ID: <datno8$gft$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0507111401170.14796@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> Hi,
>
>
> |OWNER match v1.3.1 options:
> |[!] --uid-owner userid Match local uid
> |[!] --gid-owner groupid Match local gid
>
> After analyzing the kernel part because some packets obviously did not match
> my rules, I notice that these are in reality the socket owner's uid, and not
> the process's uid.
>
> I already started a patch to add process [ug]{,e,s,fs}id to the owner
> kernel and user modules, but according to the comments in the kernel code,
> they would just be as SMP-unsafe as the pid/sid/comm code.
>
> Ideas? Why, after all, is this the case?
> BTW,
> /* files->file_lock can not be used in a BH */
> a BH is a buffer head, at least in the linux kernel...
I think BH means bottom-half, referring to the work-side of an
interrupt. I read
http://library.n0i.net/linux-unix/administration/unreliable-guides/kernel-locking/lklockingguide.html
or http://www.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/
They talk about the differnt contraints and BH
Azez
next prev parent reply other threads:[~2005-07-11 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 12:04 Owner match misnaming Jan Engelhardt
2005-07-11 12:12 ` Amin Azez [this message]
2005-07-11 18:44 ` Jan Engelhardt
2005-07-12 9:17 ` Harald Welte
2005-07-16 16:29 ` Patrick McHardy
2005-07-16 16:45 ` 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='datno8$gft$1@sea.gmane.org' \
--to=azez@ufomechanic.net \
--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.