Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CA+icZUVZSBx-=Sm8ZM12dWY4hmpnfDdhmg6UwXsR4OLSgPXY2w@mail.gmail.com>
In-Reply-To: <CA+icZUVZSBx-=Sm8ZM12dWY4hmpnfDdhmg6UwXsR4OLSgPXY2w@mail.gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 29 May 2023 13:33:18 -0400
Message-ID: <CAHk-=wjpb_j4xJoKLivHFkrruR2TRcicEUkNVfXkY3xV5ybRSA@mail.gmail.com>
Subject: Re: Revert "module: error out early on concurrent load of the same
 module file"
To:     sedat.dilek@gmail.com
Cc:     Johan Hovold <johan@kernel.org>, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, May 29, 2023 at 12:18=E2=80=AFPM Sedat Dilek <sedat.dilek@gmail.com=
> wrote:
>
> Building from scratch with latest Linus Git including:
>
> Revert "module: error out early on concurrent load of the same module fil=
e"
> https://git.kernel.org/linus/ac2263b588dffd3a1efd7ed0b156ea6c5aea200d

So just to confirm: both plain 6.4 _and_ with that revert hangs?

The revert is pure "go back to old state", so the revert really
shouldn't cause any problems what-so-ever.

So if rc4 doesn't boot for you, and the revert also didn't fix it for
you, then there is something else going on.

There have been other module changes during the merge window, and
obviously it might be entirely unrelated to modules too. Can you try
to narrow down when it started failing?

          Linus