All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 1/6] fs: unify locking semantics for fs freeze / thaw
Date: Sat, 13 May 2023 07:54:55 +0800	[thread overview]
Message-ID: <202305130705.w81PkYdS-lkp@intel.com> (raw)
In-Reply-To: <20230508011717.4034511-2-mcgrof@kernel.org>

Hi Luis,

kernel test robot noticed the following build errors:

[auto build test ERROR on gfs2/for-next]
[also build test ERROR on axboe-block/for-next jaegeuk-f2fs/dev-test jaegeuk-f2fs/dev linus/master v6.4-rc1 next-20230512]
[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/Luis-Chamberlain/fs-unify-locking-semantics-for-fs-freeze-thaw/20230508-092008
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git for-next
patch link:    https://lore.kernel.org/r/20230508011717.4034511-2-mcgrof%40kernel.org
patch subject: [PATCH 1/6] fs: unify locking semantics for fs freeze / thaw
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20230513/202305130705.w81PkYdS-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/intel-lab-lkp/linux/commit/f277836573b983c2aa96f25337a36a13e56382f5
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Luis-Chamberlain/fs-unify-locking-semantics-for-fs-freeze-thaw/20230508-092008
        git checkout f277836573b983c2aa96f25337a36a13e56382f5
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 olddefconfig
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202305130705.w81PkYdS-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/gfs2/sys.c: In function 'freeze_store':
>> fs/gfs2/sys.c:167:31: error: 'sb' undeclared (first use in this function); did you mean 's8'?
     167 |         if (!get_active_super(sb->s_bdev))
         |                               ^~
         |                               s8
   fs/gfs2/sys.c:167:31: note: each undeclared identifier is reported only once for each function it appears in
--
   fs/gfs2/util.c: In function 'gfs2_withdraw':
>> fs/gfs2/util.c:348:39: error: 'sb' undeclared (first use in this function); did you mean 's8'?
     348 |                 if (!get_active_super(sb->s_bdev)) {
         |                                       ^~
         |                                       s8
   fs/gfs2/util.c:348:39: note: each undeclared identifier is reported only once for each function it appears in


vim +167 fs/gfs2/sys.c

   155	
   156	static ssize_t freeze_store(struct gfs2_sbd *sdp, const char *buf, size_t len)
   157	{
   158		int error, n;
   159	
   160		error = kstrtoint(buf, 0, &n);
   161		if (error)
   162			return error;
   163	
   164		if (!capable(CAP_SYS_ADMIN))
   165			return -EPERM;
   166	
 > 167		if (!get_active_super(sb->s_bdev))
   168			return -ENOTTY;
   169	
   170		switch (n) {
   171		case 0:
   172			error = thaw_super(sdp->sd_vfs);
   173			break;
   174		case 1:
   175			error = freeze_super(sdp->sd_vfs);
   176			break;
   177		default:
   178			deactivate_locked_super(sb);
   179			return -EINVAL;
   180		}
   181	
   182		deactivate_locked_super(sb);
   183	
   184		if (error) {
   185			fs_warn(sdp, "freeze %d error %d\n", n, error);
   186			return error;
   187		}
   188	
   189		return len;
   190	}
   191	

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

  parent reply	other threads:[~2023-05-12 23:55 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  1:17 [PATCH 0/6] vfs: provide automatic kernel freeze / resume Luis Chamberlain
2023-05-08  1:17 ` Luis Chamberlain
2023-05-08  1:17 ` [PATCH 1/6] fs: unify locking semantics for fs freeze / thaw Luis Chamberlain
2023-05-08  1:17   ` Luis Chamberlain
2023-05-12  6:00   ` kernel test robot
2023-05-12 23:54   ` kernel test robot [this message]
2023-05-18  5:32   ` Darrick J. Wong
2023-05-18  5:32     ` Darrick J. Wong
2023-05-25 12:17   ` Jan Kara
2023-05-25 12:17     ` Jan Kara
2023-06-08  5:01   ` Christoph Hellwig
2023-06-08  5:01     ` Christoph Hellwig
2023-06-08 19:55     ` Luis Chamberlain
2023-06-08 19:55       ` Luis Chamberlain
2023-05-08  1:17 ` [PATCH 2/6] fs: add frozen sb state helpers Luis Chamberlain
2023-05-08  1:17   ` Luis Chamberlain
2023-05-25 12:19   ` Jan Kara
2023-05-25 12:19     ` Jan Kara
2023-06-08  5:05   ` Christoph Hellwig
2023-06-08  5:05     ` Christoph Hellwig
2023-06-08 15:05     ` Darrick J. Wong
2023-06-08 15:05       ` Darrick J. Wong
2023-05-08  1:17 ` [PATCH 3/6] fs: distinguish between user initiated freeze and kernel initiated freeze Luis Chamberlain
2023-05-08  1:17   ` Luis Chamberlain
2023-05-16 15:23   ` Darrick J. Wong
2023-05-16 15:23     ` Darrick J. Wong
2023-05-22 23:42   ` Darrick J. Wong
2023-05-22 23:42     ` Darrick J. Wong
2023-05-25 14:14     ` Jan Kara
2023-05-25 14:14       ` Jan Kara
2023-06-06 17:19       ` Darrick J. Wong
2023-06-06 17:19         ` Darrick J. Wong
2023-06-07  9:22         ` Jan Kara
2023-06-07  9:22           ` Jan Kara
2023-06-07 14:50           ` Darrick J. Wong
2023-06-07 14:50             ` Darrick J. Wong
2023-06-08 20:30         ` Luis Chamberlain
2023-06-08 20:30           ` Luis Chamberlain
2023-06-07 16:31       ` Darrick J. Wong
2023-06-07 16:31         ` Darrick J. Wong
2023-06-07 20:46         ` Jan Kara
2023-06-07 20:46           ` Jan Kara
2023-06-08 18:58           ` Darrick J. Wong
2023-06-08 18:58             ` Darrick J. Wong
2023-06-08  5:29       ` Christoph Hellwig
2023-06-08  5:29         ` Christoph Hellwig
2023-06-08  9:11         ` Jan Kara
2023-06-08  9:11           ` Jan Kara
2023-06-08 18:16           ` Darrick J. Wong
2023-06-08 18:16             ` Darrick J. Wong
2023-06-08  5:24     ` Christoph Hellwig
2023-06-08  5:24       ` Christoph Hellwig
2023-06-08 18:15       ` Darrick J. Wong
2023-06-08 18:15         ` Darrick J. Wong
2023-06-08 20:26     ` Luis Chamberlain
2023-06-08 20:26       ` Luis Chamberlain
2023-06-08 21:10       ` Darrick J. Wong
2023-06-08 21:10         ` Darrick J. Wong
2023-05-08  1:17 ` [PATCH 4/6] fs: move !SB_BORN check early on freeze and add for thaw Luis Chamberlain
2023-05-08  1:17   ` Luis Chamberlain
2023-05-08  1:17 ` [PATCH 5/6] fs: add iterate_supers_excl() and iterate_supers_reverse_excl() Luis Chamberlain
2023-05-08  1:17   ` Luis Chamberlain
2023-05-08  1:17 ` [PATCH 6/6] fs: add automatic kernel fs freeze / thaw and remove kthread freezing Luis Chamberlain
2023-05-08  1:17   ` Luis Chamberlain
2023-05-09  1:20   ` Dave Chinner
2023-05-09  1:20     ` Dave Chinner
2023-05-16 15:17     ` Darrick J. Wong
2023-05-16 15:17       ` Darrick J. Wong
2023-05-08  1:21 ` [PATCH 0/6] vfs: provide automatic kernel freeze / resume Luis Chamberlain
2023-05-08  1:21   ` Luis Chamberlain

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=202305130705.w81PkYdS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=mcgrof@kernel.org \
    --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.