All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 219504] XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 for XFS/iomap causing the problems?
Date: Thu, 28 Nov 2024 21:09:27 +0000	[thread overview]
Message-ID: <bug-219504-201763-DK3k4WyihR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219504-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219504

--- Comment #2 from Mike-SPC (speedcracker@hotmail.com) ---
Hello Long Li,

thanks for investigation.
It seems, that the patch went into the kernel 6.1.113:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e3aa99b13a99405d935910306d1bbf419edfd679

It looks like this:

--- snip ---

diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
index 98617f00101d68..1833608f39318e 100644
--- a/fs/iomap/buffered-io.c
+++ b/fs/iomap/buffered-io.c
@@ -990,7 +990,15 @@ static int iomap_write_delalloc_release(struct inode
*inode,
                        error = data_end;
                        goto out_unlock;
                }
-               WARN_ON_ONCE(data_end <= start_byte);
+
+               /*
+                * If we race with post-direct I/O invalidation of the page
cache,
+                * there might be no data left at start_byte.
+                */
+               if (data_end == start_byte)
+                       continue;
+
+               WARN_ON_ONCE(data_end < start_byte);
                WARN_ON_ONCE(data_end > scan_end_byte);

                error = iomap_write_delalloc_scan(inode, &punch_start_byte,

--- snap ---

Looks like your's:

https://patchwork.kernel.org/project/xfs/patch/20231216115559.3823359-1-leo.lilong@huawei.com/

Due to lack of time, I haven't gotten around to testing the latest kernel with
this patch in it.

Regards,
Mike

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-11-28 21:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17 13:42 [Bug 219504] New: XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 for XFS/iomap causing the problems? bugzilla-daemon
2024-11-21 11:49 ` [Bug 219504] " bugzilla-daemon
2024-11-28 21:09 ` bugzilla-daemon [this message]
2024-12-19 13:58 ` bugzilla-daemon
2024-12-19 17:02 ` [Bug 219504] XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 (and up) " bugzilla-daemon
2024-12-30 21:26 ` [Bug 219504] New: XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 " Marco Nelissen
2024-12-30 21:26 ` [Bug 219504] iomap/buffered-io/XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 (and up) " bugzilla-daemon
2024-12-31 22:11 ` [Bug 219504] New: XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 " Marco Nelissen
2024-12-31 22:11 ` [Bug 219504] iomap/buffered-io/XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 (and up) " bugzilla-daemon
2025-01-18 14:00 ` bugzilla-daemon
2025-01-18 23:51   ` Marco Nelissen
2025-01-18 23:51 ` bugzilla-daemon
2025-01-28 20:00 ` bugzilla-daemon
2025-02-03 10:03 ` bugzilla-daemon

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=bug-219504-201763-DK3k4WyihR@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.