From: sashiko-bot@kernel.org
To: "Gabriele Monaco" <gmonaco@redhat.com>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] verification/rvgen: Use .old instead of .bak for kunit backup files
Date: Mon, 24 Aug 2026 08:28:00 +0000 [thread overview]
Message-ID: <20260824082801.1D8011F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260824081519.81103-2-gmonaco@redhat.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `rvgen kunit` tool generates `.old` backup files which are not cleaned up by `make distclean`, polluting the user's working directory.
--
--- Patch [1]: [PATCH] verification/rvgen: Use .old instead of .bak for kunit backup files ---
commit 293b444e4dfea5692931faee1bc9c58a549085d8
Author: Gabriele Monaco <gmonaco@redhat.com>
verification/rvgen: Use .old instead of .bak for kunit backup files
The rvgen kunit command generates .bak backup files and these can be
checked in for selftests (make check). Clean targets like make disclean
remove such files, leaving the tree dirty. Switch to .old to preserve a
clean tree after make disclean.
Closes: https://lore.kernel.org/lkml/aosuwKH5GOEo0xTN@google.com
> diff --git a/tools/verification/rvgen/rvgen/kunit.py b/tools/verification/rvgen/rvgen/kunit.py
> index ed2082d7d3bc4..85973f918c9b5 100644
> --- a/tools/verification/rvgen/rvgen/kunit.py
> +++ b/tools/verification/rvgen/rvgen/kunit.py
[ ... ]
> @@ -173,7 +173,7 @@ EXPORT_SYMBOL_IF_KUNIT({struct_name});
> for path in (header_file_path, kunit_c_file_path):
> if path.exists():
> try:
> - path.rename(path.with_suffix(path.suffix + ".bak"))
> + path.rename(path.with_suffix(path.suffix + ".old"))
[Severity: Medium]
Will this regression leave users' working directories polluted with .old
backup files that aren't cleaned up by the top-level make distclean target?
The kernel's global Makefile explicitly cleans *.bak files during
distclean, but ignores *.old files.
When a user runs rvgen kunit in a directory with existing kunit files and
accepts the backup prompt, print_files() will generate these .old files.
Since they are no longer .bak files, is it expected that they will persist
after running make distclean?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260824081519.81103-2-gmonaco@redhat.com?part=1
next prev parent reply other threads:[~2026-08-24 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 8:15 [PATCH] verification/rvgen: Use .old instead of .bak for kunit backup files Gabriele Monaco
2026-08-24 8:28 ` sashiko-bot [this message]
2026-08-24 15:33 ` Kuan-Wei Chiu
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=20260824082801.1D8011F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=gmonaco@redhat.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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