linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Daniel Pinto <danielpinto52@gmail.com>,
	kernel test robot <lkp@intel.com>
Cc: <ntfs3@lists.linux.dev>, <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<oe-kbuild-all@lists.linux.dev>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH] fs/ntfs3: fix wrong cast in xattr.c
Date: Mon, 26 Dec 2022 19:07:50 +0400	[thread overview]
Message-ID: <9e11da02-80f1-55f3-8bb5-28c3508e5396@paragon-software.com> (raw)
In-Reply-To: <be1a2495-1c46-cda1-4f89-7e3a39d939db@gmail.com>

On 15.11.2022 12:17, Daniel Pinto wrote:
> cpu_to_be32 and be32_to_cpu respectively return and receive
> __be32, change the cast to the correct types.
>
> Fixes the following sparse warnings:
> fs/ntfs3/xattr.c:811:48: sparse: sparse: incorrect type in
>                           assignment (different base types)
> fs/ntfs3/xattr.c:901:34: sparse: sparse: cast to restricted __be32
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Daniel Pinto <danielpinto52@gmail.com>
> ---
>   fs/ntfs3/xattr.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ntfs3/xattr.c b/fs/ntfs3/xattr.c
> index 8620a7b4b3e6..6056ecbe8e4f 100644
> --- a/fs/ntfs3/xattr.c
> +++ b/fs/ntfs3/xattr.c
> @@ -808,7 +808,7 @@ static int ntfs_getxattr(const struct xattr_handler *handler, struct dentry *de,
>   			err = sizeof(u32);
>   			*(u32 *)buffer = le32_to_cpu(ni->std_fa);
>   			if (!strcmp(name, SYSTEM_NTFS_ATTRIB_BE))
> -				*(u32 *)buffer = cpu_to_be32(*(u32 *)buffer);
> +				*(__be32 *)buffer = cpu_to_be32(*(u32 *)buffer);
>   		}
>   		goto out;
>   	}
> @@ -898,7 +898,7 @@ static noinline int ntfs_setxattr(const struct xattr_handler *handler,
>   		if (size != sizeof(u32))
>   			goto out;
>   		if (!strcmp(name, SYSTEM_NTFS_ATTRIB_BE))
> -			new_fa = cpu_to_le32(be32_to_cpu(*(u32 *)value));
> +			new_fa = cpu_to_le32(be32_to_cpu(*(__be32 *)value));
>   		else
>   			new_fa = cpu_to_le32(*(u32 *)value);

Thank you for your work, applied!


      reply	other threads:[~2022-12-26 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  8:17 Daniel Pinto
2022-12-26 15:07 ` Konstantin Komarov [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=9e11da02-80f1-55f3-8bb5-28c3508e5396@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=danielpinto52@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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