From: kernel test robot <lkp@intel.com>
To: Edward Adam Davis <eadavis@sina.com>,
syzbot+a31cda410a4ccd419712@syzkaller.appspotmail.com
Cc: oe-kbuild-all@lists.linux.dev, axboe@kernel.dk,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] loop: prohibit the use of sysfs as a backing file
Date: Tue, 3 Nov 2026 02:36:56 +0800 [thread overview]
Message-ID: <202611030239.QMvbuUI3-lkp@intel.com> (raw)
In-Reply-To: <20261102103354.427722-1-eadavis@sina.com>
Hi Edward,
kernel test robot noticed the following build errors:
[auto build test ERROR on axboe/for-next]
[also build test ERROR on linus/master v7.3 next-20261030]
[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/Edward-Adam-Davis/loop-prohibit-the-use-of-sysfs-as-a-backing-file/20261102-183354
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/r/20261102103354.427722-1-eadavis%40sina.com
patch subject: [PATCH] loop: prohibit the use of sysfs as a backing file
config: nios2-defconfig (https://download.01.org/0day-ci/archive/20261103/202611030239.QMvbuUI3-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261103/202611030239.QMvbuUI3-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/202611030239.QMvbuUI3-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/block/loop.c: In function 'loop_check_backing_file':
>> drivers/block/loop.c:537:48: error: 'SYSFS_MAGIC' undeclared (first use in this function)
537 | if (file_inode(file)->i_sb->s_magic == SYSFS_MAGIC)
| ^~~~~~~~~~~
drivers/block/loop.c:537:48: note: each undeclared identifier is reported only once for each function it appears in
vim +/SYSFS_MAGIC +537 drivers/block/loop.c
528
529 static int loop_check_backing_file(struct file *file)
530 {
531 if (!file->f_op->read_iter)
532 return -EINVAL;
533
534 if ((file->f_mode & FMODE_WRITE) && !file->f_op->write_iter)
535 return -EINVAL;
536
> 537 if (file_inode(file)->i_sb->s_magic == SYSFS_MAGIC)
538 return -EINVAL;
539
540 return 0;
541 }
542
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-11-02 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 3:47 [syzbot] [block?] INFO: task hung in blk_mq_freeze_queue_nomemsave (3) syzbot
2026-11-02 10:33 ` [PATCH] loop: prohibit the use of sysfs as a backing file Edward Adam Davis
2026-11-02 15:59 ` kernel test robot
2026-11-02 18:36 ` kernel test robot [this message]
2026-11-02 22:49 ` Bart Van Assche
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=202611030239.QMvbuUI3-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=eadavis@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=syzbot+a31cda410a4ccd419712@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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.