linux-kernel - Re: RFC: Fix f_flags races without the BKL

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: <20090102195446.GJ28946@ZenIV.linux.org.uk>
Date:	Fri, 2 Jan 2009 19:54:46 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Jonathan Corbet <corbet@....net>,
	LKML <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, bfields@...ldses.org,
	xfs-masters@....sgi.com
Subject: Re: RFC: Fix f_flags races without the BKL

On Fri, Jan 02, 2009 at 08:09:03PM +0100, Oleg Nesterov wrote:
> On 01/02, Al Viro wrote:
> >
> > Bloating with mutex is over the top, indeed, but why can't we simply keep
> > a pointer to fasync_struct in there?  Do we ever have a struct file with
> > several fasync_struct?
> 
> pipe_rdwr_fasync() ?

Ho-hum...  Right you are ;-/

FWIW, it's still bloody tempting to try.  How about hlist from struct file
through fasync_struct?  Possibly with reference from fasync_struct back
to the queue it's on, while we are at it - would make fasync_helper simpler...
--
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/