From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: David Disseldorp <ddiss@suse.de>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, christophe.jaillet@wanadoo.fr,
andriy.shevchenko@linux.intel.com, David.Laight@ACULAB.COM
Subject: Re: [PATCH v2 3/4] kstrtox: add unit tests for memparse_safe()
Date: Thu, 4 Jan 2024 09:15:33 +1030 [thread overview]
Message-ID: <a5a65a27-07bb-4399-bf28-1c27f9af6fbf@gmx.com> (raw)
In-Reply-To: <20240103011700.222b2b5c@echidna>
On 2024/1/3 00:47, David Disseldorp wrote:
> On Tue, 2 Jan 2024 14:42:13 +1030, Qu Wenruo wrote:
>
[...]
>> + {"P", -EINVAL},
>> +
>> + /* Overflow in the string itself*/
>> + {"18446744073709551616", -ERANGE},
>> + {"02000000000000000000000", -ERANGE},
>> + {"0x10000000000000000", -ERANGE},
> nit: ^ whitespace damage
Sorry, I didn't get the point here.
I checked the patch it's a single space.
Or I missed/screwed up something?
>> +
>> + /*
[...]
>> +
>> + /*
>> + * Finally one suffix then tailing chars, to test the @retptr
>> + * behavior.
>> + */
>> + {"68k ", 69632, 3},
>> + {"8MS", 8388608, 2},
>> + {"0xaeGis", 0x2b80000000, 5},
>> + {"0xaTx", 0xa0000000000, 4},
>> + {"3E8", 0x3000000000000000, 2},
>
> In future it'd be good to get some coverage for non-MEMPARSE_TEST_SUFFIX
> use cases, e.g.:
> /* supported suffix, but not provided with @suffixes */
> {"7K", (MEMPARSE_SUFFIX_M |\
> MEMPARSE_SUFFIX_G | MEMPARSE_SUFFIX_T |\
> MEMPARSE_SUFFIX_P | MEMPARSE_SUFFIX_E), 7, 1},
That's a great idea, since I'm still prepare a v3, it's not hard to add
it into v3.
Thanks,
Qu
>
>> + };
>> + unsigned int i;
>> +
>> + for_each_test(i, tests) {
>> + const struct memparse_test_ok *t = &tests[i];
>> + unsigned long long tmp;
>> + char *retptr;
>> + int ret;
>> +
>> + ret = memparse_safe(t->str, MEMPARSE_TEST_SUFFIX, &tmp, &retptr);
>> + if (ret != 0) {
>> + WARN(1, "str '%s', expected ret 0 got %d\n", t->str, ret);
>> + continue;
>> + }
>> + if (tmp != t->expected_value)
>> + WARN(1, "str '%s' incorrect result, expected %llu got %llu",
>> + t->str, t->expected_value, tmp);
>> + if (retptr != t->str + t->retptr_off)
>> + WARN(1, "str '%s' incorrect endptr, expected %u got %zu",
>> + t->str, t->retptr_off, retptr - t->str);
>> + }
>> +}
>> static void __init test_kstrtoll_fail(void)
>> {
>> static DEFINE_TEST_FAIL(test_ll_fail) = {
>> @@ -710,6 +941,10 @@ static int __init test_kstrtox_init(void)
>> test_kstrtoll_ok();
>> test_kstrtoll_fail();
>>
>> + test_memparse_safe_ok();
>> + test_memparse_safe_fail();
>> +
>> +
> nit: whitespace ^
>
>> test_kstrtou64_ok();
>> test_kstrtou64_fail();
>> test_kstrtos64_ok();
>
> With Geert's comments addressed:
> Reviewed-by: David Disseldorp <ddiss@suse.de>
>
next prev parent reply other threads:[~2024-01-03 22:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 4:12 [PATCH v2 0/4] kstrtox: introduce memparse_safe() Qu Wenruo
2024-01-02 4:12 ` [PATCH v2 1/4] kstrtox: always skip the leading "0x" even if no more valid chars Qu Wenruo
2024-01-02 14:16 ` David Disseldorp
2024-01-02 4:12 ` [PATCH v2 2/4] kstrtox: introduce a safer version of memparse() Qu Wenruo
2024-01-02 14:19 ` David Disseldorp
2024-01-02 4:12 ` [PATCH v2 3/4] kstrtox: add unit tests for memparse_safe() Qu Wenruo
2024-01-02 13:23 ` Geert Uytterhoeven
2024-01-02 20:55 ` Qu Wenruo
2024-01-03 9:27 ` Geert Uytterhoeven
2024-01-03 9:45 ` Qu Wenruo
2024-01-02 14:17 ` David Disseldorp
2024-01-03 22:45 ` Qu Wenruo [this message]
2024-01-02 4:12 ` [PATCH v2 4/4] btrfs: migrate to the newer memparse_safe() helper Qu Wenruo
2024-01-02 14:24 ` David Disseldorp
2024-01-02 17:10 ` [PATCH v2 0/4] kstrtox: introduce memparse_safe() David Sterba
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=a5a65a27-07bb-4399-bf28-1c27f9af6fbf@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=David.Laight@ACULAB.COM \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=ddiss@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wqu@suse.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