public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Mike Snitzer <snitzer@kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs: add dummy definition for nfsd_file
Date: Wed, 26 Mar 2025 21:59:19 +0100	[thread overview]
Message-ID: <20250326205919.gdxxtcejde2jpil7@pali> (raw)
In-Reply-To: <eedc7b36-6ac1-498e-8e73-1608621d84f7@oss.qualcomm.com>

On Wednesday 26 March 2025 08:33:32 Jeff Johnson wrote:
> On 3/26/2025 8:09 AM, Mike Snitzer wrote:
> > Add dummy definition for nfsd_file in both nfslocalio.c and localio.c
> > so older gcc (e.g. EL8's 8.5.0) can be used.  Older gcc causes RCU
> > code (rcu_dereference and rcu_access_pointer) to dereference what
> > should just be an opaque pointer with its use of typeof.
> > 
> > So without the dummy definition compiling with older gcc fails.
> > 
> > Link: https://lore.kernel.org/all/Zsyhco1OrOI_uSbd@kernel.org/
> > Fixes: 55a9742d02eff ("nfs: cache all open LOCALIO nfsd_file(s) in client")

As this change is fixing compile error, should not be there also cc: stable line?

> 
> I saw this issue using crosstools/gcc-13.3.0-nolibc and this patch fixes it.

So maybe the commit message can be adjusted, so it does not say only
"older gcc"?

> Tested-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>

I have tested this change and it fixed compilation for me too. So:

Tested-by: Pali Rohár <pali@kernel.org>

> 
> > Signed-off-by: Mike Snitzer <snitzer@hammerspace.com>
> 
> note this doesn't match the From: address
> 
> 

  reply	other threads:[~2025-03-26 20:59 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 [this message]
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
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=20250326205919.gdxxtcejde2jpil7@pali \
    --to=pali@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=snitzer@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