linux-kernel - Re: revert "config FS_JOURNAL

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]

Message-ID: <b6fcc0a0912172325i34d214d3r11b3bfae7381547f@mail.gmail.com>
Date:	Fri, 18 Dec 2009 09:25:51 +0200
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: revert "config FS_JOURNAL_INFO"

On 12/18/09, Hiroshi Shimamoto <h-shimamoto@...jp.nec.com> wrote:
> So we never allow to make memory usage small with providing an option
> to remove unused area, right?

We certainly allow this if it results in zero loss in functionality.

> If I want to reduce memory usage by this way, should I keep
> this kind of patches out of tree?

Certainly nobody can prohibit you from keeping patch out of tree.
But if you want something mainlinable, moving ->journal_info
to fs-specific data structures should do the trick. Or something.
--
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/