From: Li Wang <li.wang@linux.dev>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 2/3] swapon04: Add test for discard flags
Date: Fri, 28 Aug 2026 17:01:02 +0800 [thread overview]
Message-ID: <apFOTreIdNbi2U72@linux.dev> (raw)
In-Reply-To: <6a914b26.1f1211b9.7a419.d9d7@mx.google.com>
> > this is interesting. Also I notice how it's hard to read the logs, so
> > I need a TINFO before the checks. But technically, this could be a kernel
> > bug: can you please add a sync() before stat() while we are getting the
> > blocks_after? We might need to flush the cache before reading the blocks.
> >
> > fd = SAFE_OPEN(BACKING_FILE, O_RDONLY);
> > SAFE_FSYNC(fd);
> > SAFE_CLOSE(fd);
>
> sorry, this should stay after the tst_fill_file()
Great, this works!
I think the fsync after tst_fill_file() ensures all allocated blocks are
flushed to disk, so stat() reflects the real block count.
Feel free to add my RBT with this change applied:
Reviewed-by: Li Wang <li.wang@linux.dev>
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-28 9:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 11:54 [LTP] [PATCH 0/3] Increase coverage for swapon syscall Andrea Cervesato
2026-08-27 11:54 ` [LTP] [PATCH 1/3] lapi: fallback definitions " Andrea Cervesato
2026-08-27 13:58 ` [LTP] " linuxtestproject.agent
2026-08-28 7:54 ` [LTP] [PATCH 1/3] " Li Wang
2026-08-27 11:54 ` [LTP] [PATCH 2/3] swapon04: Add test for discard flags Andrea Cervesato
2026-08-28 3:57 ` Li Wang
2026-08-28 8:30 ` Andrea Cervesato via ltp
2026-08-28 8:47 ` Li Wang
2026-08-28 9:02 ` Andrea Cervesato via ltp
2026-08-28 8:47 ` Andrea Cervesato via ltp
2026-08-28 9:01 ` Li Wang [this message]
2026-08-28 9:02 ` Andrea Cervesato via ltp
2026-08-28 9:12 ` Li Wang
2026-08-27 11:54 ` [LTP] [PATCH 3/3] swapon02: Add test cases for invalid swapflags Andrea Cervesato
2026-08-28 7:59 ` Li Wang
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=apFOTreIdNbi2U72@linux.dev \
--to=li.wang@linux.dev \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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