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: <1409815781-28011-1-git-send-email-gioh.kim@lge.com>
Date:	Thu,  4 Sep 2014 16:29:38 +0900
From:	Gioh Kim <gioh.kim@....com>
To:	gioh.kim@....com, akpm@...ux-foundation.org, jack@...e.cz,
	tytso@....edu, linux-fsdevel@...r.kernel.org,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	viro@...iv.linux.org.uk, paulmck@...ux.vnet.ibm.com,
	peterz@...radead.org, adilger.kernel@...ger.ca
Cc:	minchan@...nel.org, js1304@...il.com, gunho.lee@....com
Subject: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

Hello,

This patch try to solve problem that a long-lasting page caches of
ext4 superblock and journaling of superblock disturb page migration.

I've been testing CMA feature on my ARM-based platform
and found that two page caches cannot be migrated.
They are page caches of superblock of ext4 filesystem and its journaling data.

Current ext4 reads superblock with sb_bread() that allocates page
from movable area. But the problem is that ext4 hold the page until
it is unmounted. If root filesystem is ext4 the page cannot be migrated
forever.
And also the journaling data for the superblock cannot be migreated.

I introduce new APIs that allocates page cache with specific flag passed by an
argument.
*_gfp APIs are for user want to set page allocation flag for page cache
allocation.
And *_unmovable APIs are for the user wants to allocate page cache from
non-movable area.

It is useful for ext4/ext3 and others that want to hold page cache for a long
time.

I have 3 patchs:

1. Patch 1/3: introduce a new API that create page cache with allocation flag
2. Patch 2/3: have ext4 use the new API to read superblock
3. Patch 3/3: have jbd/jbd2 use the new API to make journaling of superblock

This patchset is based on linux-next-20140814.

Thanks a lot.

Gioh Kim (3):
  fs.c: support buffer cache allocations with gfp modifiers
  ext4: use non-movable memory for the ext4 superblock
  jbd/jbd2: use non-movable memory for the jbd superblock

 fs/buffer.c                 |   45 ++++++++++++++++++++++++-----------------
 fs/ext4/super.c             |    6 +++---
 fs/jbd/journal.c            |    2 +-
 fs/jbd2/journal.c           |    2 +-
 include/linux/buffer_head.h |   47 ++++++++++++++++++++++++++++++++++++++-----
 5 files changed, 73 insertions(+), 29 deletions(-)

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ