From: kernel test robot <lkp@intel.com>
To: Samuel Wu <wusamuel@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Lukasz Luba <lukasz.luba@arm.com>
Cc: oe-kbuild-all@lists.linux.dev, Samuel Wu <wusamuel@google.com>,
Saravana Kannan <saravanak@google.com>,
kernel-team@android.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] PM: Support aborting suspend during filesystem sync
Date: Thu, 14 Aug 2025 03:21:52 +0800 [thread overview]
Message-ID: <202508140303.9c38ncEh-lkp@intel.com> (raw)
In-Reply-To: <20250812232126.1814253-1-wusamuel@google.com>
Hi Samuel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v6.17-rc1 next-20250813]
[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/Samuel-Wu/PM-Support-aborting-suspend-during-filesystem-sync/20250813-072435
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20250812232126.1814253-1-wusamuel%40google.com
patch subject: [PATCH v1] PM: Support aborting suspend during filesystem sync
config: arm64-randconfig-r132-20250813 (https://download.01.org/0day-ci/archive/20250814/202508140303.9c38ncEh-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250814/202508140303.9c38ncEh-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/202508140303.9c38ncEh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/power/suspend.c:79:1: sparse: sparse: symbol 'suspend_fs_sync_lock' was not declared. Should it be static?
>> kernel/power/suspend.c:80:1: sparse: sparse: symbol 'suspend_fs_sync_complete' was not declared. Should it be static?
kernel/power/suspend.c:104:54: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] @@
kernel/power/suspend.c:104:54: sparse: expected int val
kernel/power/suspend.c:104:54: sparse: got restricted suspend_state_t [usertype]
kernel/power/suspend.c:141:54: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] @@
kernel/power/suspend.c:141:54: sparse: expected int val
kernel/power/suspend.c:141:54: sparse: got restricted suspend_state_t [usertype]
kernel/power/suspend.c:202:19: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:202:47: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:203:19: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:203:51: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:208:26: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:208:65: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:215:42: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:215:51: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:216:38: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:217:51: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:215:72: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:240:34: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:240:73: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:241:27: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:241:59: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:246:34: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:246:69: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:247:21: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:247:42: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:537:33: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] state @@
kernel/power/suspend.c:537:33: sparse: expected int val
kernel/power/suspend.c:537:33: sparse: got restricted suspend_state_t [usertype] state
kernel/power/suspend.c:540:33: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] state @@
kernel/power/suspend.c:540:33: sparse: expected int val
kernel/power/suspend.c:540:33: sparse: got restricted suspend_state_t [usertype] state
kernel/power/suspend.c:610:57: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] state @@
kernel/power/suspend.c:610:57: sparse: expected int val
kernel/power/suspend.c:610:57: sparse: got restricted suspend_state_t [usertype] state
kernel/power/suspend.c:612:57: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] state @@
kernel/power/suspend.c:612:57: sparse: expected int val
kernel/power/suspend.c:612:57: sparse: got restricted suspend_state_t [usertype] state
kernel/power/suspend.c:650:52: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] state @@
kernel/power/suspend.c:650:52: sparse: expected int val
kernel/power/suspend.c:650:52: sparse: got restricted suspend_state_t [usertype] state
kernel/power/suspend.c:675:9: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:675:9: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:684:52: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected int val @@ got restricted suspend_state_t [usertype] state @@
kernel/power/suspend.c:684:52: sparse: expected int val
kernel/power/suspend.c:684:52: sparse: got restricted suspend_state_t [usertype] state
kernel/power/suspend.c:685:9: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:685:9: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:708:13: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:708:22: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:708:39: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:708:48: sparse: sparse: restricted suspend_state_t degrades to integer
kernel/power/suspend.c:711:9: sparse: sparse: restricted suspend_state_t degrades to integer
vim +/suspend_fs_sync_lock +79 kernel/power/suspend.c
77
78 static bool suspend_fs_sync_queued;
> 79 DEFINE_SPINLOCK(suspend_fs_sync_lock);
> 80 DECLARE_COMPLETION(suspend_fs_sync_complete);
81 void suspend_abort_fs_sync(void)
82 {
83 spin_lock(&suspend_fs_sync_lock);
84 complete(&suspend_fs_sync_complete);
85 spin_unlock(&suspend_fs_sync_lock);
86 }
87
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-13 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 23:21 [PATCH v1] PM: Support aborting suspend during filesystem sync Samuel Wu
2025-08-13 5:53 ` Greg Kroah-Hartman
2025-08-15 0:49 ` Samuel Wu
2025-08-13 19:21 ` kernel test robot [this message]
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=202508140303.9c38ncEh-lkp@intel.com \
--to=lkp@intel.com \
--cc=bsegall@google.com \
--cc=dakr@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=saravanak@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vschneid@redhat.com \
--cc=wusamuel@google.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.