linux-kernel - Re: [PATCH 0/2] module_refcounting and anonymous inodes

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: <493E7122.5010904@redhat.com>
Date:	Tue, 09 Dec 2008 15:22:42 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Christian Borntraeger <borntraeger@...ibm.com>
CC:	Sheng Yang <sheng@...ux.intel.com>, kvm@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] module_refcounting and anonymous inodes

Avi Kivity wrote:
> Christian Borntraeger wrote:
>> The problem is, how do you detect if the base kernel has patch1 applied?
>>   
>
> In the external module compatibility kit, implement two versions of 
> anon_inode_getfd(), and select the appropriate one according to kernel 
> version (like we currently support 91 smp_call_function_single variants).
>

I committed something simpler:  if running on 2.6.28 or earlier, I hack 
out the two lines your second patch adds.\

-- 
error compiling committee.c: too many arguments to function

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