From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH v2] test/xattr: don't rely on NUL-termination
Date: Tue, 16 Aug 2022 06:23:23 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 16 Aug 2022 12:51:34 +0200, Jiri Slaby wrote:
> The returned value from io_uring_fgetxattr() needs not be NUL-terminated,
> as we stored non-NUL-terminated string by io_uring_fsetxattr()
> previously.
>
> So don't use strlen() on value, but on VALUE1, and VALUE2 respectively.
>
> This fixes random test failures.
>
> [...]
Applied, thanks!
[1/1] test/xattr: don't rely on NUL-termination
commit: bf3fedba890e66d644692910964fe1d8cbf4fb1b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-08-16 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2022-08-16 10:51 ` [PATCH v2] test/xattr: don't rely on NUL-termination Jiri Slaby
2022-08-16 12:23 ` Jens Axboe [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=166065260332.198111.1252860082138342519.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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