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: <CAPb+xgOKD3URc3ViJaYm65TOT1tmPMHK4BfpUn+9khCA9SOGOA@mail.gmail.com>
Date:	Sun, 27 Jul 2014 14:28:05 +0530
From:	zubraz singha <zubrajsingha@...il.com>
To:	Richard Weinberger <richard@....at>
Cc:	Richard Weinberger <richard.weinberger@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: "copy_to_user" function not working in stable build "2.6.36.4"

My mistake,  I forgot to add this, the "copy_to_user" function I'm
referring here is for "X86"
based architecture.

What I have found:
-> 2.6.36.4
*  "copy_to_user" calls "_copy_to_user"
* "_copy_to_user" no definition.

-> 3.14
* copy_to_user calls "_copy_to_user"
* "_copy_to_user" has a definiton
* _copy_to_user is  defined as a function call to access_ok function
and __copy_to_user.

 I was just wondering if the fix present in kernel versions "3.14" for
this , will work straight forward on "2.6.36.4". What I mean is
whether back porting of this fix will work, or there are other
parameters to consider.




On 7/27/14, Richard Weinberger <richard@....at> wrote:
> Am 27.07.2014 10:44, schrieb zubraz singha:
>> I do understand that this is a very old build and its not being
>> supported. As I wrote in my earlier mail,  the function works fine
>> with higher kernel versions. I will try to find out a work around for
>> this. Appreciate your feedback.
>
> First I'd look into 2.6.32.x. Maybe it needed fixing and you can forward
> port the fix. :)
>
> Thanks,
> //richard
>


-- 
-- Regards
Zubraj Singha
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ