From: Matthew Wilcox <willy@infradead.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 1/5] Xarray: Do not return sibling entries from xas_find_marked()
Date: Mon, 16 Dec 2024 14:04:50 +0000 [thread overview]
Message-ID: <Z2AzgqT7LCcT-BGr@casper.infradead.org> (raw)
In-Reply-To: <5d89f26a-8ac9-9768-5fc7-af155473f396@huaweicloud.com>
On Mon, Dec 16, 2024 at 03:05:26PM +0800, Kemeng Shi wrote:
> Ahhh, right. Thank you for correcting me. Then I would like to use nfs as low-level
> filesystem in example and the potential crash could be triggered in the same steps.
Have you actually seen this crash, or do you just think it can happen?
next prev parent reply other threads:[~2024-12-16 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 12:25 [PATCH v3 0/5] Fixes and cleanups to xarray Kemeng Shi
2024-12-13 12:25 ` [PATCH v3 1/5] Xarray: Do not return sibling entries from xas_find_marked() Kemeng Shi
2024-12-13 6:12 ` Baolin Wang
2024-12-16 7:05 ` Kemeng Shi
2024-12-16 14:04 ` Matthew Wilcox [this message]
2024-12-17 0:59 ` Kemeng Shi
2024-12-13 12:25 ` [PATCH v3 2/5] Xarray: move forward index correctly in xas_pause() Kemeng Shi
2024-12-13 12:25 ` [PATCH v3 3/5] Xarray: distinguish large entries correctly in xas_split_alloc() Kemeng Shi
2024-12-13 12:25 ` [PATCH v3 4/5] Xarray: remove repeat check in xas_squash_marks() Kemeng Shi
2024-12-13 12:25 ` [PATCH v3 5/5] Xarray: use xa_mark_t in xas_squash_marks() to keep code consistent Kemeng Shi
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=Z2AzgqT7LCcT-BGr@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=shikemeng@huaweicloud.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