All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] note owner match brokenness
Date: Fri, 01 Oct 2004 23:09:37 +0200	[thread overview]
Message-ID: <415DC791.3060409@trash.net> (raw)
In-Reply-To: <20041001204447.GA30390@linuxace.com>

Phil Oester wrote:

>Someone recently complained in bugzilla that the note about owner
>match being broken on SMP took hours to find because it was in
>syslog instead of userspace.  Hopefully the below patch will
>save others some time.
>
>This closes bugzilla #244
>
If we warn in userspace, we should warn when then options are used
instead of in the helptext.

Regards
Patrick

>Phil
>
>
>  
>
>------------------------------------------------------------------------
>
>diff -ru ipt-orig/extensions/libipt_owner.c ipt-new/extensions/libipt_owner.c
>--- ipt-orig/extensions/libipt_owner.c	2004-06-14 15:02:17.000000000 -0700
>+++ ipt-new/extensions/libipt_owner.c	2004-10-01 13:36:50.779263920 -0700
>@@ -22,6 +22,7 @@
> "[!] --pid-owner processid  Match local pid\n"
> "[!] --sid-owner sessionid  Match local sid\n"
> "[!] --cmd-owner name       Match local command name\n"
>+"NOTE: pid, sid and command matching are broken on SMP\n"
> "\n",
> IPTABLES_VERSION);
> #else
>@@ -31,6 +32,7 @@
> "[!] --gid-owner groupid    Match local gid\n"
> "[!] --pid-owner processid  Match local pid\n"
> "[!] --sid-owner sessionid  Match local sid\n"
>+"NOTE: pid and sid matching are broken on SMP\n"
> "\n",
> IPTABLES_VERSION);
> #endif /* IPT_OWNER_COMM */
>  
>

  reply	other threads:[~2004-10-01 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 20:44 [PATCH] note owner match brokenness Phil Oester
2004-10-01 21:09 ` Patrick McHardy [this message]
2004-10-01 21:12   ` Phil Oester
2004-10-01 21:30     ` Patrick McHardy
2004-10-03 19:43       ` Herve Eychenne
2004-10-03 20:36         ` Patrick McHardy

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=415DC791.3060409@trash.net \
    --to=kaber@trash.net \
    --cc=kernel@linuxace.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.