Linux filesystem development
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Kara <jack@suse.com>,
	linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>
Subject: [git pull] old udf fix
Date: Mon, 15 Jun 2026 03:36:21 +0100	[thread overview]
Message-ID: <20260615023621.GA2142293@ZenIV> (raw)
In-Reply-To: <n7blo2z6tk25p2pkjk53ifm2p2nejodngojrnmgdcr2bqpv3m4@up4qbcufnfii>

[just noticed that udf fix had been sitting in #fixes since February;
still applicable, Jan's Acked-by applied, very belated pull request
follows]

The following changes since commit 2005aabe94eaab8608879d98afb901bc99bc3a31:

  functionfs: use spinlock for FFS_DEACTIVATED/FFS_CLOSING transitions (2026-02-05 13:53:12 -0500)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

for you to fetch changes up to 462bdd08fbdf41db223c6117d907c8fd68d666ea:

  udf: fix nls leak on udf_fill_super() failure (2026-06-14 22:29:21 -0400)

----------------------------------------------------------------
old udf fix that had fallen through the cracks...

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (1):
      udf: fix nls leak on udf_fill_super() failure

 fs/udf/super.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

  reply	other threads:[~2026-06-15  2:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 20:18 [PATCH] udf: fix nls leak on udf_fill_super() failure Al Viro
2026-02-12  9:59 ` Jan Kara
2026-06-15  2:36   ` Al Viro [this message]
2026-06-15 10:27     ` [git pull] old udf fix pr-tracker-bot

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=20260615023621.GA2142293@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=jack@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=torvalds@linux-foundation.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