netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Li, Ke" <keli@akamai.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kli@udel.edu" <kli@udel.edu>, "Li, Ji" <jli@akamai.com>
Subject: Re: [PATCH net] net: Properly typecast int values to set sk_max_pacing_rate
Date: Thu, 22 Oct 2020 06:31:06 +0000	[thread overview]
Message-ID: <15C07001-BF04-4430-834F-E1973F866DC5@akamai.com> (raw)
In-Reply-To: <20201021205320.57cb4c6f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

Thanks for review and comment, Jakub!
Please check my v2 patch.

Best,
-Ke

On 10/21/20, 8:53 PM, "Jakub Kicinski" <kuba@kernel.org> wrote:

    On Mon, 19 Oct 2020 20:31:49 -0400 Ke Li wrote:
    > In setsockopt(SO_MAX_PACING_RATE) on 64bit systems, sk_max_pacing_rate,
    > after extended from 'u32' to 'unsigned long', takes unintentionally
    > hiked value whenever assigned from an 'int' value with MSB=1, due to
    > binary sign extension in promoting s32 to u64, e.g. 0x80000000 becomes
    > 0xFFFFFFFF80000000.
    > 
    > Thus inflated sk_max_pacing_rate causes subsequent getsockopt to return
    > ~0U unexpectedly. It may also result in increased pacing rate.
    > 
    > Fix by explicitly casting the 'int' value to 'unsigned int' before
    > assigning it to sk_max_pacing_rate, for zero extension to happen.
    > 
    > Fixes: 76a9ebe811fb ("net: extend sk_pacing_rate to unsigned long")
    > Signed-off-by: Ji Li <jli@akamai.com>
    > Signed-off-by: Ke Li <keli@akamai.com>
    > Cc: Eric Dumazet <edumazet@google.com>
    > ---
    >  net/core/filter.c | 2 +-
    >  net/core/sock.c   | 2 +-
    >  2 files changed, 2 insertions(+), 2 deletions(-)
    > 
    > diff --git a/net/core/filter.c b/net/core/filter.c
    > index c5e2a1c5fd8d..43f20c14864c 100644
    > --- a/net/core/filter.c
    > +++ b/net/core/filter.c
    > @@ -4693,7 +4693,7 @@ static int _bpf_setsockopt(struct sock *sk, int level, int optname,
    >  				cmpxchg(&sk->sk_pacing_status,
    >  					SK_PACING_NONE,
    >  					SK_PACING_NEEDED);
    > -			sk->sk_max_pacing_rate = (val == ~0U) ? ~0UL : val;
    > +			sk->sk_max_pacing_rate = (val == ~0U) ? ~0UL : (unsigned int)val;

    Looks good, but please wrap this to 80 chars.

    >  			sk->sk_pacing_rate = min(sk->sk_pacing_rate,
    >  						 sk->sk_max_pacing_rate);
    >  			break;
    > diff --git a/net/core/sock.c b/net/core/sock.c
    > index 4e8729357122..727ea1cc633c 100644
    > --- a/net/core/sock.c
    > +++ b/net/core/sock.c
    > @@ -1163,7 +1163,7 @@ int sock_setsockopt(struct socket *sock, int level, int optname,
    >  
    >  	case SO_MAX_PACING_RATE:
    >  		{
    > -		unsigned long ulval = (val == ~0U) ? ~0UL : val;
    > +		unsigned long ulval = (val == ~0U) ? ~0UL : (unsigned int)val;
    >  
    >  		if (sizeof(ulval) != sizeof(val) &&
    >  		    optlen >= sizeof(ulval) &&
    > 
    > base-commit: 0e8b8d6a2d85344d80dda5beadd98f5f86e8d3d3



      reply	other threads:[~2020-10-22  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20  0:31 [PATCH net] net: Properly typecast int values to set sk_max_pacing_rate Ke Li
2020-10-22  3:53 ` Jakub Kicinski
2020-10-22  6:31   ` Li, Ke [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=15C07001-BF04-4430-834F-E1973F866DC5@akamai.com \
    --to=keli@akamai.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jli@akamai.com \
    --cc=kli@udel.edu \
    --cc=kuba@kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).