MIME-Version: 1.0
References: <CAHk-=wii6BZtVKYfvQCQqbE3+t1_yAb-ea80-3PcJ4KxgpfHkA@mail.gmail.com>
 <d915df60-d06b-47d4-8b47-8aa1bbc2aac7@roeck-us.net> <CAHk-=wi8xQw6eTRncbJfWWYHHi0UBG2B_AfHrzZbPr=k0V_WYQ@mail.gmail.com>
 <fce02d50-65a7-4aa7-8949-6a82321da292@roeck-us.net>
In-Reply-To: <fce02d50-65a7-4aa7-8949-6a82321da292@roeck-us.net>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 13 Mar 2023 15:16:11 -0700
Message-ID: <CAHk-=wgVCTJTQPwoLrscmOa+n9X8+bc5ieCD+7PXw35Ke7i6ng@mail.gmail.com>
Subject: Re: Linux 6.3-rc2
To:     Guenter Roeck <linux@roeck-us.net>
Cc:     "Paul E. McKenney" <paulmck@kernel.org>,
        Frederic Weisbecker <frederic@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Mar 13, 2023 at 1:30=E2=80=AFPM Guenter Roeck <linux@roeck-us.net> =
wrote:
>
> It gets weird. Bisect log below. Reverting the identified patch does
> indeed seem to fix the problem, only I have no clue why this might
> be the case. The patch looks completely innocent to me. Yet, I can
> reliably reproduce the problem with v6.3-rc2, but at least so far I
> have not been able to reproduce it with commit f3dd0c53370 reverted
> (and I am trying on five different servers in parallel).

Yeah, that commit looks very innocuous. I'm surprised it would even
change any code generation, but it's very possible that it ends up
affecting some code layout or something almost by mistake.

I'd be inclined to think that the problem is very timing-sensitive,
and has probably been there for a while, and some random moon phase
just made it happen now.

               Linus