From: Will Deacon <will@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] wait_on_bit: add an acquire memory barrier
Date: Fri, 26 Aug 2022 18:43:53 +0100 [thread overview]
Message-ID: <20220826174352.GA20386@willie-the-truck> (raw)
In-Reply-To: <alpine.LRH.2.02.2208261003590.27240@file01.intranet.prod.int.rdu2.redhat.com>
On Fri, Aug 26, 2022 at 10:08:42AM -0400, Mikulas Patocka wrote:
> On Fri, 26 Aug 2022, Mikulas Patocka wrote:
> > On Fri, 26 Aug 2022, Will Deacon wrote:
> > > On Thu, Aug 25, 2022 at 05:03:40PM -0400, Mikulas Patocka wrote:
> > > > For me, the kernel 6.0-rc2 doesn't boot in an arm64 virtual machine at all
> > > > (with or without this patch), so I only compile-tested it on arm64. I have
> > > > to bisect it.
> > >
> > > It's working fine for me and I haven't had any other reports that it's not
> > > booting. Please could you share some more details about your setup so we
> > > can try to reproduce the problem?
> >
> > I'm bisecting it now. I'll post the offending commit when I'm done.
>
> So, the bad commit is aacd149b62382c63911060b8f64c1e3d89bd405a ("arm64:
> head: avoid relocating the kernel twice for KASLR").
Thanks. Any chance you could give this a go, please?
https://lore.kernel.org/r/20220826164800.2059148-1-ardb@kernel.org
Will
next prev parent reply other threads:[~2022-08-26 17:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:38 [PATCH] wait_on_bit: add an acquire memory barrier Mikulas Patocka
2022-08-22 17:08 ` Linus Torvalds
2022-08-22 17:39 ` Linus Torvalds
2022-08-22 18:00 ` Joel Fernandes
2022-08-25 21:03 ` Mikulas Patocka
2022-08-25 21:54 ` Linus Torvalds
2022-08-26 13:17 ` [PATCH v3] " Mikulas Patocka
2022-08-26 16:45 ` Linus Torvalds
2022-08-26 17:19 ` Linus Torvalds
2022-08-26 17:50 ` Mikulas Patocka
2022-08-26 19:23 ` Geert Uytterhoeven
2022-08-26 20:03 ` [PATCH] provide arch_test_bit_acquire for architectures that define test_bit Mikulas Patocka
2022-08-26 20:07 ` Linus Torvalds
2022-08-26 20:03 ` [PATCH v3] wait_on_bit: add an acquire memory barrier Linus Torvalds
2022-08-26 20:43 ` [PATCH] provide arch_test_bit_acquire for architectures that define test_bit Mikulas Patocka
2022-08-26 23:10 ` Linus Torvalds
2022-08-26 23:18 ` Linus Torvalds
2022-08-27 11:38 ` Mikulas Patocka
2022-08-27 16:50 ` Linus Torvalds
2022-08-26 0:57 ` [PATCH] wait_on_bit: add an acquire memory barrier Alan Stern
2022-08-26 11:23 ` Will Deacon
2022-08-26 11:46 ` Mikulas Patocka
2022-08-26 14:08 ` Mikulas Patocka
2022-08-26 17:43 ` Will Deacon [this message]
2022-08-26 18:25 ` Mikulas Patocka
2022-08-26 18:31 ` Ard Biesheuvel
2022-08-26 19:10 ` Mikulas Patocka
2022-08-27 6:32 ` Ard Biesheuvel
2022-08-27 6:56 ` Ard Biesheuvel
2022-08-27 8:42 ` Mikulas Patocka
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=20220826174352.GA20386@willie-the-truck \
--to=will@kernel.org \
--cc=akiyks@gmail.com \
--cc=ardb@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mpatocka@redhat.com \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox