From: Adrian Garcia Casado <adriangarciacasado42@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gfs2: add missing __rcu annotation to i_gl in incore.h
Date: Fri, 24 Jul 2026 18:50:00 +0200 [thread overview]
Message-ID: <6a639813.e862d496.345987.397e@mx.google.com> (raw)
Hi Andreas,
I am terribly sorry for the confusion and the noise in my previous email.
I completely misread your message and drafted a rushed reply by mistake.
Please disregard my previous "Thanks for applying" message.
You are absolutely right. Adding the __rcu annotation only exposes the
200 sparse warnings without fixing the actual underlying RCU dereferences,
which is indeed not very useful for upstream yet.
I will go back and work on a proper patch series to cleanly address those
underlying RCU dereference warnings in fs/gfs2/ before submitting again.
My sincere apologies for the noise, and thank you for your patience and
valuable feedback.
Best regards,
Adrian
next reply other threads:[~2026-07-24 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 16:50 Adrian Garcia Casado [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-24 16:08 [PATCH] gfs2: add missing __rcu annotation to i_gl in incore.h Adrian Garcia Casado
2026-07-24 16:08 Adrian Garcia Casado
2026-07-23 17:44 Adrian Garcia Casado
2026-06-30 10:02 Adrian Garcia Casado
2026-07-24 15:32 ` Andreas Gruenbacher
[not found] ` <CA+cq9YO=6PJ1Xx97vMuWsv+h8ebe2a8mKYoktuyZOY6MBKRxzg@mail.gmail.com>
2026-07-24 16:17 ` Andreas Gruenbacher
2026-06-30 9:55 Adrian Garcia Casado
2026-06-18 13:56 Adrian
2026-06-18 13:56 Adrian
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=6a639813.e862d496.345987.397e@mx.google.com \
--to=adriangarciacasado42@gmail.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).