linux-kernel - Re: [PATCH] ramster: depend on CONFIG_NET for sock

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:	Mon, 7 May 2012 10:29:23 +0200
From:	Sasha Levin <levinsasha928@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	gregkh@...uxfoundation.org, dan.magenheimer@...cle.com,
	sjenning@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ramster: depend on CONFIG_NET for sock_* functions

On Mon, May 7, 2012 at 10:10 AM, Paul Bolle <pebolle@...cali.nl> wrote:
> On Mon, 2012-05-07 at 10:02 +0200, Sasha Levin wrote:
>> Building ramster without CONFIG_NET would cause linkage issue due to missing
>
> I'd say s/CONFIG_NET/NET/
>
>> sock_*() functions in cluster/tcp.c
>>
>> Signed-off-by: Sasha Levin <levinsasha928@...il.com>
>> ---
>>  drivers/staging/ramster/Kconfig |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/staging/ramster/Kconfig b/drivers/staging/ramster/Kconfig
>> index 4af1f8d..8e334cb 100644
>> --- a/drivers/staging/ramster/Kconfig
>> +++ b/drivers/staging/ramster/Kconfig
>> @@ -1,6 +1,6 @@
>>  config RAMSTER
>>       bool "Cross-machine RAM capacity sharing, aka peer-to-peer tmem"
>> -     depends on (CLEANCACHE || FRONTSWAP) && CONFIGFS_FS=y && !ZCACHE && !XVMALLOC && !HIGHMEM
>> +     depends on (CLEANCACHE || FRONTSWAP) && CONFIGFS_FS=y && !ZCACHE && !XVMALLOC && !HIGHMEM && CONFIG_NET
>
> s/CONFIG_NET/NET/ again, I'd say. How was this tested?

Hm... ran the build again with the patch and noticed it stopped
complaining, but apparently it wasn't enough.
--
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/