similar to: [V4]fix ocfs2 aio/dio writing process hang

Inlined xattr shared free space of inode block with inlined data or data extent record, so the size of the later two should be adjusted when inlined xattr is enabled. See ocfs2_xattr_ibody_init(). But this isn't done well when reflink. For inode with inlined data, its max inlined data size is adjusted in ocfs2_duplicate_inline_data(), no problem. But for inode with data extent record, its

The patch below does not apply to the 5.10-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable at vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

From: Jan Kara via Ocfs2-devel <ocfs2-devel at oss.oracle.com> commit 90410bcf873cf05f54a32183afff0161f44f9715 upstream. When buffered write fails to copy data into underlying page cache page, ocfs2_write_end_nolock() just zeroes out and dirties the page. This can leave dirty page beyond EOF and if page writeback tries to write this page before write succeeds and expands i_size, page gets

The patch below does not apply to the 4.19-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable at vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

The patch titled Subject: ocfs2: fix use-after-free when unmounting read-only filesystem has been added to the -mm mm-hotfixes-unstable branch. Its filename is ocfs2-fix-use-after-free-when-unmounting-read-only-filesystem.patch This patch will shortly appear at

Hi folks, [I am resending to fix the broken thread in the previous one.] This patchset adds vhost-blk support. vhost-blk is a in kernel virito-blk device accelerator. Compared to userspace virtio-blk implementation, vhost-blk gives about 5% to 15% performance improvement. Asias He (5): aio: Export symbols and struct kiocb_batch for in kernel aio usage eventfd: Export symbol

Hi folks, [I am resending to fix the broken thread in the previous one.] This patchset adds vhost-blk support. vhost-blk is a in kernel virito-blk device accelerator. Compared to userspace virtio-blk implementation, vhost-blk gives about 5% to 15% performance improvement. Asias He (5): aio: Export symbols and struct kiocb_batch for in kernel aio usage eventfd: Export symbol

Hi folks, This patchset adds vhost-blk support. vhost-blk is a in kernel virito-blk device accelerator. Compared to userspace virtio-blk implementation, vhost-blk gives about 5% to 15% performance improvement. Asias He (5): aio: Export symbols and struct kiocb_batch for in kernel aio usage eventfd: Export symbol eventfd_file_create() vhost: Make vhost a separate module vhost-net: Use

Hi folks, This patchset adds vhost-blk support. vhost-blk is a in kernel virito-blk device accelerator. Compared to userspace virtio-blk implementation, vhost-blk gives about 5% to 15% performance improvement. Asias He (5): aio: Export symbols and struct kiocb_batch for in kernel aio usage eventfd: Export symbol eventfd_file_create() vhost: Make vhost a separate module vhost-net: Use

V1->V2: Check to see if our current ppos is >= i_size after a short DIO read, just in case it was actually a short read and we need to just return. This is similar to what already happens in the write case. If we have a short read while doing O_DIRECT, instead of just returning, fallthrough and try to read the rest via buffered IO. BTRFS needs this because if we encounter a compressed or

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-4.14 subdirectory. If

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-4.19 subdirectory. If

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-5.4 subdirectory. If you,

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 5.10-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-5.10 subdirectory. If

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 5.15-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-5.15 subdirectory. If

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 6.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-6.1 subdirectory. If you,

This is a note to let you know that I've just added the patch titled ocfs2: check new file size on fallocate call to the 6.3-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: ocfs2-check-new-file-size-on-fallocate-call.patch and it can be found in the queue-6.3 subdirectory. If you,

The patch titled Subject: ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page has been added to the -mm mm-unstable branch. Its filename is ocfs2-dont-use-write_one_page-in-ocfs2_duplicate_clusters_by_page.patch This patch will shortly appear at

The patch titled Subject: ocfs2: check new file size on fallocate call has been added to the -mm mm-nonmm-unstable branch. Its filename is ocfs2-check-new-file-size-on-fallocate-call.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/ocfs2-check-new-file-size-on-fallocate-call.patch This patch will later appear in

The quilt patch titled Subject: ocfs2: fix non-auto defrag path not working issue has been removed from the -mm tree. Its filename was ocfs2-fix-non-auto-defrag-path-not-working-issue.patch This patch was dropped because it was merged into the mm-hotfixes-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: