From: kernel test robot <lkp@intel.com>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/1] ovl: Use fsid as unique identifier for trusted origin
Date: Wed, 15 Oct 2025 03:52:47 +0800 [thread overview]
Message-ID: <202510150318.j2kBtJYC-lkp@intel.com> (raw)
In-Reply-To: <20251014015707.129013-2-andrealmeid@igalia.com>
Hi André,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on linus/master v6.18-rc1 next-20251014]
[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/Andr-Almeida/ovl-Use-fsid-as-unique-identifier-for-trusted-origin/20251014-100119
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20251014015707.129013-2-andrealmeid%40igalia.com
patch subject: [RFC PATCH 1/1] ovl: Use fsid as unique identifier for trusted origin
config: s390-randconfig-001-20251015 (https://download.01.org/0day-ci/archive/20251015/202510150318.j2kBtJYC-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251015/202510150318.j2kBtJYC-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/202510150318.j2kBtJYC-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/overlayfs/copy_up.c: In function 'ovl_encode_real_fh':
>> fs/overlayfs/copy_up.c:431:16: error: assignment to expression with array type
431 | uuid.b = ks.f_fsid;
| ^
>> fs/overlayfs/copy_up.c:470:31: error: invalid type argument of unary '*' (have 'uuid_t')
470 | fh->fb.uuid = *uuid;
| ^~~~~
vim +431 fs/overlayfs/copy_up.c
418
419 struct ovl_fh *ovl_encode_real_fh(struct ovl_fs *ofs, struct inode *realinode,
420 bool is_upper)
421 {
422 struct ovl_fh *fh;
423 int fh_type, dwords;
424 int buflen = MAX_HANDLE_SZ;
425 uuid_t uuid;
426 struct kstatfs ks;
427 int err;
428
429 // RFC: dentry can't be NULL, uuid needs a type cast
430 realinode->i_sb->s_op->statfs(NULL, &ks);
> 431 uuid.b = ks.f_fsid;
432
433 /* Make sure the real fid stays 32bit aligned */
434 BUILD_BUG_ON(OVL_FH_FID_OFFSET % 4);
435 BUILD_BUG_ON(MAX_HANDLE_SZ + OVL_FH_FID_OFFSET > 255);
436
437 fh = kzalloc(buflen + OVL_FH_FID_OFFSET, GFP_KERNEL);
438 if (!fh)
439 return ERR_PTR(-ENOMEM);
440
441 /*
442 * We encode a non-connectable file handle for non-dir, because we
443 * only need to find the lower inode number and we don't want to pay
444 * the price or reconnecting the dentry.
445 */
446 dwords = buflen >> 2;
447 fh_type = exportfs_encode_inode_fh(realinode, (void *)fh->fb.fid,
448 &dwords, NULL, 0);
449 buflen = (dwords << 2);
450
451 err = -EIO;
452 if (fh_type < 0 || fh_type == FILEID_INVALID ||
453 WARN_ON(buflen > MAX_HANDLE_SZ))
454 goto out_err;
455
456 fh->fb.version = OVL_FH_VERSION;
457 fh->fb.magic = OVL_FH_MAGIC;
458 fh->fb.type = fh_type;
459 fh->fb.flags = OVL_FH_FLAG_CPU_ENDIAN;
460 /*
461 * When we will want to decode an overlay dentry from this handle
462 * and all layers are on the same fs, if we get a disconncted real
463 * dentry when we decode fid, the only way to tell if we should assign
464 * it to upperdentry or to lowerstack is by checking this flag.
465 */
466 if (is_upper)
467 fh->fb.flags |= OVL_FH_FLAG_PATH_UPPER;
468 fh->fb.len = sizeof(fh->fb) + buflen;
469 if (ovl_origin_uuid(ofs))
> 470 fh->fb.uuid = *uuid;
471
472 return fh;
473
474 out_err:
475 kfree(fh);
476 return ERR_PTR(err);
477 }
478
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-14 19:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 1:57 [RFC PATCH 0/1] ovl: brtfs' temp_fsid doesn't work with ovl index=on André Almeida
2025-10-14 1:57 ` [RFC PATCH 1/1] ovl: Use fsid as unique identifier for trusted origin André Almeida
2025-10-14 4:39 ` Christoph Hellwig
2025-10-14 5:13 ` Qu Wenruo
2025-10-14 17:40 ` David Sterba
2025-10-14 17:55 ` André Almeida
2025-10-14 23:46 ` Anand Jain
2025-10-15 1:22 ` Christoph Hellwig
2025-10-20 21:43 ` Dave Chinner
2025-10-21 1:16 ` Anand Jain
2025-10-14 19:52 ` kernel test robot [this message]
2025-10-15 10:52 ` Amir Goldstein
2025-10-14 5:26 ` [RFC PATCH 0/1] ovl: brtfs' temp_fsid doesn't work with ovl index=on Qu Wenruo
2025-10-14 18:24 ` David Sterba
2025-10-14 21:08 ` Qu Wenruo
2025-10-15 0:05 ` Anand Jain
2025-10-15 4:18 ` Qu Wenruo
2025-10-14 22:04 ` Anand Jain
2025-10-15 11:09 ` Amir Goldstein
2025-10-16 4:57 ` Christoph Hellwig
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=202510150318.j2kBtJYC-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrealmeid@igalia.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.