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: <4B2AFF4C.5010100@ct.jp.nec.com>
Date:	Fri, 18 Dec 2009 13:04:28 +0900
From:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
To:	Alexey Dobriyan <adobriyan@...il.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"

Alexey Dobriyan wrote:
> Can we please revert commit e4c570c4cb7a95dbfafa3d016d2739bf3fdfe319
> "task_struct: make journal_info conditional"

I'm fine to revert it, because it seems merged accidentally.

> 
> I think I gave a good enough arguments to not merge it.
> To iterate:
> * patch makes impossible to start using ext3 on EXT3_FS=n kernels
> without reboot.
> * this is done only for one pointer on task_struct

I don't think it's only one pointer.
There might be a lot of "only one pointer".

> 
> None of config options which define task_struct are tristate directly
> or effectively.

So we never allow to make memory usage small with providing an option
to remove unused area, right? Of cause, that option should be handled
carefully. If I want to reduce memory usage by this way, should I keep
this kind of patches out of tree?

thanks,
Hiroshi

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