lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241006152849.247152-1-yizhou.tang@shopee.com>
Date: Sun,  6 Oct 2024 23:28:46 +0800
From: Tang Yizhou <yizhou.tang@...pee.com>
To: jack@...e.cz,
	hch@...radead.org,
	willy@...radead.org,
	akpm@...ux-foundation.org,
	chandan.babu@...cle.com
Cc: linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org,
	linux-xfs@...r.kernel.org,
	Tang Yizhou <yizhou.tang@...pee.com>
Subject: [PATCH v2 0/3] Cleanup some writeback codes

From: Tang Yizhou <yizhou.tang@...pee.com>

v2:
PATCH #1: Rename BANDWIDTH_INTERVAL to BW_DIRTYLIMIT_INTERVAL and update
some comments.

PATCH #2: Pick up Jan's Reviewed-by tag.

PATCH #3: xfs_max_map_length() was written following the logic of
writeback_chunk_size().


Tang Yizhou (3):
  mm/page-writeback.c: Rename BANDWIDTH_INTERVAL to
    BW_DIRTYLIMIT_INTERVAL
  mm/page-writeback.c: Fix comment of wb_domain_writeout_add()
  xfs: Let the max iomap length be consistent with the writeback code

 fs/fs-writeback.c         |  5 ----
 fs/xfs/xfs_iomap.c        | 52 ++++++++++++++++++++++++---------------
 include/linux/writeback.h |  5 ++++
 mm/page-writeback.c       | 18 +++++++-------
 4 files changed, 46 insertions(+), 34 deletions(-)

-- 
2.25.1


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ