linux-kernel - Re: [patch -mm] update mq_notify to use a struct pid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060911154833.GB82@oleg>
Date:	Mon, 11 Sep 2006 19:48:33 +0400
From:	Oleg Nesterov <oleg@...sign.ru>
To:	Cedric Le Goater <clg@...ibm.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>, containers@...ts.osdl.org
Subject: Re: [patch -mm] update mq_notify to use a struct pid

On 09/11, Cedric Le Goater wrote:
>
> Eric W. Biederman wrote:
> > Cedric Le Goater <clg@...ibm.com> writes:
> > 
> >> message queues can signal a process waiting for a message.
> >>
> >> this patch replaces the pid_t value with a struct pid to avoid pid wrap
> >> around problems.
> >>
> >> Signed-off-by: Cedric Le Goater <clg@...ibm.com>
> >> Cc: Eric Biederman <ebiederm@...ssion.com>
> >> Cc: Andrew Morton <akpm@...l.org>
> >> Cc: containers@...ts.osdl.org
> > 
> > Signed-off-by: Eric Biederman <ebiederm@...ssion.com>
> > 
> > I was just about to send out this patch in a couple more hours.
> 
> Well, you did the same with the usb/devio.c and friends :)
> 
> > So expect the fact we wrote the same code is a good sign :)
> 
> How does oleg feel about it ? I've seen some long thread on possible race
> conditions with put_pid() and solutions with rcu. I didn't quite get all of
> it ... it will need another run for me.

I assume you are talking about this patch:
	http://marc.theaimsgroup.com/?l=linux-mm-commits&m=115773820415171

I think it's ok, info->notify_owner is always used under info->lock.

This is simple. If, for example, mqueue_read_file() didn't take info->lock,
then we have a problem: pid_nr() may read a freed memory in case when
__do_notify()->put_pid() happens at the same time.

In this context info->notify_owner is a usual refcounted object, no special
attention is needed.

Oleg.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/