From: Florian Weimer <fweimer@redhat.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v3 3/3] statvfs: f_type: NEWS & test
Date: Tue, 15 Aug 2023 16:23:37 +0200 [thread overview]
Message-ID: <87bkf8bd06.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <vnadk34jclmnuin5fga7yaqbjlv4afsrham4bn6pfvalon6whg@2dwrwyrkbxar> (=?utf-8?B?ItC90LDQsSIncw==?= message of "Tue, 15 Aug 2023 15:07:59 +0200")
* наб:
> Subject: [PATCH] io/tst-statvfs: fix statfs().f_type comparison test on some
> arches
>
> On i686 f_type is an i32 so the test fails when that has the top bit set.
>
> Explicitly cast to u32.
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> io/tst-statvfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/io/tst-statvfs.c b/io/tst-statvfs.c
> index f3097ce1a8..fb23733667 100644
> --- a/io/tst-statvfs.c
> +++ b/io/tst-statvfs.c
> @@ -16,7 +16,7 @@ do_test (int argc, char *argv[])
> struct statfs stf;
> TEST_COMPARE (statvfs (argv[i], &st), 0);
> TEST_COMPARE (statfs (argv[i], &stf), 0);
> - TEST_COMPARE (st.f_type, stf.f_type);
> + TEST_COMPARE (st.f_type, (unsigned int) stf.f_type);
> printf ("%s: free: %llu, mandatory: %s, tp=%x\n", argv[i],
> (unsigned long long int) st.f_bfree,
> #ifdef ST_MANDLOCK
Looks good.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
Can you install this yourself, or should I push it?
Thanks,
Florian
next prev parent reply other threads:[~2023-08-15 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 14:59 [PATCH v3 1/3] hurd: statvfs: __f_type -> f_type наб
2023-07-03 14:59 ` [PATCH v3 2/3] linux: statvfs: allocate spare for f_type наб
2023-07-21 13:03 ` Adhemerval Zanella Netto
2023-07-21 15:34 ` наб
2023-07-23 19:10 ` Adhemerval Zanella Netto
2023-07-03 14:59 ` [PATCH v3 3/3] statvfs: f_type: NEWS & test наб
2023-07-21 13:04 ` Adhemerval Zanella Netto
2023-08-15 9:15 ` Florian Weimer
2023-08-15 11:54 ` Adhemerval Zanella Netto
2023-08-15 12:41 ` Florian Weimer
2023-08-15 12:48 ` Adhemerval Zanella Netto
2023-08-15 13:07 ` наб
2023-08-15 14:23 ` Florian Weimer [this message]
2023-08-15 14:37 ` наб
2023-08-15 15:09 ` Florian Weimer
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=87bkf8bd06.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).