All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Ujwal Kundur <ujwal.kundur@gmail.com>
Cc: allison.henderson@oracle.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rds: Fix endian annotations across various assignments
Date: Sun, 10 Aug 2025 19:38:55 +0100	[thread overview]
Message-ID: <20250810183855.GN222315@ZenIV> (raw)
In-Reply-To: <20250810174705.GK222315@ZenIV>

On Sun, Aug 10, 2025 at 06:47:05PM +0100, Al Viro wrote:

> > diff --git a/net/rds/connection.c b/net/rds/connection.c
> > index d62f486ab29f..0047b76c3c0b 100644
> > --- a/net/rds/connection.c
> > +++ b/net/rds/connection.c
> > @@ -62,13 +62,13 @@ static struct hlist_head *rds_conn_bucket(const struct in6_addr *laddr,
> >  	net_get_random_once(&rds_hash_secret, sizeof(rds_hash_secret));
> >  	net_get_random_once(&rds6_hash_secret, sizeof(rds6_hash_secret));
> >  
> > -	lhash = (__force u32)laddr->s6_addr32[3];
> > +	lhash = (__force __u32)laddr->s6_addr32[3];
> >  #if IS_ENABLED(CONFIG_IPV6)
> >  	fhash = __ipv6_addr_jhash(faddr, rds6_hash_secret);
> >  #else
> > -	fhash = (__force u32)faddr->s6_addr32[3];
> > +	fhash = (__force __u32)(faddr->s6_addr32[3]);
> >  #endif
> > -	hash = __inet_ehashfn(lhash, 0, fhash, 0, rds_hash_secret);
> > +	hash = __inet_ehashfn((__force __be32)lhash, 0, (__force __be32)fhash, 0, rds_hash_secret);
> 
> what the...  You have lhash and fhash set to __be32 values, then
> feed them to function that expects __be32 argument.  Just turn
> these two variables into __be32 and lose the pointless casts.

FWIW, here you do have a missing cast -
	fhash = __ipv6_addr_jhash(faddr, rds6_hash_secret);
should be
	fhash = (__force __be32)__ipv6_addr_jhash(faddr, rds6_hash_secret);
With both fhash and lhash declared as __be32.

      parent reply	other threads:[~2025-08-10 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 17:11 [PATCH net] rds: Fix endian annotations across various assignments Ujwal Kundur
2025-08-10 17:32 ` Andrew Lunn
2025-08-10 17:47 ` Al Viro
2025-08-10 18:25   ` Al Viro
2025-08-10 18:27     ` Al Viro
2025-08-10 18:41     ` Andrew Lunn
2025-08-10 19:26       ` Al Viro
2025-08-10 19:31       ` Ujwal Kundur
2025-08-10 20:19         ` Andrew Lunn
2025-08-10 21:00         ` Al Viro
2025-08-10 21:13           ` Al Viro
2025-08-10 18:38   ` Al Viro [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=20250810183855.GN222315@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=allison.henderson@oracle.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rds-devel@oss.oracle.com \
    --cc=ujwal.kundur@gmail.com \
    /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.