linux-kernel - Re: [PATCH 21/25] gfs2: use i_op->atomic

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]

Date:	Sat, 24 Mar 2012 16:38:33 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, Trond.Myklebust@...app.com,
	sfrench@...ba.org, sage@...dream.net, ericvh@...il.com,
	mszeredi@...e.cz
Subject: Re: [PATCH 21/25] gfs2: use i_op->atomic_create()

On Sat, Mar 24, 2012 at 3:27 PM, Christoph Hellwig <hch@...radead.org> wrote:
> On Wed, Mar 07, 2012 at 10:22:38PM +0100, Miklos Szeredi wrote:
>> From: Miklos Szeredi <mszeredi@...e.cz>
>>
>> GFS2 doesn't open the file in ->create, but it does check the LOOKUP_EXCL flag
>> in it's create function.  Convert to using ->atomic_create and checking O_EXCL
>> so that the nameidata argument is no longer necessary.
>
> It seems odd that we require implementing ->atomic_create even if we
> don't actually do an atomic create but just want to look at the flags.
>
> In fact I wonder if we really need to bother with having ->atomic_create
> and ->create, or if we should have one method (kinda contra my previous
> stance that ->atomic_open and ->atomic_create should be one).
>
> This method then could or could not return a file pointer, but it would
> always be the entry point for creates.

Yes, except I thought of the pain of converting all those returns to
ERR_PTR and left the old ->create instead.

Maybe I should just byte the bullet or do that, having a single return
point for those functions shouldn't be that difficult to do.

Thanks,
Miklos
--
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/