linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christian Brauner <brauner@kernel.org>,
	yukuai3@huawei.com, yangerkun@huaweicloud.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	Hugh Dickens <hughd@google.com>
Subject: Re: [RFC PATCH 0/2] Improve simple directory offset wrap behavior
Date: Wed, 20 Nov 2024 10:01:37 +0100	[thread overview]
Message-ID: <20241120-jurymitglied-randnotiz-b382d61369dc@brauner> (raw)
In-Reply-To: <20241117213206.1636438-1-cel@kernel.org>

On Sun, 17 Nov 2024 16:32:04 -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> This series attempts to narrow some gaps in the current tmpfs
> directory offset mechanism, based on misbehaviors reported by Yu
> Kuai <yukuai3@huawei.com> and Yang Erkun <yangerkun@huawei.com>.
> 
> It does not fully close the window on bad behavior, as noted in
> the patch description of 2/2. Perhaps discussion and review can
> identify improvements that further clean up the corner cases.
> 
> [...]

Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes

[1/2] libfs: Return ENOSPC when the directory offset range is exhausted
      https://git.kernel.org/vfs/vfs/c/7f82c425d13b
[2/2] libfs: Improve behavior when directory offset values wrap
      https://git.kernel.org/vfs/vfs/c/3e8dd5a7404a


      parent reply	other threads:[~2024-11-20  9:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17 21:32 cel
2024-11-17 21:32 ` [RFC PATCH 1/2] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-11-18 19:55   ` Jeff Layton
2024-11-17 21:32 ` [RFC PATCH 2/2] libfs: Improve behavior when directory offset values wrap cel
2024-11-18 20:00   ` Jeff Layton
2024-11-18 20:58     ` Chuck Lever
2024-11-20  8:59       ` Christian Brauner
2024-11-20 15:05         ` Chuck Lever
2024-11-21  8:34           ` Christian Brauner
2024-11-21 14:54             ` Chuck Lever III
2024-11-21 21:18               ` Hugh Dickins
2024-11-21 21:29                 ` Chuck Lever
2024-11-22  8:49                   ` Amir Goldstein
2024-11-22 14:24                     ` Chuck Lever III
2024-12-04 21:05                     ` Chuck Lever
2024-11-22 12:57               ` Christian Brauner
2024-11-24 21:28                 ` Chuck Lever III
2024-11-20  9:01 ` Christian Brauner [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=20241120-jurymitglied-randnotiz-b382d61369dc@brauner \
    --to=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=hughd@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yangerkun@huaweicloud.com \
    --cc=yukuai3@huawei.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