linux-kernel - Re: ioctl definition - has it changed recently?

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: <4C68E4A5.3050800@example.com>
Date:	Mon, 16 Aug 2010 09:11:33 +0200
From:	Piotr Hosowicz <piotr@...owicz.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: ioctl definition - has it changed recently?

On 16.08.2010 08:58, Arnd Bergmann wrote:
> On Sunday 15 August 2010 00:10:29 Piotr Hosowicz wrote:
>> Yes, this was it. I made git pull and git revert and now I am up and
>> kicking. But how will I manage with it not by git but by kernel org
>> provioded files? And even if I used git all the time will I have to
>> revert it each time and what's the worse I will become more and more out
>> of sync because people will write their code as if I did not revert.
>
> Just fix your driver code to no longer rely on the big kernel lock

Now I know how to do it.

> and then make it use the unlocked_ioctl operation.

This I do not know. Can You help me?

Regards,

Piotr Hosowicz

-- 
"[Oleksy] dotknął naszych domów, naszych żon, naszych dzieci,
naszych psów, naszych ŚWINEK MORSKICH, on po prostu wkroczył
swoim głupim gadaniem w sferę prywatną, która musi być chro-
niona dla dobra każdego z nas" - powiedział Kwaśniewski.
NP: Patrick O'Hearn - Night Becomes Her
NB: 2.6.35-git16
--
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/