From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH v4 09/24] dept: Apply Dept to seqlock
Date: Wed, 09 Mar 2022 02:13:22 +0800 [thread overview]
Message-ID: <202203090250.tz4le5AI-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4108 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
In-Reply-To: <1646377603-19730-10-git-send-email-byungchul.park@lge.com>
References: <1646377603-19730-10-git-send-email-byungchul.park@lge.com>
TO: Byungchul Park <byungchul.park@lge.com>
TO: torvalds(a)linux-foundation.org
CC: hamohammed.sa(a)gmail.com
CC: jack(a)suse.cz
CC: peterz(a)infradead.org
CC: daniel.vetter(a)ffwll.ch
CC: amir73il(a)gmail.com
CC: david(a)fromorbit.com
CC: dri-devel(a)lists.freedesktop.org
CC: chris(a)chris-wilson.co.uk
CC: bfields(a)fieldses.org
CC: linux-ide(a)vger.kernel.org
CC: adilger.kernel(a)dilger.ca
CC: joel(a)joelfernandes.org
CC: cl(a)linux.com
CC: will(a)kernel.org
CC: duyuyang(a)gmail.com
CC: sashal(a)kernel.org
CC: paolo.valente(a)linaro.org
CC: damien.lemoal(a)opensource.wdc.com
CC: willy(a)infradead.org
CC: hch(a)infradead.org
CC: airlied(a)linux.ie
CC: mingo(a)redhat.com
CC: djwong(a)kernel.org
CC: vdavydov.dev(a)gmail.com
CC: rientjes(a)google.com
CC: dennis(a)kernel.org
CC: linux-ext4(a)vger.kernel.org
CC: linux-mm(a)kvack.org
CC: ngupta(a)vflare.org
Hi Byungchul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/sched/core]
[also build test WARNING on linux/master linus/master v5.17-rc7]
[cannot apply to tip/locking/core hnaz-mm/master next-20220308]
[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]
url: https://github.com/0day-ci/linux/commits/Byungchul-Park/DEPT-Dependency-Tracker/20220304-150943
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 25795ef6299f07ce3838f3253a9cb34f64efcfae
:::::: branch date: 4 days ago
:::::: commit date: 4 days ago
config: s390-randconfig-m031-20220307 (https://download.01.org/0day-ci/archive/20220309/202203090250.tz4le5AI-lkp(a)intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
New smatch warnings:
include/linux/cpuset.h:176 set_mems_allowed() warn: statement has no effect 31
kernel/cgroup/cpuset.c:1743 cpuset_change_task_nodemask() warn: statement has no effect 31
net/xfrm/xfrm_state.c:179 xfrm_hash_resize() warn: statement has no effect 31
net/xfrm/xfrm_policy.c:600 xfrm_bydst_resize() warn: statement has no effect 31
net/xfrm/xfrm_policy.c:1091 __xfrm_policy_inexact_prune_bin() warn: statement has no effect 31
net/xfrm/xfrm_policy.c:1148 xfrm_policy_inexact_alloc_chain() warn: statement has no effect 31
net/xfrm/xfrm_policy.c:1358 xfrm_hash_rebuild() warn: statement has no effect 31
Old smatch warnings:
net/xfrm/xfrm_policy.c:1162 xfrm_policy_inexact_alloc_chain() warn: statement has no effect 31
net/xfrm/xfrm_policy.c:1178 xfrm_policy_inexact_alloc_chain() warn: statement has no effect 31
vim +176 include/linux/cpuset.h
c0ff7453bb5c7c Miao Xie 2010-05-24 167
58568d2a8215cb Miao Xie 2009-06-16 168 static inline void set_mems_allowed(nodemask_t nodemask)
58568d2a8215cb Miao Xie 2009-06-16 169 {
db751fe3ea6880 John Stultz 2013-10-07 170 unsigned long flags;
db751fe3ea6880 John Stultz 2013-10-07 171
c0ff7453bb5c7c Miao Xie 2010-05-24 172 task_lock(current);
db751fe3ea6880 John Stultz 2013-10-07 173 local_irq_save(flags);
cc9a6c8776615f Mel Gorman 2012-03-21 174 write_seqcount_begin(¤t->mems_allowed_seq);
58568d2a8215cb Miao Xie 2009-06-16 175 current->mems_allowed = nodemask;
cc9a6c8776615f Mel Gorman 2012-03-21 @176 write_seqcount_end(¤t->mems_allowed_seq);
db751fe3ea6880 John Stultz 2013-10-07 177 local_irq_restore(flags);
c0ff7453bb5c7c Miao Xie 2010-05-24 178 task_unlock(current);
58568d2a8215cb Miao Xie 2009-06-16 179 }
58568d2a8215cb Miao Xie 2009-06-16 180
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2022-03-08 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:13 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-10 3:22 [PATCH v4 09/24] dept: Apply Dept to seqlock kernel test robot
2022-03-09 2:14 kernel test robot
2022-03-08 20:15 kernel test robot
2022-03-04 7:06 [PATCH v4 00/24] DEPT(Dependency Tracker) Byungchul Park
2022-03-04 7:06 ` [PATCH v4 09/24] dept: Apply Dept to seqlock Byungchul Park
2022-03-04 7:06 ` Byungchul Park
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=202203090250.tz4le5AI-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.org \
/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.