From: Johan Hovold <johan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Petr Pavlu <petr.pavlu@suse.com>,
gregkh@linuxfoundation.org, rafael@kernel.org, song@kernel.org,
lucas.de.marchi@gmail.com, christophe.leroy@csgroup.eu,
peterz@infradead.org, rppt@kernel.org, dave@stgolabs.net,
willy@infradead.org, vbabka@suse.cz, mhocko@suse.com,
dave.hansen@linux.intel.com, colin.i.king@gmail.com,
jim.cromie@gmail.com, catalin.marinas@arm.com, jbaron@akamai.com,
rick.p.edgecombe@intel.com, yujie.liu@intel.com,
david@redhat.com, tglx@linutronix.de, hch@lst.de,
patches@lists.linux.dev, linux-modules@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
pmladek@suse.com, prarit@redhat.com, lennart@poettering.net
Subject: Re: [PATCH 2/2] module: add support to avoid duplicates early on load
Date: Mon, 5 Jun 2023 14:25:48 +0200 [thread overview]
Message-ID: <ZH3UTOaBD7f5KH6Q@hovoldconsulting.com> (raw)
In-Reply-To: <ZHXEktFq7NPYLtGn@hovoldconsulting.com>
On Tue, May 30, 2023 at 11:40:35AM +0200, Johan Hovold wrote:
> On Mon, May 29, 2023 at 09:55:15PM -0400, Linus Torvalds wrote:
> > On Mon, May 29, 2023 at 11:18 AM Johan Hovold <johan@kernel.org> wrote:
> > >
> > > I took a closer look at some of the modules that failed to load and
> > > noticed a pattern in that they have dependencies that are needed by more
> > > than one device.
> >
> > Ok, this is a "maybe something like this" RFC series of two patches -
> > one trivial one to re-organize things a bit so that we can then do the
> > real one which uses a filter based on the inode pointer to return an
> > "idempotent return value" for module loads that share the same inode.
> >
> > It's entirely untested, and since I'm on the road I'm going to not
> > really be able to test it. It compiles for me, and the code looks
> > fairly straightforward, but it's probably buggy.
> >
> > It's very loosely based on Luis' attempt, but it
> > (a) is internal to module loading
> > (b) uses a reliable cookie
> > (c) doesn't leave the cookie around randomly for later
> > (d) has seen absolutely no testing
> >
> > Put another way: if somebody wants to play with this, please treat it
> > as a starting point, not the final thing. You might need to debug
> > things, and fix silly mistakes.
>
> With the missing spinlock initialisation fixed:
>
> -static struct spinlock idem_lock;
> +static DEFINE_SPINLOCK(idem_lock);
>
> this passes basic smoke testing and allows the X13s to boot.
>
> It does not seem to have any significant impact on boot time, but it
> avoids some of the unnecessary load attempts as intended:
Took another look at code which modulo some nits like missing spaces
around a + operator and an "ourselfs" typo looks good to me. So with the
spinlock initialisation fixed:
Reviewed-by: Johan Hovold <johan@kernel.org>
Tested-by: Johan Hovold <johan@kernel.org>
Johan
next prev parent reply other threads:[~2023-06-05 12:25 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 21:36 [PATCH 0/2] module: avoid all memory pressure due to duplicates Luis Chamberlain
2023-05-24 21:36 ` [PATCH 1/2] fs/kernel_read_file: add support for duplicate detection Luis Chamberlain
2023-05-24 21:52 ` Linus Torvalds
2023-05-24 21:56 ` Linus Torvalds
2023-05-24 22:07 ` Luis Chamberlain
2023-05-25 4:00 ` Linus Torvalds
2023-05-25 18:08 ` Luis Chamberlain
2023-05-25 18:35 ` Luis Chamberlain
2023-05-25 18:50 ` Linus Torvalds
2023-05-25 19:32 ` Luis Chamberlain
2023-05-25 7:01 ` Christian Brauner
2023-05-24 21:36 ` [PATCH 2/2] module: add support to avoid duplicates early on load Luis Chamberlain
2023-05-25 11:40 ` Petr Pavlu
2023-05-25 16:07 ` Linus Torvalds
2023-05-25 16:42 ` Greg KH
2023-05-25 18:22 ` Luis Chamberlain
2023-05-25 17:52 ` Linus Torvalds
2023-05-25 18:45 ` Lucas De Marchi
2023-05-25 21:12 ` Linus Torvalds
2023-05-25 22:02 ` Luis Chamberlain
2023-05-26 1:39 ` Linus Torvalds
2023-05-29 8:58 ` Johan Hovold
2023-05-29 11:00 ` Linus Torvalds
2023-05-29 12:44 ` Johan Hovold
2023-05-29 15:18 ` Johan Hovold
2023-05-30 1:55 ` Linus Torvalds
2023-05-30 9:40 ` Johan Hovold
2023-06-05 12:25 ` Johan Hovold [this message]
2023-05-30 16:22 ` Luis Chamberlain
2023-05-30 17:16 ` Lucas De Marchi
2023-05-30 19:41 ` Luis Chamberlain
2023-05-30 22:17 ` Linus Torvalds
2023-05-31 5:30 ` Lucas De Marchi
2023-05-31 0:31 ` Luis Chamberlain
2023-05-31 7:51 ` David Hildenbrand
2023-05-31 16:57 ` Luis Chamberlain
2023-06-02 15:19 ` David Hildenbrand
2023-06-02 16:04 ` Luis Chamberlain
2023-06-05 11:26 ` David Hildenbrand
2023-06-05 15:17 ` Luis Chamberlain
2023-06-05 15:28 ` Luis Chamberlain
2023-06-28 18:52 ` Luis Chamberlain
2023-06-28 20:14 ` Linus Torvalds
2023-06-28 22:07 ` Linus Torvalds
2023-06-28 23:17 ` Linus Torvalds
2023-06-29 0:18 ` Luis Chamberlain
2023-06-02 16:06 ` Linus Torvalds
2023-06-02 16:37 ` David Hildenbrand
2023-05-30 22:45 ` Dan Williams
2023-06-04 14:26 ` Rudi Heitbaum
2023-05-29 17:47 ` Linus Torvalds
2023-05-30 10:01 ` Johan Hovold
2023-05-25 16:54 ` Lucas De Marchi
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=ZH3UTOaBD7f5KH6Q@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=colin.i.king@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@intel.com \
--cc=mcgrof@kernel.org \
--cc=mhocko@suse.com \
--cc=patches@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=prarit@redhat.com \
--cc=rafael@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yujie.liu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).