public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zilin Guan <zilin@seu.edu.cn>
To: slava@dubeyko.com
Cc: akpm@linux-foundation.org, frank.li@vivo.com,
	glaubitz@physik.fu-berlin.de, jianhao.xu@seu.edu.cn,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	slava.dubeyko@ibm.com, zilin@seu.edu.cn
Subject: [PATCH v3 0/2] hfsplus: fix lock leak and refactor hidden dir search
Date: Fri, 20 Mar 2026 21:04:36 +0800	[thread overview]
Message-ID: <20260320130438.988629-1-zilin@seu.edu.cn> (raw)

This series updates hidden-directory lookup handling in
hfsplus_fill_super().

Patch 1 fixes a B-tree lock leak on an error path in hidden-directory
lookup.

Patch 2 refactors the lookup path into a helper to encapsulate resource
lifetime and simplify error handling.

Changes in v3:
- Use unlikely(err) for hfs_find_init() and hfsplus_cat_build_key() checks.
- Map hfs_brec_read() errors to -ENOENT to preserve existing behavior.

Changes in v2:
- Add patch 2 to extract hidden-directory lookup into a helper function.

Zilin Guan (2):
  hfsplus: fix held lock freed on hfsplus_fill_super()
  hfsplus: extract hidden directory search into a helper function

 fs/hfsplus/super.c | 41 ++++++++++++++++++++++++++++++-----------
 1 file changed, 30 insertions(+), 11 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-03-20 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 13:04 Zilin Guan [this message]
2026-03-20 13:04 ` [PATCH v3 1/2] hfsplus: fix held lock freed on hfsplus_fill_super() Zilin Guan
2026-03-20 13:04 ` [PATCH v3 2/2] hfsplus: extract hidden directory search into a helper function Zilin Guan
2026-03-20 18:40   ` Viacheslav Dubeyko
2026-03-21  7:33     ` Zilin Guan

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=20260320130438.988629-1-zilin@seu.edu.cn \
    --to=zilin@seu.edu.cn \
    --cc=akpm@linux-foundation.org \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jianhao.xu@seu.edu.cn \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slava.dubeyko@ibm.com \
    --cc=slava@dubeyko.com \
    /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