public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Vincent Mailhol" <mailhol.vincent@wanadoo.fr>,
	"Trond Myklebust" <trond.myklebust@hammerspace.com>,
	"Anna Schumaker" <anna.schumaker@oracle.com>,
	"Pali Rohár" <pali@kernel.org>,
	linux-nfs@vger.kernel.org,
	"Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
	"Jeff Layton" <jlayton@kernel.org>, "Neil Brown" <neilb@suse.de>,
	"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: Fri, 18 Apr 2025 17:34:46 -0400	[thread overview]
Message-ID: <aALFdnEGTxF03uQd@kernel.org> (raw)
In-Reply-To: <425a2e7c-6d42-451b-b8f8-7c923ac0ed03@oracle.com>

On Wed, Apr 16, 2025 at 09:31:55AM -0400, Chuck Lever wrote:
> On 4/15/25 10:41 PM, Vincent Mailhol wrote:
> > +CC: Neil Brown
> > +CC: Olga Kornievskaia
> > +CC: Dai Ngo
> > +CC: Tom Talpey
> > +CC: Trond Myklebust
> > +CC: Anna Schumaker
> > 
> > (just to make sure that anyone listed in
> > 
> >   ./scripts/get_maintainer.pl fs/nfs_common/nfslocalio.c
> > 
> > get copied).
> > 
> > Here is the link to the full thread:
> > 
> >   https://lore.kernel.org/all/Z_coQbSdvMWD92IA@kernel.org/
> > 
> > 
> > On 10/04/2025 at 11:09, Mike Snitzer:
> >> Add dummy definition for nfsd_file in both nfslocalio.c and localio.c
> >> so various compilers (e.g. gcc 8.5.0 and 9.5.0) can be used. Otherwise
> >> RCU code (rcu_dereference and rcu_access_pointer) will dereference
> >> what should just be an opaque pointer (by using typeof(*ptr)).
> >>
> >> Fixes: 86e00412254a ("nfs: cache all open LOCALIO nfsd_file(s) in client")
> >> Cc: stable@vger.kernel.org
> >> Tested-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
> >> Tested-by: Pali Rohár <pali@kernel.org>
> >> Tested-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
> >> Signed-off-by: Mike Snitzer <snitzer@kernel.org>
> > 
> > Hi everyone,
> > 
> > The build has been broken for several weeks already. Does anyone have
> > intention to pick-up this patch?
> > 
> > (please ignore if someone already picked it up and if it is already on
> > its way to Linus's tree).
> 
> I assumed that, like all LOCALIO-related changes, this fix would go
> in through the NFS client tree. Let me know if it needs to go via NFSD.

Since we haven't heard from Trond or Anna about it, I think you'd be
perfectly fine to pick it up.  It is a compiler fixup associated with
nfd_file being kept opaque to the client -- but given it is "struct
nfsd_file" that gives you full license to grab it (IMO).

I'm also unaware of any conflicting changes in the NFS client tree.

  reply	other threads:[~2025-04-18 21:34 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 [this message]
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
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=aALFdnEGTxF03uQd@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=neilb@suse.de \
    --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