From: Thomas Bertschinger <tahbertschinger@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Greg KH <greg@kroah.com>,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
rust-for-linux@vger.kernel.org,
Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
Alice Ryhl <aliceryhl@google.com>
Subject: Re: [PATCH v2] rust: place generated init_module() function in .init.text
Date: Tue, 6 Feb 2024 07:49:59 -0700 [thread overview]
Message-ID: <20240206144959.GE296718@fedora-laptop> (raw)
In-Reply-To: <CANiq72m8V2nycL=P8yT3M=e6Nek0w45zBK48Aqbt39Kpt+bwTA@mail.gmail.com>
On Tue, Feb 06, 2024 at 11:51:35AM +0100, Miguel Ojeda wrote:
> On Tue, Feb 6, 2024 at 11:01 AM Greg KH <greg@kroah.com> wrote:
> >
> > "once" is not right, it can be called zillions of times, it's just that
> > it can't be called _AFTER_ module_init() is over for the file, as it
> > will no longer be present in memory.
> >
> > So technically, the wording you added here isn't correct, sorry.
>
> The safety preconditions may be stronger than needed. For instance, if
> we do not expect anybody to manually call this, then we can say so. In
> fact, we could even say Rust code cannot call this function.
>
> Cheers,
> Miguel
I can send a v3 that fixes the wording of the comment; it's worth being
correct.
That said, my intention was more aligned with what Miguel suggested, to
say that user-written Rust code should not call this function, rather
than to claim that it's impossible. If there is a need for the
init_module() to run multiple times, it might make more sense to put
that work in a user-defined function that gets called multiple times.
On that note, does anyone know any examples of modules that call their
init function more than once? I might go searching myself later to see
if I can find any, but in case anyone knows any off-hand. If there are
real use cases for this, it could be good to consider those here.
- Thomas Bertschinger
next prev parent reply other threads:[~2024-02-06 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 1:25 [PATCH v2] rust: place generated init_module() function in .init.text Thomas Bertschinger
2024-02-06 1:39 ` Martin Rodriguez Reboredo
2024-02-06 2:13 ` Thomas Bertschinger
2024-02-06 3:10 ` Trevor Gross
2024-02-06 3:17 ` Trevor Gross
2024-02-06 10:01 ` Greg KH
2024-02-06 10:51 ` Miguel Ojeda
2024-02-06 10:58 ` Greg KH
2024-02-06 11:31 ` Miguel Ojeda
2024-02-06 14:49 ` Thomas Bertschinger [this message]
2024-02-06 16:07 ` Martin Rodriguez Reboredo
2024-02-06 17:19 ` Miguel Ojeda
2024-02-06 21:28 ` Martin Rodriguez Reboredo
2024-02-06 17:19 ` Miguel Ojeda
2024-02-06 10:01 ` Greg KH
2024-02-06 10:29 ` Alice Ryhl
2024-02-06 10:50 ` Greg KH
2024-02-06 11:18 ` Miguel Ojeda
2024-02-06 10:57 ` Miguel Ojeda
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=20240206144959.GE296718@fedora-laptop \
--to=tahbertschinger@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=greg@kroah.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--cc=yakoyoku@gmail.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