All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Bin <yebin10@huawei.com>
To: <djwong@kernel.org>, <linux-xfs@vger.kernel.org>,
	<chandan.babu@oracle.com>, <dchinner@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <yebin10@huawei.com>
Subject: [PATCH RFC 0/2] xfs: fix potential create file failed
Date: Fri, 19 Apr 2024 14:18:46 +0800	[thread overview]
Message-ID: <20240419061848.1032366-1-yebin10@huawei.com> (raw)

This patch set fixes two potential issues that could cause failure to
create files.

Ye Bin (2):
  xfs: fix potential create file failed
  xfs: avoid potenial alloc inode failed

 fs/xfs/libxfs/xfs_alloc.c  | 32 ++++++++++----------------------
 fs/xfs/libxfs/xfs_ialloc.c | 13 ++-----------
 2 files changed, 12 insertions(+), 33 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-04-19  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  6:18 Ye Bin [this message]
2024-04-19  6:18 ` [PATCH RFC 1/2] xfs: fix potential create file failed Ye Bin
2024-04-21 23:24   ` Dave Chinner
2024-04-19  6:18 ` [PATCH RFC 2/2] xfs: avoid potenial alloc inode failed Ye Bin

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=20240419061848.1032366-1-yebin10@huawei.com \
    --to=yebin10@huawei.com \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.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 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.