linux-kernel - Re: [RFC][PATCH] mm: fix page

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 07 Mar 2007 19:24:39 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Nick Piggin <npiggin@...e.de>, Miklos Szeredi <miklos@...redi.hu>,
	akpm@...ux-foundation.org, mingo@...e.hu, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, benh@...nel.crashing.org,
	Jeff Dike <jdike@...toit.com>, hugh <hugh@...itas.com>
Subject: Re: [RFC][PATCH] mm: fix page_mkclean() vs non-linear vmas

On Wed, 2007-03-07 at 19:12 +0100, Peter Zijlstra wrote:
> On Wed, 2007-03-07 at 10:00 -0800, Linus Torvalds wrote:
> > 
> > On Wed, 7 Mar 2007, Peter Zijlstra wrote:
> > > 
> > > I'm not at all happy with this, but plain disallowing remap_file_pages on bdis
> > > without BDI_CAP_NO_WRITEBACK seems to offend some people, hence restrict it to
> > > root only.
> > 
> > I don't think that's a viable approach. Nonlinear mappings would normally 
> > be used by databases, and you don't want to limit databases to be run by 
> > root only.
> 
> It was claimed that they use it on tmpfs only, not on a 'real'
> filesystem.

More specifically, databases want to use direct IO (I know you hate it)
and use the nonlinear vma as buffer area to feed this direct IO

Mapped IO is unsuited for databases in its current form due to the way
IO errors are handled.

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