All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: cel@kernel.org
Cc: stable@kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
	stable@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH 6.8.y] NFSD: fix endianness issue in nfsd4_encode_fattr4
Date: Tue, 23 Apr 2024 09:46:56 -0700	[thread overview]
Message-ID: <2024042332-feminize-showing-b4a4@gregkh> (raw)
In-Reply-To: <20240423163702.11681-1-cel@kernel.org>

On Tue, Apr 23, 2024 at 12:37:02PM -0400, cel@kernel.org wrote:
> From: Vasily Gorbik <gor@linux.ibm.com>
> 
> [ Upstream commit f488138b526715c6d2568d7329c4477911be4210 ]
> 
> The nfs4 mount fails with EIO on 64-bit big endian architectures since
> v6.7. The issue arises from employing a union in the nfsd4_encode_fattr4()
> function to overlay a 32-bit array with a 64-bit values based bitmap,
> which does not function as intended. Address the endianness issue by
> utilizing bitmap_from_arr32() to copy 32-bit attribute masks into a
> bitmap in an endianness-agnostic manner.
> 
> Cc: stable@vger.kernel.org
> Fixes: fce7913b13d0 ("NFSD: Use a bitmask loop to encode FATTR4 results")
> Link: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217
> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
> [ cel: adjusted to apply on 6.8.y ]

This is already in the queue for 6.8.y, perhaps you missed the email
saying that.

Anyway, thanks for the patch, all should be good now.

greg k-h

      reply	other threads:[~2024-04-23 16:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 10:37 FAILED: patch "[PATCH] NFSD: fix endianness issue in nfsd4_encode_fattr4" failed to apply to 6.8-stable tree gregkh
2024-04-19 16:03 ` [PATCH 6.8.y] NFSD: fix endianness issue in nfsd4_encode_fattr4 cel
2024-04-23 16:26   ` Greg KH
2024-04-23 16:30     ` Chuck Lever III
2024-04-23 16:34       ` Greg KH
2024-04-23 16:37 ` cel
2024-04-23 16:46   ` Greg KH [this message]

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=2024042332-feminize-showing-b4a4@gregkh \
    --to=greg@kroah.com \
    --cc=cel@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=jlayton@kernel.org \
    --cc=stable@kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.