From: patchwork-bot+linux-ext4@kernel.org
To: linux-ext4@vger.kernel.org
Subject: Patchwork housekeeping for: ext4
Date: Thu, 12 Nov 2026 01:56:51 +0000 [thread overview]
Message-ID: <179444861135.1765492.13721781912592850096.git-patchwork-housekeeping@kernel.org> (raw)
Latest series: [v8] reflink and atomic write bugs (2026-11-12T01:02:29)
Superseding: [v7] reflink and atomic write bugs (2026-11-10T19:04:19):
[v7,01/11] xfs: don't skip the flush before shifting extents
[v7,02/11] xfs: flush the shifted range before changing the file
[v7,03/11] xfs: don't change the block map under a dirty folio
[v7,04/11] iomap: don't punch delalloc under a dirty EOF block
[v7,05/11] fs: validate atomic writes after O_APPEND and limits
[v7,06/11] xfs: recheck direct write alignment after write checks
[v7,07/11] xfs: test for reflink after the dio write checks
[v7,08/11] xfs: refuse writes to files racing with realtime inode flag changes
[v7,09/11] xfs: test for always COW after the dio write checks
[v7,10/11] xfs: refuse fallocate racing with realtime flag changes
[v7,11/11] xfs: restart faults racing with realtime flag changes
Checked 35 series in 2.20 seconds.
This project currently has 365 active patches.
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next reply other threads:[~2026-11-12 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 1:56 patchwork-bot+linux-ext4 [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-10 18:56 Patchwork housekeeping for: ext4 patchwork-bot+linux-ext4
2026-11-10 3:56 patchwork-bot+linux-ext4
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=179444861135.1765492.13721781912592850096.git-patchwork-housekeeping@kernel.org \
--to=patchwork-bot+linux-ext4@kernel.org \
--cc=linux-ext4@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