FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: "Luís Henriques" <lhenriques@suse.de>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v3] common/rc: cleanup old .kmemleak files
Date: Thu, 13 Jul 2023 07:04:53 -0700	[thread overview]
Message-ID: <20230713140453.GI11442@frogsfrogsfrogs> (raw)
In-Reply-To: <20230713082631.10666-1-lhenriques@suse.de>

On Thu, Jul 13, 2023 at 09:26:31AM +0100, Luís Henriques wrote:
> I've spent a non-negligible amount of time looking into a kmemleak that
> didn't exist in the code I was testing because there was an old .kmemleak
> file in the results directory.  I don't think this is an intended behaviour,
> so I'm proposing to remove these files everytime we capture the result of a
> new scan.
> 
> Signed-off-by: Luís Henriques <lhenriques@suse.de>

Looks good now,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  common/rc | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> Changes since v2:
> Incorporated comment from Darrick to explain the usage of '-f' in the test
> 
> Changes since v1:
> I realised that _capture_kmemleak() is called with /dev/null as argument, so
> this version is probably better.
> 
> diff --git a/common/rc b/common/rc
> index 741579af82d2..5c4429ed0425 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -4433,6 +4433,10 @@ _capture_kmemleak()
>  	local kern_knob="$DEBUGFS_MNT/kmemleak"
>  	local leak_file="$1"
>  
> +	# Some callers pass in /dev/null when they want to clear the
> +	# kernel's leak report file and do not care what was in that.
> +	[ -f "$leak_file" ] && rm -f "$leak_file"
> +
>  	# Tell the kernel to scan for memory leaks.  Apparently the write
>  	# returns before the scan is complete, so do it twice in the hopes
>  	# that twice is enough to capture all the leaks.

      reply	other threads:[~2023-07-13 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  8:26 [PATCH v3] common/rc: cleanup old .kmemleak files Luís Henriques
2023-07-13 14:04 ` Darrick J. Wong [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=20230713140453.GI11442@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=lhenriques@suse.de \
    /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