Displaying 20 results from an estimated 100 matches similar to: "remove most callers of write_one_page v4"
2023 Jan 18
9
remove most callers of write_one_page v3
Hi all,
this series removes most users of the write_one_page API. These helpers
internally call ->writepage which we are gradually removing from the
kernel.
Changes since v2:
- more minix error handling fixes
Changes since v1:
- drop the btrfs changes (queue up in the btrfs tree)
- drop the finaly move to jfs (can't be done without the btrfs patches)
- fix the existing minix code to
2023 Mar 07
0
+ ufs-dont-flush-page-immediately-for-dirsync-directories.patch added to mm-unstable branch
The patch titled
Subject: ufs: don't flush page immediately for DIRSYNC directories
has been added to the -mm mm-unstable branch. Its filename is
ufs-dont-flush-page-immediately-for-dirsync-directories.patch
This patch will shortly appear at
2023 Mar 30
4
[PATCH v2] mm: Take a page reference when removing device exclusive entries
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
2023 Mar 07
1
[PATCH 2/3] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page
Use filemap_write_and_wait_range to write back the range of the dirty
page instead of write_one_page in preparation of removing write_one_page
and eventually ->writepage.
Signed-off-by: Christoph Hellwig <hch at lst.de>
Reviewed-by: Jan Kara <jack at suse.cz>
Reviewed-by: Joseph Qi <joseph.qi at linux.alibaba.com>
---
fs/ocfs2/refcounttree.c | 9 +++++----
1 file changed, 5
2023 Jun 18
11
[PATCH v1 0/5] clean up block_commit_write
*** 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 +++++++-----------------
2023 Mar 28
3
[PATCH] mm: Take a page reference when removing device exclusive entries
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
2023 Mar 30
1
[PATCH] mm: Take a page reference when removing device exclusive entries
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
2023 Mar 07
0
+ ocfs2-dont-use-write_one_page-in-ocfs2_duplicate_clusters_by_page.patch added to mm-unstable branch
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
2023 Jan 18
1
remove most callers of write_one_page v3
On Wed, Jan 18, 2023 at 06:30:20PM +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series removes most users of the write_one_page API. These helpers
> internally call ->writepage which we are gradually removing from the
> kernel.
>
> Changes since v2:
> - more minix error handling fixes
>
> Changes since v1:
> - drop the btrfs changes (queue up in the
2023 Mar 29
1
[PATCH] mm: Take a page reference when removing device exclusive entries
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
ohh, and I really should have caught that too. I plead spending too much
time recently in a somewhat more driver-centric
2023 Mar 09
5
[PATCH v2 1/5] fs: add i_blockmask()
The message from this sender included one or more files
which could not be scanned for virus detection; do not
open these files unless you are certain of the sender's intent.
----------------------------------------------------------------------
Introduce i_blockmask() to simplify code, which replace
(i_blocksize(node) - 1). Like done in commit
93407472a21b("fs: add i_blocksize()").
2023 Mar 10
5
[PATCH v4 1/5] fs: add i_blockmask()
Introduce i_blockmask() to simplify code, which replace
(i_blocksize(node) - 1). Like done in commit
93407472a21b("fs: add i_blocksize()").
Signed-off-by: Yangtao Li <frank.li at vivo.com>
---
v4:
-drop ext4 patch
-erofs patch based on mainline
-a bit change in ocfs2 patch
include/linux/fs.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/fs.h
2023 Mar 29
1
[PATCH] mm: Take a page reference when removing device exclusive entries
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
2015 Jul 10
2
HP Elitebook 8460p
Hi, all.
I'm intending to install CentOS 7 on a HP Elitebook 8460p. Does anybody
have any experience of this?
Many thanks for any help.
Cheers,
Phil...
2023 Mar 09
8
[PATCH v3 1/6] fs: add i_blockmask()
Introduce i_blockmask() to simplify code, which replace
(i_blocksize(node) - 1). Like done in commit
93407472a21b("fs: add i_blocksize()").
Signed-off-by: Yangtao Li <frank.li at vivo.com>
---
v3:
-none
v2:
-convert to i_blockmask()
include/linux/fs.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index c85916e9f7db..17387d465b8b
2023 Mar 10
1
[PATCH 1/3] ufs: don't flush page immediately for DIRSYNC directories
On Tue, Mar 07, 2023 at 03:31:23PM +0100, Christoph Hellwig wrote:
> We do not need to writeout modified directory blocks immediately when
> modifying them while the page is locked. It is enough to do the flush
> somewhat later which has the added benefit that inode times can be
> flushed as well. It also allows us to stop depending on
> write_one_page() function.
>
> Ported
2023 Mar 10
1
[PATCH 1/3] ufs: don't flush page immediately for DIRSYNC directories
On Fri, Mar 10, 2023 at 03:53:53AM +0000, Al Viro wrote:
> On Tue, Mar 07, 2023 at 03:31:23PM +0100, Christoph Hellwig wrote:
> > We do not need to writeout modified directory blocks immediately when
> > modifying them while the page is locked. It is enough to do the flush
> > somewhat later which has the added benefit that inode times can be
> > flushed as well. It also
2023 Jun 19
9
[PATCH v2 0/5] clean up block_commit_write
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
2011 Jan 31
2
Protocol stream error on extended attribute, silent failure to copy all attributes
I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike
Bombich's instructions at http://www.bombich.com/rsync.html. Rsync
repeatedly exits with a protocol data stream error when trying to copy
some com.apple.FinderInfo extended attributes. While testing this issue,
I found that rsync is not actually copying all extended attributes even
when there is no error message. I'm
2008 Jul 24
4
umount oops
Hi,
I tried very promising btrfs to test it a little and I experienced a
little bug in implementation. I''m not sure where the bug lies however
this works quite well to reproduce the problem:
dd if=/dev/zero of=mountme bs=4k count=100000
dd if=/dev/zero of=mountme2 bs=4k count=100000
mkfs.btrfs mountme
mkfs.btrfs mountme2
mkdir loop loop2
mount -o loop mountme loop
mount -o loop mountme