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] [day] [month] [year] [list]
Message-ID: <20250226033506.GE2023217@ZenIV>
Date: Wed, 26 Feb 2025 03:35:06 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: NeilBrown <neilb@...e.de>
Cc: Trond Myklebust <trondmy@...merspace.com>,
	"xiubli@...hat.com" <xiubli@...hat.com>,
	"brauner@...nel.org" <brauner@...nel.org>,
	"idryomov@...il.com" <idryomov@...il.com>,
	"okorniev@...hat.com" <okorniev@...hat.com>,
	"linux-cifs@...r.kernel.org" <linux-cifs@...r.kernel.org>,
	"Dai.Ngo@...cle.com" <Dai.Ngo@...cle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"johannes@...solutions.net" <johannes@...solutions.net>,
	"chuck.lever@...cle.com" <chuck.lever@...cle.com>,
	"jlayton@...nel.org" <jlayton@...nel.org>,
	"anna@...nel.org" <anna@...nel.org>,
	"miklos@...redi.hu" <miklos@...redi.hu>,
	"anton.ivanov@...bridgegreys.com" <anton.ivanov@...bridgegreys.com>,
	"jack@...e.cz" <jack@...e.cz>, "tom@...pey.com" <tom@...pey.com>,
	"richard@....at" <richard@....at>,
	"linux-um@...ts.infradead.org" <linux-um@...ts.infradead.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"netfs@...ts.linux.dev" <netfs@...ts.linux.dev>,
	"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
	"ceph-devel@...r.kernel.org" <ceph-devel@...r.kernel.org>,
	"senozhatsky@...omium.org" <senozhatsky@...omium.org>
Subject: Re: [PATCH 1/6] Change inode_operations.mkdir to return struct
 dentry *

On Wed, Feb 26, 2025 at 02:18:01PM +1100, NeilBrown wrote:

> Thanks.  I'll submit a patch through the VFS tree as I have other VFS
> patches in the works that will depend on that so having them together
> would be good.

Do it on top of mainline, please (say, -rc4) and let's put it into
a separate branch - easier that way to pull it into other branches
without causing headache.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ