mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qi Hu <huqi@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>, Oleg Nesterov <oleg@redhat.com>,
	Xu Li <lixu@loongson.cn>,
	loongarch@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] LoongArch: Fix missing fcsr in ptrace's fpr_set
Date: Thu, 14 Jul 2022 22:07:52 +0800	[thread overview]
Message-ID: <6896bb4c-5224-678f-e73c-fe95be41d196@loongson.cn> (raw)
In-Reply-To: <CAAhV-H6NWYG1ChLRyK-EAGAmhDvP-x+z9BgBo3a=GAbQ-2bKig@mail.gmail.com>


On 2022/7/14 21:12, Huacai Chen wrote:
> Hi,
>
> On Thu, Jul 14, 2022 at 2:26 PM Qi Hu <huqi@loongson.cn> wrote:
>> In file ptrace.c, function fpr_set does not copy fcsr data from ubuf
>> to kbuf. That's the reason why fcsr cannot be modified by ptrace.
>>
>> This patch fixs this problem and allows users using ptrace to modify
>> the fcsr.
>>
>> Signed-off-by: Qi Hu <huqi@loongson.cn>
>> Signed-off-by: Xu Li <lixu@loongson.cn>
>> ---
>>   arch/loongarch/kernel/ptrace.c | 12 +++++++-----
>>   1 file changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/loongarch/kernel/ptrace.c b/arch/loongarch/kernel/ptrace.c
>> index e6ab87948e1d..dc2b82ea894c 100644
>> --- a/arch/loongarch/kernel/ptrace.c
>> +++ b/arch/loongarch/kernel/ptrace.c
>> @@ -193,7 +193,7 @@ static int fpr_set(struct task_struct *target,
>>                     const void *kbuf, const void __user *ubuf)
>>   {
>>          const int fcc_start = NUM_FPU_REGS * sizeof(elf_fpreg_t);
>> -       const int fcc_end = fcc_start + sizeof(u64);
>> +       const int fcsr_start = fcc_start + sizeof(u64);
>>          int err;
>>
>>          BUG_ON(count % sizeof(elf_fpreg_t));
>> @@ -209,10 +209,12 @@ static int fpr_set(struct task_struct *target,
>>          if (err)
>>                  return err;
>>
>> -       if (count > 0)
>> -               err |= user_regset_copyin(&pos, &count, &kbuf, &ubuf,
>> -                                         &target->thread.fpu.fcc,
>> -                                         fcc_start, fcc_end);
>> +       err |= user_regset_copyin(&pos, &count, &kbuf, &ubuf,
>> +                                 &target->thread.fpu.fcc, fcc_start,
>> +                                 fcc_start + sizeof(u64));
>> +       err |= user_regset_copyin(&pos, &count, &kbuf, &ubuf,
>> +                                 &target->thread.fpu.fcsr, fcsr_start,
>> +                                 fcsr_start + sizeof(u32));
> You shouldn't remove (count > 0) here, because  the above
> user_regset_copyin() will modify count inside, and so "count == 0" is
> possible.
>
> Huacai

Yes, the "count" should be considered. But the "count" is checked at the 
beginning of the "user_regset_copyin()".

So "count > 0" is useless, i think.

Also like riscv, "count" is not checked in "riscv_fpr_set()".

>>          return err;
>>   }
>> --
>> 2.37.0
>>


  reply	other threads:[~2022-07-14 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  6:25 Qi Hu
2022-07-14  6:51 ` Conor.Dooley
2022-07-14  7:14   ` Qi Hu
2022-07-14 13:12 ` Huacai Chen
2022-07-14 14:07   ` Qi Hu [this message]
2022-07-15  3:20     ` Huacai Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6896bb4c-5224-678f-e73c-fe95be41d196@loongson.cn \
    --to=huqi@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixu@loongson.cn \
    --cc=loongarch@lists.linux.dev \
    --cc=oleg@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®