linux-kernel - what's the replace for the big kernel lock after kernel version 2.6.39 for system call.

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-next>] [day] [month] [year] [list]

Date:	Mon, 28 Nov 2011 01:03:07 -0800
From:	Wen Yan Xin <WenYan_Xin@...antec.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	Zongliang Li <Zongliang_Li@...antec.com>,
	Gang He <Gang_He@...antec.com>,
	Yong Jun Chai <YongJun_Chai@...antec.com>
Subject: what's the replace for the big kernel lock after kernel version
 2.6.39 for system call.

Hi all,

I have a trouble of working on kernel 2.6.39 and later. Originally when our kernel module startups, it hooks some file system call, like sys_open... , and the big kernel lock - lock_kernel() - will be held before creating the hook to prevent user application use system calls, and be released after the hook created.

But after the kernel 2.6.39, the big kernel lock has been removed. I'm thinking there should be one or more lock that should be used. 

So, my question is which lock should be held now, when we hook the system call of file system?

I'd really appreciate your answer in advance.

--

>>>> 	auth ca64a8ac subscribe linux-kernel wenyan_xin@...antec.com
Succeeded.
--
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/