From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Johan Hovold <johan@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, <mcgrof@kernel.org>
Subject: Re: Revert "module: error out early on concurrent load of the same module file"
Date: Tue, 30 May 2023 15:19:21 -0700 [thread overview]
Message-ID: <64767669744d4_168e29489@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <CAHk-=whWJFw8+HP=0-ZaQYq2VVPtv1StFhUxgiJW1_FWdtgJSA@mail.gmail.com>
Linus Torvalds wrote:
> On Tue, May 30, 2023 at 5:43 PM Dan Williams <dan.j.williams@intel.com> wrote:
> >
> > [ add linux-cxl ]
> >
> > Sedat Dilek wrote:
> > > Hi,
> > >
> > > after building Linux v6.4-rc4 I can NOT boot into my Debian GNU/Linux
> > > AMD64 system with root-ext4 (/dev/sdc2 - of course using UUID in
> > > /etc/fstab).
> >
> > I did not find a mailing-list thread for "9828ed3f695a module: error out early
> > on concurrent load of the same module file", so replying here.
>
> It is this thread:
>
> https://lore.kernel.org/lkml/20230524213620.3509138-1-mcgrof@kernel.org/
>
> which initially proposed a different solution, then that "just reject
> concurrent loads", and after that caused problems, there's yet another
> proposal at
>
> https://lore.kernel.org/lkml/CAHk-=wg7ihygotpO9x5a6QJO5oAom9o91==L_Kx-gUHvRYuXiQ@mail.gmail.com/
>
> although if you want to try out that approach, Johan pointed out a
> missing initialization of a spinlock in that patch in a reply there.
>
> > Just wanted to highlight this a test case for the next attempt at this
> > fix.
>
> See above: the next attempt won't be until 6.5, but if you saw the
> failure on your test-cases, it might be a good idea to check out that
> next attempt early..
Thanks, will check those out.
I know that the "Link:" for "mailing-list thread where patch originated"
is mostly useless information [1], but when it comes to quickly reporting
test results on the output of "git bisect", it comes in handy.
[1]: https://lore.kernel.org/all/CAHk-=wgzRUT1fBpuz3xcN+YdsX0SxqOzHWRtj0ReHpUBb5TKbA@mail.gmail.com/
next prev parent reply other threads:[~2023-05-30 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 16:18 Sedat Dilek
2023-05-29 17:33 ` Linus Torvalds
2023-05-30 3:37 ` Sedat Dilek
2023-05-30 21:43 ` Dan Williams
2023-05-30 21:56 ` Linus Torvalds
2023-05-30 22:19 ` Dan Williams [this message]
2023-05-30 22:42 ` Linus Torvalds
2023-05-30 23:04 ` Dan Williams
2023-05-30 21:58 ` Revert "module: error out early on concurrent load of the same module file"' Luis Chamberlain
2023-05-30 22:21 ` Dan Williams
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=64767669744d4_168e29489@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=johan@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sedat.dilek@gmail.com \
--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
all inboxes | Powered by JetHome®