similar to: + fs-convert-block_commit_write-to-return-void.patch added to mm-unstable branch

The patch titled Subject: fs/buffer: clean up block_commit_write has been added to the -mm mm-unstable branch. Its filename is fs-buffer-clean-up-block_commit_write.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fs-buffer-clean-up-block_commit_write.patch This patch will later appear in the mm-unstable branch

On Sun 18-06-23 23:32:48, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(). > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me. Feel free to add: Reviewed-by: Jan Kara <jack at suse.cz> Honza > --- > fs/ext4/move_extent.c | 7 ++----- > 1 file

On Sun 18-06-23 23:32:46, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Originally inode is used to get blksize, after commit 45bce8f3e343 > ("fs/buffer.c: make block-size be per-page and protected by the page lock"), > __block_commit_write no longer uses this parameter inode, this patch is to > remove inode and clean up block_commit_write. >

On Sun 18-06-23 23:32:47, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > block_commit_write() always returns 0, this patch changes it to > return void. > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me but you'll need to reorder this patch at the end of the patch series to avoid breaking compilation in the middle of the series.

Changelog: v1--v2: 1. Re-order patches to avoid breaking compilation. Bean Huo (5): fs/buffer: clean up block_commit_write ext4: No need to check return value of block_commit_write() fs/ocfs2: No need to check return value of block_commit_write() udf: No need to check return value of block_commit_write() fs/buffer.c: convert block_commit_write to return void fs/buffer.c

*** BLURB HERE *** Bean Huo (5): fs/buffer: clean up block_commit_write fs/buffer.c: convert block_commit_write to return void ext4: No need to check return value of block_commit_write() fs/ocfs2: No need to check return value of block_commit_write() udf: No need to check return value of block_commit_write() fs/buffer.c | 24 +++++++-----------------

On Sun 18-06-23 23:32:49, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(). > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me. Feel free to add: Reviewed-by: Jan Kara <jack at suse.cz> Honza > --- > fs/ocfs2/file.c | 7 +------ > 1 file

The patch titled Subject: fs-buffer-clean-up-block_commit_write-fix has been added to the -mm mm-unstable branch. Its filename is fs-buffer-clean-up-block_commit_write-fix.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fs-buffer-clean-up-block_commit_write-fix.patch This patch will later appear in the

On Sun 18-06-23 23:32:50, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(). > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me. Feel free to add: Reviewed-by: Jan Kara <jack at suse.cz> Honza > --- > fs/udf/file.c | 6 +++--- > 1 file changed,

On Mon, Jun 19, 2023 at 11:18:24PM +0200, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(), > because it always returns 0. > > Signed-off-by: Bean Huo <beanhuo at micron.com> > Reviewed-by: Jan Kara <jack at suse.cz> Acked-by: Theodore Ts'o <tytso at mit.edu>

On Thu, Jul 07, 2022 at 07:50:17PM -0700, Hugh Dickins wrote: > On Wed, 8 Jun 2022, Matthew Wilcox (Oracle) wrote: > > > Now that both callers have a folio, convert this function to > > take a folio & rename it. > > > > Signed-off-by: Matthew Wilcox (Oracle) <willy at infradead.org> > > Reviewed-by: Christoph Hellwig <hch at lst.de> > >

On Thu, Jul 07, 2022 at 07:50:17PM -0700, Hugh Dickins wrote: > On Wed, 8 Jun 2022, Matthew Wilcox (Oracle) wrote: > > > Now that both callers have a folio, convert this function to > > take a folio & rename it. > > > > Signed-off-by: Matthew Wilcox (Oracle) <willy at infradead.org> > > Reviewed-by: Christoph Hellwig <hch at lst.de> > >

Device exclusive page table entries are used to prevent CPU access to a page whilst it is being accessed from a device. Typically this is used to implement atomic operations when the underlying bus does not support atomic access. When a CPU thread encounters a device exclusive entry it locks the page and restores the original entry after calling mmu notifiers to signal drivers that exclusive

I''m going to be removing hole extents in the near future so I wanted to make a sanity test for btrfs_get_extent to make sure I don''t break anything in the meantime. This patch just puts btrfs_get_extent through its paces by giving it a completely unreasonable mapping to look at and make sure it is giving us back maps that make sense. Thanks, Signed-off-by: Josef Bacik

On Tue, Mar 28, 2023 at 01:14:34PM +1100, Alistair Popple wrote: > +++ b/mm/memory.c > @@ -3623,8 +3623,19 @@ static vm_fault_t remove_device_exclusive_entry(struct vm_fault *vmf) > struct vm_area_struct *vma = vmf->vma; > struct mmu_notifier_range range; > > - if (!folio_lock_or_retry(folio, vma->vm_mm, vmf->flags)) > + /* > + * We need a page reference to

Hi, I'm having problem with generating ppc64-assembler code. First I create ppc64-assembler with llc: llc -march=ppc64 gzip.bc -f -o gzip.s Then I try to compile this with a cross-compiler on x86_64-linux to ppc64-linux: .../crosstools/gcc-4.2.4-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/powerpc64-unknown-linux-gnu-gcc gzip.s But the compiler gives me gzip.4.s: Assembler messages:

John Hubbard <jhubbard at nvidia.com> writes: > On 3/28/23 20:16, Matthew Wilcox wrote: > ... >>> + if (!get_page_unless_zero(vmf->page)) >>> + return 0; >> From a folio point of view: what the hell are you doing here? Tail >> pages don't have individual refcounts; all the refcounts are actually I had stuck with using the page because none of

Hi All I have a series of images that I''m showing in a table inside a <div> with overflow:auto on. Each of the images is a dragable. In firefox this works as expected (if the image list is longer than the div scroll bars appear to scroll the div and scrolling works). However in IE the images are shown outside the containing div and the scroll bar does nothing I think this is

I added an assert to make sure we were looking up aligned offsets for csums and I tripped it when running xfstests. This is because log_one_extent was checking if block_start == 0 for a hole instead of EXTENT_MAP_HOLE. This worked out fine in practice it seems, but it adds a lot of extra work that is uneeded. With this fix I''m no longer tripping my assert. Thanks, Signed-off-by:

Device exclusive page table entries are used to prevent CPU access to a page whilst it is being accessed from a device. Typically this is used to implement atomic operations when the underlying bus does not support atomic access. When a CPU thread encounters a device exclusive entry it locks the page and restores the original entry after calling mmu notifiers to signal drivers that exclusive