From: jamal <hadi@cyberus.ca>
To: Thomas Graf <tgraf@suug.ch>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: PATCH: rtnetlink explicit flags setting
Date: Fri, 27 May 2005 21:48:13 -0400 [thread overview]
Message-ID: <1117244893.6251.41.camel@localhost.localdomain> (raw)
In-Reply-To: <20050528012810.GN15391@postel.suug.ch>
On Sat, 2005-28-05 at 03:28 +0200, Thomas Graf wrote:
> * jamal <1117242749.6251.15.camel@localhost.localdomain> 2005-05-27 21:12
> > > Yet unconverted
> > > are: netfilter, net/sched/ tcp_diag, xfrm, kernel/audit.
> > >
> >
> > I didnt find any issues with these as far as PID extrapolation.
>
> I should have written, yet unchecked.
>
I did check netfilter, net/sched/ tcp_diag, xfrm and they do things
right.
> > > Do not apply these patches yet, they're way too intrusive
> >
> > Do you mean the two patches? Those looked fine to me;
>
> Yes, those two patches. My part comes directly out of my fingers
> and is only compile tested. I didn't even run them yet.
>
Hrm - you should probably have said that in the patch text ;->
I did test the one i sent - basic things and by code inspection saw
little risk as well. Perhaps we should push mine then you can add on top
of it.
> > i.e its mostly the patch i posted this morning with the new Macros, no?
>
> I went through all users of NLMSG_PUT in the modules you touched and
> checked if they properly set NLM_F_MULTI and used the new macro when
> appropriate.
>
> Anyways, I want to be careful with this, there might be userspace
> apps which rely on pid being filled in from siocb->scm->creds or
> userspace apps which don't expect the NLM_F_MULTI flag even when
> they should so we should check with all parties involved.
>
I dont see any issues with my original patch or for that matter yours
except for now that you are saying you havent compiled it even ;->.
All dumps MUST set NLM_F_MULTI - thats the main change really.
All non-dump paths may set NLM_F_MULTI, and from that angle, if theres
any bugs in the old code they are maintained ;->
So how about we push my original patch instead?
cheers,
jamal
next prev parent reply other threads:[~2005-05-28 1:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 12:32 PATCH: rtnetlink explicit flags setting jamal
2005-05-27 12:50 ` Thomas Graf
2005-05-27 13:58 ` jamal
2005-05-27 14:13 ` Thomas Graf
2005-05-27 15:01 ` jamal
2005-05-27 15:19 ` Thomas Graf
2005-05-27 15:57 ` jamal
2005-05-27 16:59 ` Thomas Graf
2005-05-27 17:00 ` [PATCH 1/2] [NETLINK] Introduce NLMSG_NEW macro to better handle netlink flags Thomas Graf
2005-05-27 17:01 ` [PATCH 2/2] [NETLINK] Correctly set NLM_F_MULTI without checking the pid Thomas Graf
2005-05-28 1:06 ` jamal
2005-05-31 22:37 ` David S. Miller
2005-05-28 1:12 ` PATCH: rtnetlink explicit flags setting jamal
2005-05-28 1:28 ` Thomas Graf
2005-05-28 1:48 ` jamal [this message]
2005-05-28 12:18 ` Thomas Graf
2005-05-28 16:00 ` jamal
2005-05-28 16:16 ` Thomas Graf
2005-05-31 9:39 ` jamal
2005-05-31 9:41 ` who 王海
2005-05-31 21:43 ` PATCH: rtnetlink explicit flags setting David S. Miller
2005-05-31 22:26 ` Thomas Graf
2005-05-31 22:31 ` David S. Miller
2005-06-02 13:04 ` PATCH: explicit typing WAS(Re: " jamal
2005-06-02 13:30 ` jamal
2005-06-03 5:08 ` David S. Miller
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=1117244893.6251.41.camel@localhost.localdomain \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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