From: Vitaly Chikunov <vt@altlinux.org>
To: LTP List <ltp@lists.linux.it>,
Yang Xu <xuyang2018.jy@fujitsu.com>,
Cyril Hrubis <chrubis@suse.cz>
Cc: "Dmitry V. Levin" <ldv@altlinux.org>
Subject: [LTP] statx01 test failure/bug on i586
Date: Tue, 1 Nov 2022 19:07:44 +0300 [thread overview]
Message-ID: <20221101160744.4qb3adfwaf375e6v@altlinux.org> (raw)
Hello,
We got statx01 failure on LTP 20220930 for runs on i586 arch.
statx01.c:98: TPASS: statx(AT_FDCWD, test_file, 0, 0, &buff)
statx01.c:105: TPASS: stx_uid(0) is correct
statx01.c:111: TPASS: stx_gid(0) is correct
statx01.c:117: TPASS: stx_size(256) is correct
statx01.c:125: TPASS: stx_mode(33188) is correct
statx01.c:131: TPASS: stx_blocks(8) is valid
statx01.c:138: TPASS: stx_nlink(1) is correct
statx01.c:82: TFAIL: statx.stx_mnt_id(23) is different from mount_id(13820440305888919575) in /proc/self/mountinfo
statx01.c:88: TPASS: /proc/9494/fdinfo/3 mnt_id: = 23
statx01.c:156: TPASS: statx(AT_FDCWD, mntpoint/blk_dev, 0, 0, &buff)
statx01.c:163: TPASS: stx_rdev_major(8) is correct
statx01.c:171: TPASS: stx_rdev_minor(1) is correct
Value "13820440305888919575" hints there may be integer overflow.
On Tue, Nov 01, 2022 at 06:31:20PM +0300, Dmitry V. Levin wrote:
> $ grep -Fwn mnt_id testcases/kernel/syscalls/statx/statx01.c
> 20: * - mnt_id
> 58: uint64_t mnt_id;
> 68: if (sscanf(line, "%ld %*d %d:%d", &mnt_id, &line_mjr, &line_mnr) != 3)
> ...
On 32-bit systems sscanf of %ld would leave higher part of mnt_id
uninitialized, resulting in false positive test failure.
Thanks,
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-11-01 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 16:07 Vitaly Chikunov [this message]
2022-11-02 9:12 ` [LTP] statx01 test failure/bug on i586 Cyril Hrubis
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=20221101160744.4qb3adfwaf375e6v@altlinux.org \
--to=vt@altlinux.org \
--cc=chrubis@suse.cz \
--cc=ldv@altlinux.org \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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