Re: [x86] copy_from{to}_user question

From: yalin wang
Date: Sun Aug 16 2015 - 23:27:13 EST



> On Aug 14, 2015, at 00:43, Borislav Petkov <bp@xxxxxxx> wrote:
>
> On Thu, Aug 13, 2015 at 06:04:54PM +0800, yalin wang wrote:
>> we store type into one fix register, for example r12 ,
>> then in fix up code, we can know the exception is caused by copy_from
>> copy_to or copy_in user function by check r12 value(0 , 1 ,2 value), then if
>> it is copy_from, we only allow read fault, if the exception is write fault, panic() .
>>
>> the same rules also apply to copy_to / copy_in function .
>>
>> is it possible to change it like this ?
>
> ... and we'll do all that jumping through hoops to fix what actual,
> real-life problem exactly?
i just want the x86 copy_from{to,in}_user() function have
the same behaviour as other platforms.
and can disclose potential BUGs in kernel, if do like this.

Thanks.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/