linux-ext4 - Re: ext3 leaking buffer

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

Message-ID: <49C9D779.4030805@cs.utexas.edu>
Date:	Wed, 25 Mar 2009 02:04:25 -0500
From:	Don Porter <porterde@...utexas.edu>
To:	Theodore Tso <tytso@....edu>
CC:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: ext3 leaking buffer_heads

Theodore Tso wrote:
> The journal is a fixed sized, circular log, so the buffer_head will be
> reused eventually.  In the case of memory pressure the unreferenced
> buffer_head will be freed, but since we never reference the contents
> of the journal, we could be more aggressive about freeing the
> buffer_head just to avoid pushing out more valuable memory contents
> when we start getting put under memory pressure.
>
> 					- Ted
>   

Thanks Ted.  This makes sense.

I am working on a research project that may require more aggressive 
reclaiming of these buffer_heads.  If I were to implement something, 
would this be an optimization the maintainers would be interested in?

Thanks again for the help,

Don
--
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