netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
	eric.dumazet@gmail.com, Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 10/13] net: add netdev_set_operstate() helper
Date: Thu, 8 Feb 2024 19:44:17 +0800	[thread overview]
Message-ID: <202402081918.OLyGaea3-lkp@intel.com> (raw)
In-Reply-To: <20240207142629.3456570-11-edumazet@google.com>

Hi Eric,

kernel test robot noticed the following build errors:

[auto build test ERROR on net-next/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Eric-Dumazet/net-annotate-data-races-around-dev-name_assign_type/20240207-222903
base:   net-next/main
patch link:    https://lore.kernel.org/r/20240207142629.3456570-11-edumazet%40google.com
patch subject: [PATCH net-next 10/13] net: add netdev_set_operstate() helper
config: sh-defconfig (https://download.01.org/0day-ci/archive/20240208/202402081918.OLyGaea3-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240208/202402081918.OLyGaea3-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/202402081918.OLyGaea3-lkp@intel.com/

All errors (new ones prefixed by >>):

   sh4-linux-ld: net/core/rtnetlink.o: in function `set_operstate':
>> rtnetlink.c:(.text+0x1220): undefined reference to `__cmpxchg_called_with_bad_pointer'
   sh4-linux-ld: net/core/rtnetlink.o: in function `netdev_set_operstate':
   rtnetlink.c:(.text+0x17a0): undefined reference to `__cmpxchg_called_with_bad_pointer'

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

  reply	other threads:[~2024-02-08 11:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 14:26 [PATCH net-next 00/13] net: complete dev_base_lock removal Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 01/13] net: annotate data-races around dev->name_assign_type Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 02/13] ip_tunnel: annotate data-races around t->parms.link Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 03/13] dev: annotate accesses to dev->link Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 04/13] net: convert dev->reg_state to u8 Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 05/13] net-sysfs: convert netdev_show() to RCU Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 06/13] net-sysfs: use dev_addr_sem to remove races in address_show() Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 07/13] net-sysfs: convert dev->operstate reads to lockless ones Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 08/13] net-sysfs: convert netstat_show() to RCU Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 09/13] net: remove stale mentions of dev_base_lock in comments Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 10/13] net: add netdev_set_operstate() helper Eric Dumazet
2024-02-08 11:44   ` kernel test robot [this message]
2024-02-08 13:20   ` kernel test robot
2024-02-08 13:35     ` Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 11/13] net: remove dev_base_lock from do_setlink() Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 12/13] net: remove dev_base_lock from register_netdevice() and friends Eric Dumazet
2024-02-07 14:26 ` [PATCH net-next 13/13] net: remove dev_base_lock Eric Dumazet

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=202402081918.OLyGaea3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).