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
| ||
|
Message-Id: <20170106141107.23953-1-mhocko@kernel.org> Date: Fri, 6 Jan 2017 15:10:59 +0100 From: Michal Hocko <mhocko@...nel.org> To: <linux-mm@...ck.org>, <linux-fsdevel@...r.kernel.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Dave Chinner <david@...morbit.com>, djwong@...nel.org, "Theodore Ts'o" <tytso@....edu>, Chris Mason <clm@...com>, David Sterba <dsterba@...e.cz>, Jan Kara <jack@...e.cz>, ceph-devel@...r.kernel.org, cluster-devel@...hat.com, linux-nfs@...r.kernel.org, logfs@...fs.org, linux-xfs@...r.kernel.org, linux-ext4@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-mtd@...ts.infradead.org, reiserfs-devel@...r.kernel.org, linux-ntfs-dev@...ts.sourceforge.net, linux-f2fs-devel@...ts.sourceforge.net, linux-afs@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>, Brian Foster <bfoster@...hat.com>, Michal Hocko <mhocko@...e.com>, "Peter Zijlstra (Intel)" <peterz@...radead.org> Subject: [PATCH 0/8 v3] scope GFP_NOFS api Hi, I have posted the previous version here [1]. Since then I've added some reviewed bys and fixed some minor issues. I've dropped patch 2 [2] based on Dave's request [3]. I agree that this can be done later and doing all at once. I still think that __GFP_NOLOCKDEP should be added by this series to make the further development easier. There didn't seem to be any real objections and so I think we should go and merge this and build further on top. I would like to get rid of all explicit GFP_NOFS usage in ext4 code. I have something half baked already and will send it later on. I also hope we can get further with the xfs as well. I haven't heard anything from btrfs or other filesystems guys which is a bit unfortunate but I do not want to wait for them to much longer, they can join the effort later on. The patchset is based on next-20170106 Diffstat says fs/ext4/acl.c | 6 +++--- fs/ext4/extents.c | 8 ++++---- fs/ext4/resize.c | 4 ++-- fs/ext4/xattr.c | 4 ++-- fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 10 +++++----- fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 8 +++++--- mm/vmscan.c | 6 +++--- 19 files changed, 109 insertions(+), 45 deletions(-) Shortlog: Michal Hocko (8): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe Revert "ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp" Revert "ext4: fix wrong gfp type under transaction" [1] http://lkml.kernel.org/r/20161215140715.12732-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20161215140715.12732-3-mhocko@kernel.org [3] http://lkml.kernel.org/r/20161219212413.GN4326@dastard -- 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