From: Disha Goel <disgoel@linux.ibm.com>
To: Christian Brauner <brauner@kernel.org>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 1/2] selftests/filesystems: Move file_stressor to dedicated subdirectory
Date: Mon, 31 Aug 2026 15:24:03 +0530 [thread overview]
Message-ID: <31368a5a-989a-46ff-a3e2-ec0e7838a7d5@linux.ibm.com> (raw)
In-Reply-To: <20260831-klopfen-gedenken-vorleben-54fd9d119a83@brauner>
On 31/08/26 1:20 pm, Christian Brauner wrote:
> On Thu, 21 May 2026 15:47:56 +0530, Disha Goel wrote:
>> The file_stressor test requires a 30-minute timeout (1800 seconds) due to
>> its 15-minute runtime plus setup/teardown overhead. This is significantly
>> longer than the default 45-second timeout used by other filesystem tests.
>>
>> Move file_stressor into its own subdirectory (filesystems/file_stressor/)
>> with a dedicated settings file to isolate its timeout configuration. This
>> prevents the long timeout from affecting other fast-running tests in the
>> filesystems/ directory.
>>
>> [...]
>
> Applied to the vfs-7.4.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-7.4.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-7.4.misc
>
> [1/2] selftests/filesystems: Move file_stressor to dedicated subdirectory
> https://git.kernel.org/vfs/vfs/c/5550456dad37
> [2/2] selftests/filesystems: allow security.selinux xattr in listxattr kernfs test
> https://git.kernel.org/vfs/vfs/c/cc87d0a97bc0
Hi Christian,
Thanks for applying the series. One note — v3 of this series was sent on
03/08/26, and patch 2/2 had changes compared to v2. It looks like v2 was
applied instead.
v3 patch 2/2 link:
https://lore.kernel.org/linux-kselftest/20260803150837.91604-1-disgoel@linux.ibm.com/
Could you update the applied commit with the v3 version, or let me know
if a re-send is needed?
--
Regards,
Disha
prev parent reply other threads:[~2026-08-31 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 10:17 [PATCH v2 1/2] selftests/filesystems: Move file_stressor to dedicated subdirectory Disha Goel
2026-05-21 10:17 ` [PATCH v2 2/2] selftests/filesystems: allow security.selinux xattr in listxattr kernfs test Disha Goel
2026-06-15 5:19 ` Ojaswin Mujoo
2026-06-17 11:18 ` Yeswanth Krishna
2026-06-15 5:12 ` [PATCH v2 1/2] selftests/filesystems: Move file_stressor to dedicated subdirectory Ojaswin Mujoo
2026-06-17 11:14 ` Yeswanth Krishna
2026-08-31 7:50 ` Christian Brauner
2026-08-31 9:54 ` Disha Goel [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=31368a5a-989a-46ff-a3e2-ec0e7838a7d5@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=shuah@kernel.org \
/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