From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Andi Kleen <ak@suse.de>
Cc: kuznet@ms2.inr.ac.ru, jt@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: Multicast netlink for non-root process
Date: Tue, 11 Jun 2002 16:55:16 -0700 [thread overview]
Message-ID: <20020611165516.B23007@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020611141330.A22927@bougret.hpl.hp.com> <200206112140.BAA14401@sex.inr.ac.ru> <20020612013101.A22399@wotan.suse.de>
On Wed, Jun 12, 2002 at 01:31:01AM +0200, Andi Kleen wrote:
> On Wed, Jun 12, 2002 at 01:40:45AM +0400, A.N.Kuznetsov wrote:
> > Hello!
> >
> > > One potential reason is that some of the message may contain
> > > data that is root only. But this should be handled with a finer
> > > granularity.
> >
> > Exactly. Taking into account that it is not handled with a finer granularity,
> > it is restricted in a facsict manner.
>
> The only problematic protocols are nf_queue and the firewall netlink I guess.
>
> This (barely tested) patch should relax it for rtnetlink at least:
The path works fine here. At least, my non-root app get all
the event proper.
Thanks a lot for your quick turnaround. I hope it will show up
in 2.5.X someday ;-)
Jean
next prev parent reply other threads:[~2002-06-11 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020611134418.A22893@bougret.hpl.hp.com.suse.lists.linux.kernel>
2002-06-11 21:02 ` Andi Kleen
2002-06-11 21:13 ` Jean Tourrilhes
2002-06-11 21:23 ` Andi Kleen
2002-06-11 21:40 ` kuznet
2002-06-11 23:31 ` Andi Kleen
2002-06-11 23:55 ` Jean Tourrilhes [this message]
2002-06-12 4:25 ` James Morris
2002-06-12 17:25 ` kuznet
2002-06-12 17:45 ` James Morris
2002-06-12 17:54 ` kuznet
2002-06-12 22:53 ` David S. Miller
2002-06-11 20:44 Jean Tourrilhes
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=20020611165516.B23007@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=ak@suse.de \
--cc=jt@hpl.hp.com \
--cc=kuznet@ms2.inr.ac.ru \
--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
all inboxes | Powered by JetHome®