All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
	Bobby Eshleman <bobbyeshleman@meta.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: ld.lld: error: vmlinux.a(af_vsock.o at 1186296) <inline asm>:5:8: unpredictable STXR instruction, status is also a source
Date: Fri, 10 Jul 2026 08:54:28 -0700	[thread overview]
Message-ID: <20260710155428.GA3149665@ax162> (raw)
In-Reply-To: <CAGxU2F5KvtLSgT9pzhv8YxcP_j9L7usXqKY+W446XxLAovdbog@mail.gmail.com>

On Fri, Jul 10, 2026 at 04:22:20PM +0200, Stefano Garzarella wrote:
> On Mon, 6 Jul 2026 at 10:44, kernel test robot <lkp@intel.com> wrote:
> >
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   8cdeaa50eae8dad34885515f62559ee83e7e8dda
> > commit: 102eab95f025b4d3f3a6c0a858400aca2af2fe52 vsock: lock down child_ns_mode as write-once
> > date:   4 months ago
> > config: arm64-randconfig-001-20260706 (https://download.01.org/0day-ci/archive/20260706/202607061644.jD93AjWc-lkp@intel.com/config)
> > compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260706/202607061644.jD93AjWc-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
> > | Fixes: 102eab95f025 ("vsock: lock down child_ns_mode as write-once")
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202607061644.jD93AjWc-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > >> ld.lld: error: vmlinux.a(af_vsock.o at 1186296) <inline asm>:5:8: unpredictable STXR instruction, status is also a source
> >    stlxr   w8, w8, [x21]
> >    ^
> >
> 
> Could this be related to https://github.com/llvm/llvm-project/issues/106380 ?
> That issue seems fixed in llvm >= 20

Indeed, this is resolved by

  https://github.com/llvm/llvm-project/commit/7183771834d9035ffbedd8f1ff9233b16722b986

in LLVM 20.1.0, I confirmed with a reverse bisect. It looks like
this issue triggers on undefined values being passed to inline asm but I
don't see where there is an undefined value in the blamed commit but I
did not look too hard. Presumably this is around the try_cmpxchg() in
vsock_net_set_child_mode(). I am not sure this will be easily to
workaround so we might just have to leave it broken.

-- 
Cheers,
Nathan

  reply	other threads:[~2026-07-10 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  8:42 ld.lld: error: vmlinux.a(af_vsock.o at 1186296) <inline asm>:5:8: unpredictable STXR instruction, status is also a source kernel test robot
2026-07-10 14:22 ` Stefano Garzarella
2026-07-10 15:54   ` Nathan Chancellor [this message]
2026-07-14  9:35     ` Stefano Garzarella

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=20260710155428.GA3149665@ax162 \
    --to=nathan@kernel.org \
    --cc=bobbyeshleman@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@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 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.