All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [RFC PATCH v2 1/8] Use atomic type for ucounts reference counting
Date: Mon, 11 Jan 2021 06:34:03 +0800	[thread overview]
Message-ID: <202101110649.O2F9EINT-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2738 bytes --]

CC: kbuild-all(a)lists.01.org
In-Reply-To: <447547b12bba1894d3f1f79d6408dfc60b219b0c.1610299857.git.gladkov.alexey@gmail.com>
References: <447547b12bba1894d3f1f79d6408dfc60b219b0c.1610299857.git.gladkov.alexey@gmail.com>
TO: Alexey Gladkov <gladkov.alexey@gmail.com>

Hi Alexey,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[also build test WARNING on hnaz-linux-mm/master v5.11-rc2 next-20210108]
[cannot apply to linux/master kees/for-next/pstore]
[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/Alexey-Gladkov/Count-rlimits-in-each-user-namespace/20210111-014938
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2ff90100ace886895e4fbb2850b8d5e49d931ed6
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
config: mips-randconfig-c003-20210111 (attached as .config)
compiler: mips64-linux-gcc (GCC) 9.3.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>


"coccinelle warnings: (new ones prefixed by >>)"
>> kernel/ucount.c:169:5-24: atomic_dec_and_test variation before object free at line 170.
   kernel/ucount.c:169:5-24: atomic_dec_and_test variation before object free at line 175.

vim +169 kernel/ucount.c

f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  163  
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  164  static void put_ucounts(struct ucounts *ucounts)
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  165  {
880a38547ff08715 Nikolay Borisov   2017-01-20  166  	unsigned long flags;
880a38547ff08715 Nikolay Borisov   2017-01-20  167  
880a38547ff08715 Nikolay Borisov   2017-01-20  168  	spin_lock_irqsave(&ucounts_lock, flags);
e58c759c8718b56a Alexey Gladkov    2021-01-10 @169  	if (atomic_dec_and_test(&ucounts->count))
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08 @170  		hlist_del_init(&ucounts->node);
040757f738e13caa Eric W. Biederman 2017-03-05  171  	else
040757f738e13caa Eric W. Biederman 2017-03-05  172  		ucounts = NULL;
880a38547ff08715 Nikolay Borisov   2017-01-20  173  	spin_unlock_irqrestore(&ucounts_lock, flags);
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  174  
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  175  	kfree(ucounts);
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  176  }
f6b2db1a3e8d141d Eric W. Biederman 2016-08-08  177  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38685 bytes --]

             reply	other threads:[~2021-01-10 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 22:34 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-10 17:33 [RFC PATCH v2 0/8] Count rlimits in each user namespace Alexey Gladkov
2021-01-10 17:33 ` [RFC PATCH v2 1/8] Use atomic type for ucounts reference counting Alexey Gladkov
2021-01-10 17:33   ` Alexey Gladkov
2021-01-13 16:31   ` Eric W. Biederman
2021-01-13 16:31     ` Eric W. Biederman
2021-01-13 18:01     ` Kees Cook
2021-01-13 18:01       ` Kees Cook

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=202101110649.O2F9EINT-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.