From: David Laight <David.Laight@ACULAB.COM>
To: "x86@kernel.org" <x86@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: RE: [PATCH] x86: Optimise x86 IP checksum code
Date: Mon, 9 Dec 2019 17:12:57 +0000 [thread overview]
Message-ID: <8ae91feb2edc47f08eda5212dbf05183@AcuMS.aculab.com> (raw)
In-Reply-To: <201912060941.f3Qi9xtV%lkp@intel.com>
From: kbuild test robot
> Sent: 06 December 2019 01:45
>
> [auto build test WARNING on tip/auto-latest]
> [also build test WARNING on tip/x86/core linus/master v5.4 next-20191202]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/David-Laight/x86-Optimise-x86-IP-checksum-code/20191203-211313
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git e445033e58108a9891abfbc0dea90b066a75e4a9
> reproduce:
> # apt-get install sparse
> # sparse version: v0.6.1-91-g817270f-dirty
> make ARCH=x86_64 allmodconfig
> make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
>
> >> arch/x86/lib/csum-partial_64.c:141:23: sparse: sparse: incorrect type in return expression (different base types) @@ expected
> restricted __wsum @@ got icted __wsum @@
> >> arch/x86/lib/csum-partial_64.c:141:23: sparse: expected restricted __wsum
> >> arch/x86/lib/csum-partial_64.c:141:23: sparse: got unsigned int
>
> vim +141 arch/x86/lib/csum-partial_64.c
>
...
> 138 */
> 139 __wsum csum_partial(const void *buff, int len, __wsum sum)
> 140 {
> > 141 return do_csum(buff, len, (__force u32)sum);
> 142 }
> 143 EXPORT_SYMBOL(csum_partial);
> 144
I can regenerate the patch with the (__force __wsum) cast added back in.
Anyone going to review the changes?
I've tested all (I hope) of the corner cases in a user-space test program.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2019-12-09 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 11:52 [PATCH] x86: Optimise x86 IP checksum code David Laight
2019-12-04 9:14 ` Peter Zijlstra
2019-12-04 10:06 ` David Laight
2019-12-06 1:45 ` kbuild test robot
2019-12-09 17:12 ` David Laight [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=8ae91feb2edc47f08eda5212dbf05183@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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