From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org, Stable <stable@vger.kernel.org>,
Yury Norov <yury.norov@gmail.com>,
Amritha Nambiar <amritha.nambiar@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Kees Cook <keescook@chromium.org>,
Matthew Wilcox <willy@infradead.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Steffen Klassert <steffen.klassert@secunet.com>,
"Tobin C . Harding" <tobin@kernel.org>,
Vineet Gupta <vineet.gupta1@synopsys.com>,
Will Deacon <will.deacon@arm.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH RESEND] lib: fix bitmap_parse() on 64-bit big endian archs
Date: Mon, 8 Jun 2020 12:28:02 +0200 [thread overview]
Message-ID: <20200608102801.GA22989@oc3871087118.ibm.com> (raw)
In-Reply-To: <20200605132558.GM2428291@smile.fi.intel.com>
On Fri, Jun 05, 2020 at 04:25:58PM +0300, Andy Shevchenko wrote:
> Test case, please.
Hi Andy,
Below is the output of the runtime kernel test "test_bitmap".
I resent the patch with Andrew Morton on CC, but did not include
the excessive test output:
test_bitmap: parse: 4: input is 1, result is 0x100000000, expected 0x1
test_bitmap: parse: 5: input is deadbeef, result is 0xdeadbeef00000000, expected 0xdeadbeef
test_bitmap: parse: 6: input is 1,0, result is 0x1, expected 0x100000000
test_bitmap: parse: 7: input is deadbeef,,0,1, result is 0x1, expected 0xdeadbeef
test_bitmap: parse: 8: input is deadbeef,1,0, result is 0x1, expected 0x100000000
test_bitmap: parse: 9: input is baadf00d,deadbeef,1,0, result is 0x1, expected 0x100000000
test_bitmap: parse: 10: input is badf00d,deadbeef,1,0, errno is -75, expected 0
test_bitmap: parse: 11: input is badf00d,deadbeef,1,0, errno is -75, expected 0
test_bitmap: parse: 12: input is badf00d,deadbeef,1,0 , errno is -75, expected 0
test_bitmap: parse: 13: input is , badf00d,deadbeef,1,0 , , errno is -75, expected 0
test_bitmap: parse: 14: input is , badf00d, ,, ,,deadbeef,1,0 , , errno is -75, expected 0
test_bitmap: parse: 16: input is 3,0, errno is 0, expected -75
test_bitmap: parse_user: 4: input is 1, result is 0x100000000, expected 0x1
test_bitmap: parse_user: 5: input is deadbeef, result is 0xdeadbeef00000000, expected 0xdeadbeef
test_bitmap: parse_user: 6: input is 1,0, result is 0x1, expected 0x100000000
test_bitmap: parse_user: 7: input is deadbeef,,0,1, result is 0x1, expected 0xdeadbeef
test_bitmap: parse_user: 8: input is deadbeef,1,0, result is 0x1, expected 0x100000000
test_bitmap: parse_user: 9: input is baadf00d,deadbeef,1,0, result is 0x1, expected 0x100000000
test_bitmap: parse_user: 10: input is badf00d,deadbeef,1,0, errno is -75, expected 0
test_bitmap: parse_user: 11: input is badf00d,deadbeef,1,0, errno is -75, expected 0
test_bitmap: parse_user: 12: input is badf00d,deadbeef,1,0 , errno is -75, expected 0
test_bitmap: parse_user: 13: input is , badf00d,deadbeef,1,0 , , errno is -75, expected 0
test_bitmap: parse_user: 14: input is , badf00d, ,, ,,deadbeef,1,0 , , errno is -75, expected 0
test_bitmap: parse_user: 16: input is 3,0, errno is 0, expected -75
Thanks!
> Yes, you can simulate BE test case on LE platform and vise versa.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
prev parent reply other threads:[~2020-06-08 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 10:34 [PATCH RESEND] lib: fix bitmap_parse() on 64-bit big endian archs Alexander Gordeev
2020-05-18 11:33 ` Andy Shevchenko
2020-05-18 11:35 ` Andy Shevchenko
2020-05-18 11:51 ` Alexander Gordeev
2020-06-02 10:24 ` Alexander Gordeev
2020-06-05 13:25 ` Andy Shevchenko
2020-06-08 10:28 ` Alexander Gordeev [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=20200608102801.GA22989@oc3871087118.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=acme@redhat.com \
--cc=amritha.nambiar@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=tobin@kernel.org \
--cc=vineet.gupta1@synopsys.com \
--cc=will.deacon@arm.com \
--cc=willemb@google.com \
--cc=willy@infradead.org \
--cc=yury.norov@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 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).