linux-kernel - Re: [PATCH] Kconfig: XIP doesn't depend on block

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: <AANLkTi=T3TGYcxm2=C6QtYss09H9R+m0Zk9KDQepMqiL@mail.gmail.com>
Date:	Mon, 7 Feb 2011 08:52:41 +0100
From:	Marco Stornelli <marco.stornelli@...il.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux FS Devel <linux-fsdevel@...r.kernel.org>,
	Linux Embedded <linux-embedded@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Kconfig: XIP doesn't depend on block

2011/2/6 Randy Dunlap <rdunlap@...otime.net>:
> On Sun, 06 Feb 2011 16:15:00 +0100 Marco Stornelli wrote:
>
>> From: Marco Stornelli <marco.stornelli@...il.com>
>>
>> XIP doesn't depend on block symbol, then we can reorder the Kconfig.
>> For ext2 doesn't change the Kconfig behavior but if other fs will use
>> FS_XIP it won't need to include block support if not needed.
>
> Hi Marco,
>
> Do you know of a filesystem where this matters?
>

Yes, for example mine (pramfs) :)

>> Signed-off-by: Marco Stornelli <marco.stornelli@...il.com>
>> ---
>>
>> --- Kconfig.orig      2011-01-19 00:14:02.000000000 +0100
>> +++ Kconfig   2011-02-06 16:04:51.000000000 +0100
>
> This filename should include path, like
> --- fs/Kconfig.orig
> +++ fs/Kconfig
>
>> @@ -9,13 +9,6 @@ if BLOCK
>>  source "fs/ext2/Kconfig"
>>  source "fs/ext3/Kconfig"
>>  source "fs/ext4/Kconfig"
>> -
>
> The 3 filesystems above are immediately under:
>
> if BLOCK
>
> so ext[234] depend on BLOCK.  Why would it matter about FS_XIP?
>

I don't know but for example even POSIX ACL was under "if BLOCK",
maybe there is only an historical refuse.

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