From: Eder Zulian <ezulian@redhat.com>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
williams@redhat.com, ojeda@kernel.org, alex.gaynor@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, tmgross@umich.edu
Subject: Re: [PATCH] rust: Fix build error
Date: Thu, 17 Oct 2024 01:48:19 +0200 [thread overview]
Message-ID: <ZxBQw1X_OG26RO9o@f39> (raw)
In-Reply-To: <Zw1_rXUyjTBOh0QH@boqun-archlinux>
Hi Boqun,
On Mon, Oct 14, 2024 at 01:31:41PM -0700, Boqun Feng wrote:
> Hi Eder,
>
> Thanks for the patch!
Sure, my pleasure.
>
> On Mon, Oct 14, 2024 at 09:52:53PM +0200, Eder Zulian wrote:
> > When CONFIG_DEBUG_SPINLOCK=y and CONFIG_PREEMPT_RT=y the following build
> > error occurs:
> >
> > In file included from rust/helpers/helpers.c:22:
> > rust/helpers/spinlock.c: In function ‘rust_helper___spin_lock_init’:
> > rust/helpers/spinlock.c:10:30: error: implicit declaration of function ‘spinlock_check’; did you mean ‘spin_lock_bh’? [-Wimplicit-function-declaration]
> > 10 | __raw_spin_lock_init(spinlock_check(lock), name, key, LD_WAIT_CONFIG);
> > | ^~~~~~~~~~~~~~
> > | spin_lock_bh
> > rust/helpers/spinlock.c:10:30: error: passing argument 1 of ‘__raw_spin_lock_init’ makes pointer from integer without a cast [-Wint-conversion]
> > 10 | __raw_spin_lock_init(spinlock_check(lock), name, key, LD_WAIT_CONFIG);
> > | ^~~~~~~~~~~~~~~~~~~~
> > | |
> > | int
> > In file included from ./include/linux/wait.h:9,
> > from ./include/linux/wait_bit.h:8,
> > from ./include/linux/fs.h:6,
> > from ./include/linux/highmem.h:5,
> > from ./include/linux/bvec.h:10,
> > from ./include/linux/blk_types.h:10,
> > from ./include/linux/blkdev.h:9,
> > from ./include/linux/blk-mq.h:5,
> > from rust/helpers/blk.c:3,
> > from rust/helpers/helpers.c:10:
> > ./include/linux/spinlock.h:101:52: note: expected ‘raw_spinlock_t *’ {aka ‘struct raw_spinlock *’} but argument is of type ‘int’
> > 101 | extern void __raw_spin_lock_init(raw_spinlock_t *lock, const char *name,
> > | ~~~~~~~~~~~~~~~~^~~~
> > make[2]: *** [scripts/Makefile.build:229: rust/helpers/helpers.o] Error 1
> >
> > Error observed while building a rt-debug kernel for aarch64.
> >
> > On a PREEMPT_RT build, spin locks have been mapped to rt_mutex types, so
> > avoid the raw_spinlock_init call for RT.
> >
>
> This is true, but to keep lockdep working I think we need to open code
> the PREEMPT_RT version of spin_lock_init(), please see below
>
> > Suggested-by: Clark Williams <williams@redhat.com>
> >
>
> ^ unnecessary emtpy line here.
Thanks for pointing it out. Should I fix it and send a v2?
>
> > Signed-off-by: Eder Zulian <ezulian@redhat.com>
> > ---
> > rust/helpers/spinlock.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/rust/helpers/spinlock.c b/rust/helpers/spinlock.c
> > index acc1376b833c..924c1a380448 100644
> > --- a/rust/helpers/spinlock.c
> > +++ b/rust/helpers/spinlock.c
> > @@ -6,7 +6,7 @@
> > void rust_helper___spin_lock_init(spinlock_t *lock, const char *name,
> > struct lock_class_key *key)
> > {
> > -#ifdef CONFIG_DEBUG_SPINLOCK
> > +#if defined(CONFIG_DEBUG_SPINLOCK) && !defined(CONFIG_PREEMPT_RT)
> > __raw_spin_lock_init(spinlock_check(lock), name, key, LD_WAIT_CONFIG);
> > #else
> > spin_lock_init(lock);
>
> This should be:
>
> void rust_helper___spin_lock_init(spinlock_t *lock, const char *name,
> struct lock_class_key *key)
> {
> #ifdef CONFIG_DEBUG_SPINLOCK
> # if defined(CONFIG_PREEMPT_RT)
Even though I don't have a strong preference on this, in my opinion, there is no
much difference here just a line break and inverted logic. Perhaps it would be
better to write like this: 'if (IS_ENABLED(CONFIG_PREEMPT_RT && ... ) { this }
else { that }', however, spinlock_check() is not declared for PREEMPT_RT
kernels because its declaration is conditional to #ifndef CONFIG_PREEMPT_RT in
'spinlock.h'. spinlock_check() as is does not make sense for PREEMPT_RT
because spinlock is not mapped to raw_spinlock but to rt_mutex (cf.
'spinlock_types.h')
> rt_mutex_base_init(&(lock)->lock);
> __rt_spin_lock_init(lock, name, key, false);
Apparently, this ^ matches spin_lock_init() in 'spinlock_rt.h', if true, we could
call spin_lock_init() for PREEMPT_RT kernels. However the debug version of
__rt_spin_lock_init() (instrumented with lockdep in 'spinlock_rt.c') depends
on CONFIG_DEBUG_LOCK_ALLOC. Luckily, in my opnion, the #ifdefs are already in
place.
> # else /* !CONFIG_PREEMPT_RT */
> __raw_spin_lock_init(spinlock_check(lock), name, key, LD_WAIT_CONFIG);
> # endif /* CONFIG_PREEMPT_RT */
> #else
> spin_lock_init(lock);
> #endif
> }
>
Please let me know what you think, and bear with me if I'm missing something.
Thanks.
> Regards,
> Boqun
>
> > --
> > 2.46.2
> >
> >
>
next prev parent reply other threads:[~2024-10-16 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 19:52 [PATCH] rust: Fix build error Eder Zulian
2024-10-14 20:31 ` Boqun Feng
2024-10-16 23:48 ` Eder Zulian [this message]
2024-10-14 20:38 ` Miguel Ojeda
2024-10-14 20:58 ` Boqun Feng
2024-10-17 0:15 ` Eder Zulian
2024-10-17 13:24 ` Miguel Ojeda
2024-11-04 11:09 ` Eder Zulian
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=ZxBQw1X_OG26RO9o@f39 \
--to=ezulian@redhat.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=williams@redhat.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).