All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC][PATCH] simpler way to get benefits of "vfs: shave work on failed file open"
Date: Sun, 26 Nov 2023 15:07:09 +0800	[thread overview]
Message-ID: <202311261322.8ip3vqTD-lkp@intel.com> (raw)
In-Reply-To: <20231126020834.GC38156@ZenIV>

Hi Al,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on linux/master]
[also build test ERROR on linus/master v6.7-rc2 next-20231124]
[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/Al-Viro/simpler-way-to-get-benefits-of-vfs-shave-work-on-failed-file-open/20231126-101216
base:   linux/master
patch link:    https://lore.kernel.org/r/20231126020834.GC38156%40ZenIV
patch subject: [RFC][PATCH] simpler way to get benefits of "vfs: shave work on failed file open"
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20231126/202311261322.8ip3vqTD-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231126/202311261322.8ip3vqTD-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/202311261322.8ip3vqTD-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/array_size.h:5,
                    from include/linux/string.h:5,
                    from fs/file_table.c:9:
   fs/file_table.c: In function 'fput':
>> fs/file_table.c:436:32: error: 'f' undeclared (first use in this function); did you mean 'fd'?
     436 |                 if (unlikely(!(f->f_mode & (FMODE_BACKING | FMODE_OPENED)))) {
         |                                ^
   include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
      77 | # define unlikely(x)    __builtin_expect(!!(x), 0)
         |                                             ^
   fs/file_table.c:436:32: note: each undeclared identifier is reported only once for each function it appears in
     436 |                 if (unlikely(!(f->f_mode & (FMODE_BACKING | FMODE_OPENED)))) {
         |                                ^
   include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
      77 | # define unlikely(x)    __builtin_expect(!!(x), 0)
         |                                             ^


vim +436 fs/file_table.c

   430	
   431	void fput(struct file *file)
   432	{
   433		if (atomic_long_dec_and_test(&file->f_count)) {
   434			struct task_struct *task = current;
   435	
 > 436			if (unlikely(!(f->f_mode & (FMODE_BACKING | FMODE_OPENED)))) {
   437				file_free(f);
   438				return;
   439			}
   440			if (likely(!in_interrupt() && !(task->flags & PF_KTHREAD))) {
   441				init_task_work(&file->f_rcuhead, ____fput);
   442				if (!task_work_add(task, &file->f_rcuhead, TWA_RESUME))
   443					return;
   444				/*
   445				 * After this task has run exit_task_work(),
   446				 * task_work_add() will fail.  Fall through to delayed
   447				 * fput to avoid leaking *file.
   448				 */
   449			}
   450	
   451			if (llist_add(&file->f_llist, &delayed_fput_list))
   452				schedule_delayed_work(&delayed_fput_work, 1);
   453		}
   454	}
   455	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2023-11-26  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26  2:08 [RFC][PATCH] simpler way to get benefits of "vfs: shave work on failed file open" Al Viro
2023-11-26  4:59 ` Linus Torvalds
2023-11-26  5:08   ` Al Viro
2023-11-26  5:17     ` Linus Torvalds
2023-11-26  9:21       ` Christian Brauner
2023-11-26 10:58         ` Mateusz Guzik
2023-11-27 15:03           ` Christian Brauner
2023-11-26  7:07 ` kernel test robot
2023-11-26  7:07 ` kernel test robot [this message]
2023-11-26  9:31 ` Christian Brauner

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=202311261322.8ip3vqTD-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 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.