linux-kernel - Re: [PATCH 00/25] vfs: atomic open RFC

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:	Wed, 7 Mar 2012 15:27:14 -0600
From:	Steve French <smfrench@...il.com>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, hch@...radead.org,
	Trond.Myklebust@...app.com, sfrench@...ba.org, sage@...dream.net,
	ericvh@...il.com, mszeredi@...e.cz
Subject: Re: [PATCH 00/25] vfs: atomic open RFC

On Wed, Mar 7, 2012 at 3:22 PM, Miklos Szeredi <miklos@...redi.hu> wrote:
> This series allows clean implementation of atomic lookup+(create)+open and
> create+open operations that previously were done via ->lookup and ->create using
> open intents.
>
> Testing and review is welcome, but at this stage mainly I'd like to hear
> opinions on the overall design of the new interfaces.

This could be great for network file systems like cifs/smb2

Historically mapping the multistage lookup/create/open to an atomic
opencreate protocol operation (for cifs, and now smb2 and smb2.2)
has always been hard.   We go from an atomic syscall to
lookup intents, but it was tricky to make this atomic on the wire in every case.

It will be interesting to review this.

-- 
Thanks,

Steve
--
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/