From: Mike Snitzer <snitzer@kernel.org>
To: NeilBrown <neil@brown.name>
Cc: "Vincent Mailhol" <mailhol.vincent@wanadoo.fr>,
"Pali Rohár" <pali@kernel.org>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Trond Myklebust" <trond.myklebust@hammerspace.com>,
"Anna Schumaker" <anna.schumaker@oracle.com>,
linux-nfs@vger.kernel.org,
"Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
"Jeff Layton" <jlayton@kernel.org>,
"Olga Kornievskaia" <okorniev@redhat.com>,
"Dai Ngo" <Dai.Ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
"Trond Myklebust" <trondmy@kernel.org>,
"Anna Schumaker" <anna@kernel.org>
Subject: Re: [PATCH v2] nfs: add dummy definition for nfsd_file
Date: Thu, 24 Apr 2025 12:04:03 -0400 [thread overview]
Message-ID: <aApg86mNKak2e--H@kernel.org> (raw)
In-Reply-To: <174539938027.500591.1190076221216165031@noble.neil.brown.name>
On Wed, Apr 23, 2025 at 07:09:40PM +1000, NeilBrown wrote:
> On Wed, 23 Apr 2025, Vincent Mailhol wrote:
> > On 23/04/2025 at 09:32, NeilBrown wrote:
> > > On Wed, 23 Apr 2025, Pali Rohár wrote:
> > >> On Wednesday 23 April 2025 07:54:40 NeilBrown wrote:
> > >>> On Wed, 23 Apr 2025, Pali Rohár wrote:
> >
> > (...)
> >
> > >>> Actually I do object to this fix (though I've been busy and hadn't had
> > >>> much change to look at it properly).
> > >>> The fix is ugly. At the very least it should be wrapping in an
> > >>> #if GCC_VERSION < whatever
> >
> > I acknowledge that the fix is a bit ugly, but Mike is the only one who
> > has proposed a solution so far.
>
> FYI here is my current patch which fixes this problem and a few other
> problems, but doesn't fix everything I (think I) have found, and may
> introduce some problems because some of the interactions are subtle and
> need careful review.
>
> Once I'm confident of it I hope to break it up into individual patches
> and submit.
Thanks for working through it (and sorry for the troubles...).
This was where we last discussed the need for my hack (I actually
thought it was older RCU implementation in 5.15 that was the issue):
https://lore.kernel.org/all/Zsyhco1OrOI_uSbd@kernel.org/
(somehow it morphed into blaming vintage compilers, e.g. RHEL8's gcc
8.5 or whatever).
We have stable@ kernels to be concerned about. But hopefully you
carry forward with splitting up the patches like you've planned, they
all make sense and they all get marked for stable@ (6.14+). Saves the
make-work of effectively implementing the fixes twice (purely for
stable's benefit, by needing to pull your subtle rcu race fixes to the
front).
Thanks,
Mike
next prev parent reply other threads:[~2025-04-24 16:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 12:00 nfs compile error nfslocalio.o and localio.o since v6.14-rc1 Pali Rohár
2025-02-15 16:29 ` Chuck Lever
2025-02-15 16:38 ` Pali Rohár
2025-02-15 16:41 ` Chuck Lever
2025-02-15 16:51 ` Pali Rohár
2025-02-23 18:27 ` Pali Rohár
2025-03-18 19:05 ` Pali Rohár
2025-03-25 18:25 ` Jeff Johnson
2025-03-26 15:09 ` [PATCH] nfs: add dummy definition for nfsd_file Mike Snitzer
2025-03-26 15:33 ` Jeff Johnson
2025-03-26 20:59 ` Pali Rohár
2025-03-27 2:00 ` Mike Snitzer
2025-03-27 8:28 ` Pali Rohár
2025-03-27 20:17 ` Mike Snitzer
2025-04-09 12:17 ` [PATCH] " Vincent Mailhol
2025-04-10 2:09 ` [PATCH v2] " Mike Snitzer
2025-04-16 2:41 ` Vincent Mailhol
2025-04-16 13:31 ` Chuck Lever
2025-04-18 21:34 ` Mike Snitzer
2025-04-19 17:52 ` Chuck Lever
2025-04-20 16:12 ` Mike Snitzer
2025-04-22 20:16 ` Pali Rohár
2025-04-22 21:54 ` NeilBrown
2025-04-22 22:02 ` Pali Rohár
2025-04-23 0:32 ` NeilBrown
2025-04-23 6:47 ` Vincent Mailhol
2025-04-23 8:45 ` Vincent Mailhol
2025-04-23 9:09 ` NeilBrown
2025-04-23 10:03 ` Vincent Mailhol
2025-04-24 16:04 ` Mike Snitzer [this message]
2025-05-04 9:07 ` Pali Rohár
2025-05-07 2:29 ` NeilBrown
2025-04-23 14:59 ` Chuck Lever
2025-04-21 11:52 ` Jeff Layton
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=aApg86mNKak2e--H@kernel.org \
--to=snitzer@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=anna.schumaker@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=pali@kernel.org \
--cc=tom@talpey.com \
--cc=trond.myklebust@hammerspace.com \
--cc=trondmy@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