On Tue, Dec 23, 2014 at 11:57 PM, Catalin Marinas
wrote:
> On Tue, Dec 23, 2014 at 03:15:10PM +, Min-Hua Chen wrote:
>> Setup return path for el1_undef since el1_undef may
>> be handled by handlers.
>
> Did you find a real issue or it was just code inspection.
Thanks for your reply. It was
On Tue, Dec 23, 2014 at 03:15:10PM +, Min-Hua Chen wrote:
> Setup return path for el1_undef since el1_undef may
> be handled by handlers.
Did you find a real issue or it was just code inspection.
> asmlinkage void __exception do_undefinstr(struct pt_regs *regs)
> {
> siginfo_t info;
>
Setup return path for el1_undef since el1_undef may
be handled by handlers.
asmlinkage void __exception do_undefinstr(struct pt_regs *regs)
{
siginfo_t info;
void __user *pc = (void __user *)instruction_pointer(regs);
/* check for AArch32 breakpoint instructions */
if
Setup return path for el1_undef since el1_undef may
be handled by handlers.
asmlinkage void __exception do_undefinstr(struct pt_regs *regs)
{
siginfo_t info;
void __user *pc = (void __user *)instruction_pointer(regs);
/* check for AArch32 breakpoint instructions */
if
On Tue, Dec 23, 2014 at 03:15:10PM +, Min-Hua Chen wrote:
Setup return path for el1_undef since el1_undef may
be handled by handlers.
Did you find a real issue or it was just code inspection.
asmlinkage void __exception do_undefinstr(struct pt_regs *regs)
{
siginfo_t info;
void
On Tue, Dec 23, 2014 at 11:57 PM, Catalin Marinas
catalin.mari...@arm.com wrote:
On Tue, Dec 23, 2014 at 03:15:10PM +, Min-Hua Chen wrote:
Setup return path for el1_undef since el1_undef may
be handled by handlers.
Did you find a real issue or it was just code inspection.
Thanks for your
6 matches
Mail list logo