public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] fsverity: add missing fsverity_free_info()
Date: Tue, 3 Feb 2026 19:33:29 -0800	[thread overview]
Message-ID: <20260204033329.GA3726@sol> (raw)
In-Reply-To: <20260203053228.GB15956@lst.de>

On Tue, Feb 03, 2026 at 06:32:28AM +0100, Christoph Hellwig wrote:
> On Mon, Feb 02, 2026 at 01:43:06PM -0800, Eric Biggers wrote:
> > If fsverity_set_info() fails, we need to call fsverity_free_info().
> > 
> > Fixes: ada3a1a48d5a ("fsverity: use a hashtable to find the fsverity_info")
> > Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> 
> Looks good.  It might make sense to fold into the offending patch to help
> with bisectability, though.
> 

I folded it into "fsverity: use a hashtable to find the fsverity_info".

- Eric

      reply	other threads:[~2026-02-04  3:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 21:43 [PATCH] fsverity: add missing fsverity_free_info() Eric Biggers
2026-02-03  5:32 ` Christoph Hellwig
2026-02-04  3:33   ` Eric Biggers [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=20260204033329.GA3726@sol \
    --to=ebiggers@kernel.org \
    --cc=fsverity@lists.linux.dev \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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