[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190312141708.6652-1-vbabka@suse.cz>
Date: Tue, 12 Mar 2019 15:17:06 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Jann Horn <jannh@...gle.com>, Michal Hocko <mhocko@...nel.org>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org, Vlastimil Babka <vbabka@...e.cz>,
Andy Lutomirski <luto@...capital.net>,
Cyril Hrubis <chrubis@...e.cz>, Daniel Gruss <daniel@...ss.cc>,
Dave Chinner <david@...morbit.com>,
Dominique Martinet <asmadeus@...ewreck.org>,
Jiri Kosina <jikos@...nel.org>, Jiri Kosina <jkosina@...e.cz>,
Josh Snyder <joshs@...flix.com>,
Kevin Easton <kevin@...rana.org>,
"Kirill A. Shutemov" <kirill@...temov.name>,
Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...e.com>, Tejun Heo <tj@...nel.org>
Subject: [PATCH v2 0/2] prevent mincore() page cache leaks
Here's a new version of the mincore() patches, with feedback from Andrew Morton
applied. The IOCB_NOWAIT patch was dropped since David Chinner pointed out it's
incomplete. We definitely want the first patch, while for the second Linus
said:
I think that's fine, and probably the right thing to do, but I also
suspect that nobody actually cares ;(
Whether or not somebody cares, we should hear of no breakage. If somebody does
care after all, without second patch we might hear of breakage, so I would
suggest applying it. It's not that complicated after all (famous last words?)
Jiri Kosina (1):
mm/mincore: make mincore() more conservative
Vlastimil Babka (1):
mm/mincore: provide mapped status when cached status is not allowed
mm/mincore.c | 80 ++++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 68 insertions(+), 12 deletions(-)
--
2.20.1
Powered by blists - more mailing lists