From: Brian Foster <bfoster@redhat.com>
To: linux-bcachefs@vger.kernel.org
Subject: [PATCH v4 1/4] bcachefs: drop duplicate fiemap sync flag
Date: Fri, 19 Apr 2024 14:15:35 -0400 [thread overview]
Message-ID: <20240419181538.1411082-2-bfoster@redhat.com> (raw)
In-Reply-To: <20240419181538.1411082-1-bfoster@redhat.com>
FIEMAP_FLAG_SYNC handling was deliberately moved into core code in
commit 45dd052e67ad ("fs: handle FIEMAP_FLAG_SYNC in fiemap_prep"),
released in kernel v5.8. Update bcachefs accordingly.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
fs/bcachefs/fs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/bcachefs/fs.c b/fs/bcachefs/fs.c
index de307e2323bb..f6cd14c9b38c 100644
--- a/fs/bcachefs/fs.c
+++ b/fs/bcachefs/fs.c
@@ -963,7 +963,7 @@ static int bch2_fiemap(struct inode *vinode, struct fiemap_extent_info *info,
u32 snapshot;
int ret = 0;
- ret = fiemap_prep(&ei->v, info, start, &len, FIEMAP_FLAG_SYNC);
+ ret = fiemap_prep(&ei->v, info, start, &len, 0);
if (ret)
return ret;
--
2.44.0
next prev parent reply other threads:[~2024-04-19 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 18:15 [PATCH v4 0/4] bcachefs: fiemap delalloc support and cleanup Brian Foster
2024-04-19 18:15 ` Brian Foster [this message]
2024-04-19 18:15 ` [PATCH v4 2/4] bcachefs: track current fiemap offset in start variable Brian Foster
2024-04-19 18:15 ` [PATCH v4 3/4] bcachefs: refactor fiemap processing into extent helper and struct Brian Foster
2024-04-19 18:15 ` [PATCH v4 4/4] bcachefs: add fiemap delalloc extent detection Brian Foster
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=20240419181538.1411082-2-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=linux-bcachefs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).