From: kernel test robot <lkp@intel.com>
To: Rishikesh Jethwani <rjethwani@purestorage.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, saeedm@nvidia.com,
tariqt@nvidia.com, mbloch@nvidia.com, borisp@nvidia.com,
john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
leon@kernel.org, Rishikesh Jethwani <rjethwani@purestorage.com>
Subject: Re: [PATCH v4 2/3] tls: add hardware offload key update support
Date: Thu, 22 Jan 2026 08:19:40 +0100 [thread overview]
Message-ID: <202601220850.8AbmdIiS-lkp@intel.com> (raw)
In-Reply-To: <20260121215727.3994324-3-rjethwani@purestorage.com>
Hi Rishikesh,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.19-rc6 next-20260121]
[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/Rishikesh-Jethwani/tls-add-TLS-1-3-hardware-offload-support/20260122-060724
base: linus/master
patch link: https://lore.kernel.org/r/20260121215727.3994324-3-rjethwani%40purestorage.com
patch subject: [PATCH v4 2/3] tls: add hardware offload key update support
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260122/202601220850.8AbmdIiS-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260122/202601220850.8AbmdIiS-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/202601220850.8AbmdIiS-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from ./arch/x86/include/generated/asm/rwonce.h:1,
from include/linux/compiler.h:380,
from arch/x86/include/asm/atomic.h:5,
from include/linux/atomic.h:7,
from include/crypto/aead.h:11,
from net/tls/tls_device.c:32:
net/tls/tls_device.c: In function 'tls_set_device_offload':
>> include/asm-generic/rwonce.h:55:37: error: lvalue required as left operand of assignment
55 | *(volatile typeof(x) *)&(x) = (val); \
| ^
include/asm-generic/rwonce.h:61:9: note: in expansion of macro '__WRITE_ONCE'
61 | __WRITE_ONCE(x, val); \
| ^~~~~~~~~~~~
arch/x86/include/asm/barrier.h:63:9: note: in expansion of macro 'WRITE_ONCE'
63 | WRITE_ONCE(*p, v); \
| ^~~~~~~~~~
include/asm-generic/barrier.h:172:55: note: in expansion of macro '__smp_store_release'
172 | #define smp_store_release(p, v) do { kcsan_release(); __smp_store_release(p, v); } while (0)
| ^~~~~~~~~~~~~~~~~~~
net/tls/tls_device.c:1249:25: note: in expansion of macro 'smp_store_release'
1249 | smp_store_release(sk->sk_validate_xmit_skb,
| ^~~~~~~~~~~~~~~~~
--
In file included from arch/x86/include/generated/asm/rwonce.h:1,
from include/linux/compiler.h:380,
from arch/x86/include/asm/atomic.h:5,
from include/linux/atomic.h:7,
from include/crypto/aead.h:11,
from tls_device.c:32:
tls_device.c: In function 'tls_set_device_offload':
>> include/asm-generic/rwonce.h:55:37: error: lvalue required as left operand of assignment
55 | *(volatile typeof(x) *)&(x) = (val); \
| ^
include/asm-generic/rwonce.h:61:9: note: in expansion of macro '__WRITE_ONCE'
61 | __WRITE_ONCE(x, val); \
| ^~~~~~~~~~~~
arch/x86/include/asm/barrier.h:63:9: note: in expansion of macro 'WRITE_ONCE'
63 | WRITE_ONCE(*p, v); \
| ^~~~~~~~~~
include/asm-generic/barrier.h:172:55: note: in expansion of macro '__smp_store_release'
172 | #define smp_store_release(p, v) do { kcsan_release(); __smp_store_release(p, v); } while (0)
| ^~~~~~~~~~~~~~~~~~~
tls_device.c:1249:25: note: in expansion of macro 'smp_store_release'
1249 | smp_store_release(sk->sk_validate_xmit_skb,
| ^~~~~~~~~~~~~~~~~
vim +55 include/asm-generic/rwonce.h
e506ea451254ab Will Deacon 2019-10-15 52
e506ea451254ab Will Deacon 2019-10-15 53 #define __WRITE_ONCE(x, val) \
e506ea451254ab Will Deacon 2019-10-15 54 do { \
e506ea451254ab Will Deacon 2019-10-15 @55 *(volatile typeof(x) *)&(x) = (val); \
e506ea451254ab Will Deacon 2019-10-15 56 } while (0)
e506ea451254ab Will Deacon 2019-10-15 57
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-22 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 21:57 [PATCH v4 0/3] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-01-21 21:57 ` [PATCH v4 1/3] tls: add " Rishikesh Jethwani
2026-01-21 21:57 ` [PATCH v4 2/3] tls: add hardware offload key update support Rishikesh Jethwani
2026-01-22 4:09 ` kernel test robot
2026-01-22 5:15 ` kernel test robot
2026-01-22 7:19 ` kernel test robot [this message]
2026-01-22 7:54 ` kernel test robot
2026-01-21 21:57 ` [PATCH v4 3/3] mlx5: TLS 1.3 hardware offload support Rishikesh Jethwani
2026-01-22 11:30 ` [PATCH v4 0/3] tls: Add " Tariq Toukan
2026-01-22 19:22 ` Rishikesh Jethwani
2026-01-23 19:05 ` Rishikesh Jethwani
2026-01-26 23:37 ` Rishikesh Jethwani
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=202601220850.8AbmdIiS-lkp@intel.com \
--to=lkp@intel.com \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=rjethwani@purestorage.com \
--cc=saeedm@nvidia.com \
--cc=sd@queasysnail.net \
--cc=tariqt@nvidia.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