linux-kernel - Re: per-bdi-throttling: synchronous writepage doesn't work correctly

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:	Thu, 01 Nov 2007 18:39:30 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	jdike@...toit.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: per-bdi-throttling: synchronous writepage doesn't work
	correctly

On Thu, 2007-11-01 at 18:28 +0100, Miklos Szeredi wrote:
> > The page not having PG_writeback set on return is a hint, but not fool
> > proof, it could be the device is just blazing fast.
> 
> Hmm, does it actually has to be foolproof though?  What will happen if
> bdi_writeout_inc() is called twice for the page?  The device will get
> twice the number of pages it deserves?  That's not all that bad,
> especially since that is a really really fast device.

Basically, yes.

But then again, that would require auditing all ->writepage() callsites.



Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)