public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charlie Jenkins <charlie@rivosinc.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: David Laight <David.Laight@aculab.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 0/2] lib: checksum: Fix issues with checksum tests
Date: Tue, 23 Jan 2024 16:23:30 -0800	[thread overview]
Message-ID: <ZbBYgmBZ/1BRPi3S@ghost> (raw)
In-Reply-To: <84790a56-1c7c-4ddb-a4da-17dc84c1f670@roeck-us.net>

On Tue, Jan 23, 2024 at 03:22:30PM -0800, Guenter Roeck wrote:
> On 1/23/24 13:58, Charlie Jenkins wrote:
> > The ip_fast_csum and csum_ipv6_magic tests did not have the data
> > types properly casted, and improperly misaligned data.
> > 
> > Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> > ---
> > Changes in v2:
> > - Add additional patch to fix alignment issues
> > - Link to v1: https://lore.kernel.org/r/20240119-fix_sparse_errors_checksum_tests-v1-1-2d3df86d8d78@rivosinc.com
> > 
> 
> I applied both patches but see the following.
> 
>     KTAP version 1
>     # Subtest: checksum
>     # module: checksum_kunit
>     1..5
>     ok 1 test_csum_fixed_random_inputs
>     ok 2 test_csum_all_carry_inputs
>     ok 3 test_csum_no_carry_inputs
>     # test_ip_fast_csum: ASSERTION FAILED at lib/checksum_kunit.c:541
>     Expected ( u64)csum_result == ( u64)expected, but
>         ( u64)csum_result == 27015 (0x6987)
>         ( u64)expected == 55912 (0xda68)
>     not ok 4 test_ip_fast_csum
>     # test_csum_ipv6_magic: ASSERTION FAILED at lib/checksum_kunit.c:564
>     Expected ( u64)csum_result == ( u64)expected, but
>         ( u64)csum_result == 42151 (0xa4a7)
>         ( u64)expected == 5513 (0x1589)
>     not ok 5 test_csum_ipv6_magic
> # checksum: pass:3 fail:2 skip:0 total:5
> # Totals: pass:3 fail:2 skip:0 total:5
> not ok 17 checksum
> 
> Old result, before applying the patches (v6.8-rc1):
> 
>     KTAP version 1
>     # Subtest: checksum
>     # module: checksum_kunit
>     1..5
>     ok 1 test_csum_fixed_random_inputs
>     ok 2 test_csum_all_carry_inputs
>     ok 3 test_csum_no_carry_inputs
>     ok 4 test_ip_fast_csum
>     ok 5 test_csum_ipv6_magic
> # checksum: pass:5 fail:0 skip:0 total:5
> # Totals: pass:5 fail:0 skip:0 total:5
> ok 17 checksum
> 
> This is with the imx25-pdk emulation in qemu.
> 
> Guenter

Apologies for that, some garbage values snuck in. I'll send a new
version.

- Charlie

> 

      reply	other threads:[~2024-01-24  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 21:58 [PATCH v2 0/2] lib: checksum: Fix issues with checksum tests Charlie Jenkins
2024-01-23 21:58 ` [PATCH v2 1/2] lib: checksum: Fix type casting in checksum kunits Charlie Jenkins
2024-01-23 21:58 ` [PATCH v2 2/2] lib: checksum: Use aligned accesses for ip_fast_csum and csum_ipv6_magic tests Charlie Jenkins
2024-01-23 23:22 ` [PATCH v2 0/2] lib: checksum: Fix issues with checksum tests Guenter Roeck
2024-01-24  0:23   ` Charlie Jenkins [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=ZbBYgmBZ/1BRPi3S@ghost \
    --to=charlie@rivosinc.com \
    --cc=David.Laight@aculab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkp@intel.com \
    --cc=palmer@dabbelt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox