From: kernel test robot <lkp@intel.com>
To: NeilBrown <neilb@ownmail.net>,
Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>, Jan Kara <jack@suse.cz>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
John Johansen <john.johansen@canonical.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
apparmor@lists.ubuntu.com, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: [PATCH 04/13] Apparmor: Use simple_start_creating() / simple_done_creating()
Date: Wed, 4 Feb 2026 18:58:08 +0800 [thread overview]
Message-ID: <202602041851.x2RfFgKO-lkp@intel.com> (raw)
In-Reply-To: <20260204050726.177283-5-neilb@ownmail.net>
Hi NeilBrown,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on viro-vfs/for-next linus/master v6.19-rc8 next-20260203]
[cannot apply to pcmoore-selinux/next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/NeilBrown/fs-proc-Don-t-lock-root-inode-when-creating-self-and-thread-self/20260204-131659
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20260204050726.177283-5-neilb%40ownmail.net
patch subject: [PATCH 04/13] Apparmor: Use simple_start_creating() / simple_done_creating()
config: arm-randconfig-r133-20260204 (https://download.01.org/0day-ci/archive/20260204/202602041851.x2RfFgKO-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260204/202602041851.x2RfFgKO-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202602041851.x2RfFgKO-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> security/apparmor/apparmorfs.c:295:16: sparse: sparse: Using plain integer as NULL pointer
vim +295 security/apparmor/apparmorfs.c
247
248 /**
249 * aafs_create - create a dentry in the apparmorfs filesystem
250 *
251 * @name: name of dentry to create
252 * @mode: permissions the file should have
253 * @parent: parent directory for this dentry
254 * @data: data to store on inode.i_private, available in open()
255 * @link: if symlink, symlink target string
256 * @fops: struct file_operations that should be used for
257 * @iops: struct of inode_operations that should be used
258 *
259 * This is the basic "create a xxx" function for apparmorfs.
260 *
261 * Returns a pointer to a dentry if it succeeds, that must be free with
262 * aafs_remove(). Will return ERR_PTR on failure.
263 */
264 static struct dentry *aafs_create(const char *name, umode_t mode,
265 struct dentry *parent, void *data, void *link,
266 const struct file_operations *fops,
267 const struct inode_operations *iops)
268 {
269 struct dentry *dentry;
270 struct inode *dir;
271 int error;
272
273 AA_BUG(!name);
274 AA_BUG(!parent);
275
276 if (!(mode & S_IFMT))
277 mode = (mode & S_IALLUGO) | S_IFREG;
278
279 error = simple_pin_fs(&aafs_ops, &aafs_mnt, &aafs_count);
280 if (error)
281 return ERR_PTR(error);
282
283 dir = d_inode(parent);
284
285 dentry = simple_start_creating(parent, name);
286 if (IS_ERR(dentry)) {
287 error = PTR_ERR(dentry);
288 goto fail;
289 }
290
291 error = __aafs_setup_d_inode(dir, dentry, mode, data, link, fops, iops);
292 simple_done_creating(dentry);
293 if (error)
294 goto fail;
> 295 return 0;
296 fail:
297 simple_release_fs(&aafs_mnt, &aafs_count);
298 return ERR_PTR(error);
299 }
300
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-04 10:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 4:57 [PATCH 00/13] Further centralising of directory locking for name ops NeilBrown
2026-02-04 4:57 ` [PATCH 01/13] fs/proc: Don't lock root inode when creating "self" and "thread-self" NeilBrown
2026-02-05 12:33 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 02/13] VFS: move the start_dirop() kerndoc comment to before start_dirop() NeilBrown
2026-02-05 12:33 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 03/13] libfs: change simple_done_creating() to use end_creating() NeilBrown
2026-02-05 12:19 ` Jeff Layton
2026-02-06 2:13 ` NeilBrown
2026-02-04 4:57 ` [PATCH 04/13] Apparmor: Use simple_start_creating() / simple_done_creating() NeilBrown
2026-02-04 10:58 ` kernel test robot [this message]
2026-02-05 12:58 ` Jeff Layton
2026-02-06 0:21 ` NeilBrown
2026-02-04 4:57 ` [PATCH 05/13] selinux: " NeilBrown
2026-02-05 12:36 ` Jeff Layton
2026-02-20 22:47 ` Paul Moore
2026-02-21 22:28 ` NeilBrown
2026-02-22 14:19 ` Paul Moore
2026-02-23 0:58 ` NeilBrown
2026-02-04 4:57 ` [PATCH 06/13] nfsd: switch purge_old() to use start_removing_noperm() NeilBrown
2026-02-05 12:36 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 07/13] VFS: make lookup_one_qstr_excl() static NeilBrown
2026-02-05 12:37 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 08/13] ovl: Simplify ovl_lookup_real_one() NeilBrown
2026-02-05 12:38 ` Jeff Layton
2026-02-05 13:04 ` Amir Goldstein
2026-02-06 0:43 ` NeilBrown
2026-02-04 4:57 ` [PATCH 09/13] cachefiles: change cachefiles_bury_object to use start_renaming_dentry() NeilBrown
2026-02-05 12:38 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 10/13] ovl: change ovl_create_real() to get a new lock when re-opening created file NeilBrown
2026-02-05 12:26 ` Amir Goldstein
2026-02-06 1:11 ` NeilBrown
2026-02-06 13:35 ` Amir Goldstein
2026-02-04 4:57 ` [PATCH 11/13] ovl: use is_subdir() for testing if one thing is a subdir of another NeilBrown
2026-02-05 9:37 ` Amir Goldstein
2026-02-05 12:38 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 12/13] ovl: remove ovl_lock_rename_workdir() NeilBrown
2026-02-05 9:45 ` Amir Goldstein
2026-02-06 1:18 ` NeilBrown
2026-02-05 12:40 ` Jeff Layton
2026-02-05 12:58 ` Jeff Layton
2026-02-04 4:57 ` [PATCH 13/13] VFS: unexport lock_rename(), lock_rename_child(), unlock_rename() NeilBrown
2026-02-05 12:41 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202602041851.x2RfFgKO-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=apparmor@lists.ubuntu.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neilb@ownmail.net \
--cc=netfs@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox