All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baokun Li <libaokun@linux.alibaba.com>
To: fuse-devel@lists.linux.dev
Cc: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, vgoyal@redhat.com,
	jefflexu@linux.alibaba.com
Subject: [PATCH 0/2] fuse: fix invalidate lock leaks on DAX truncate error paths
Date: Mon, 17 Aug 2026 23:17:59 +0800	[thread overview]
Message-ID: <20260817151801.2677899-1-libaokun@linux.alibaba.com> (raw)

Baokun Li (2):
  fuse: fix invalidate lock leak on setattr writeback failure
  fuse: fix invalidate lock leak on open O_TRUNC DAX failure

 fs/fuse/dir.c  | 9 ++++-----
 fs/fuse/file.c | 4 ++--
 2 files changed, 6 insertions(+), 7 deletions(-)

-- 
2.43.7


             reply	other threads:[~2026-08-17 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 15:17 Baokun Li [this message]
2026-08-17 15:18 ` [PATCH 1/2] fuse: fix invalidate lock leak on setattr writeback failure Baokun Li
2026-08-17 15:18 ` [PATCH 2/2] fuse: fix invalidate lock leak on open O_TRUNC DAX failure Baokun Li

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=20260817151801.2677899-1-libaokun@linux.alibaba.com \
    --to=libaokun@linux.alibaba.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.