From: Conor Dooley <conor@kernel.org>
To: Qinglin Pan <panqinglin2020@iscas.ac.cn>
Cc: atishp@atishpatra.org, alex@ghiti.fr,
linux-riscv@lists.infradead.org, palmer@dabbelt.com
Subject: Re: [PATCH v1 1/1] riscv: mm: add missing memcpy in kasan_init
Date: Sun, 9 Oct 2022 14:32:31 +0100 [thread overview]
Message-ID: <Y0LNb6lJ2eQ7/O21@spud> (raw)
In-Reply-To: <2de46c94-0792-7a4b-5bcd-d57fffe1160c@iscas.ac.cn>
On Sun, Oct 09, 2022 at 09:25:31PM +0800, Qinglin Pan wrote:
> On 10/9/22 7:30 PM, Conor Dooley wrote:
> > On Sun, Oct 09, 2022 at 04:30:50PM +0800, panqinglin2020@iscas.ac.cn wrote:
> > > From: Qinglin Pan <panqinglin2020@iscas.ac.cn>
> > >
> > > Hi Atish,
> > >
> > > It seems that the panic is due to the missing memcpy during kasan_init.
> > > Could you please check whether this patch is helpful?
> >
> > If this does solve the problem it would be:
> > Fixes: 8fbdccd2b173 ("riscv: mm: Support kasan for sv57")
> > right?
> >
> > Thanks,
> > Conor.
> >
>
> Hi Conor,
>
> Thanks a lot for notification!
> I have change the title and resend it.
Unfortunately I was not suggesting a new title for the patch.. A
"Fixes:" tag goes as part of the sign off block to show what commit a
given patch fixes. Your original title looks fine to me.
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-10-09 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 0:10 KASAN/pcpu_alloc related panics on v6.0 Atish Patra
2022-10-09 8:30 ` [PATCH v1 1/1] riscv: mm: add missing memcpy in kasan_init panqinglin2020
2022-10-09 11:30 ` Conor Dooley
2022-10-09 13:25 ` Qinglin Pan
2022-10-09 13:32 ` Conor Dooley [this message]
2022-10-10 6:49 ` Atish Patra
2022-10-14 16:34 ` Palmer Dabbelt
2022-10-27 22:45 ` Palmer Dabbelt
2022-10-09 13:23 ` [PATCH v1 1/1] Fixes: 8fbdccd2b173 ("riscv: mm: Support kasan for sv57") panqinglin2020
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=Y0LNb6lJ2eQ7/O21@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=atishp@atishpatra.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=panqinglin2020@iscas.ac.cn \
/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