LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: Jiri Slaby <jirislaby@kernel.org>,
	gregkh@linuxfoundation.org, amit@kernel.org, arnd@arndb.de
Cc: linuxppc-dev@lists.ozlabs.org,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, osandov@fb.com
Subject: Re: [PATCH 2/2] virtio-console: remove unnecessary kmemdup()
Date: Mon, 2 Aug 2021 16:55:53 +0800	[thread overview]
Message-ID: <61a6d459-338b-7e77-c78e-3a069bbfd690@linux.alibaba.com> (raw)
In-Reply-To: <a2598ec9-7bc9-be42-bcab-fa19c9e734f7@kernel.org>


在 2021/8/2 下午4:40, Jiri Slaby 写道:
> On 02. 08. 21, 10:32, Xianting Tian wrote:
>>
>> 在 2021/8/2 下午3:25, Jiri Slaby 写道:
>>> Hi,
>>>
>>> why is this 2/2? I seem (Lore neither) to find 1/2.
>> You didn't receive 1/2?
>> [PATCH 1/2] tty: hvc: pass DMA capable memory to put_chars()
>> https://lkml.org/lkml/2021/8/1/8 <https://lkml.org/lkml/2021/8/1/8>
>
> Oh, I did, but it's not properly threaded. PLease fix your setup.
Ok, thanks
>
>>> On 01. 08. 21, 7:16, Xianting Tian wrote:
>>>> hvc framework will never pass stack memory to the put_chars() 
>>>> function,
>>>
>>> Am I blind or missing something?
>>>
>>> hvc_console_print(...)
>>> {
>>>   char c[N_OUTBUF]
>>> ...
>>>   cons_ops[index]->put_chars(vtermnos[index], c, i);
>>>
>>> The same here:
>>>
>>> hvc_poll_put_char(..., char ch)
>>> {
>>> ...
>>>    n = hp->ops->put_chars(hp->vtermno, &ch, 1);
>>>
>>> AFAICS both of them *pass* a pointer to stack variable.
>>
>> yes, I discussed the issue with Arnd before in below thread, you can 
>> get the history, thanks
>>
>> https://lkml.org/lkml/2021/7/27/494 
>> <https://lkml.org/lkml/2021/7/27/494>
>
> So is this a v2? You should have noted that. And what changed from v1 
> too.

I think yes, I should mentioned it in this patch, sorry for that:(

>
>>>> So the calling of kmemdup() is unnecessary, remove it.
>>>>
>>>> Fixes: c4baad5029 ("virtio-console: avoid DMA from stack")
>>>
>>> This patch doesn't "Fix" -- it reverts the commit. You should've 
>>> CCed the author too.
>>
>> yes, we discussed ther issue in above thread, which we CCed the author.
>
> I don't see any input from the author?
>
>
> Anyway, 1/2 does not even build, so you will send v3 with all the 
> above fixed, hopefully.

yes, I will send v3 patch after I figured out a better solution based on 
Arnd's comments for the patch '1/2'.

Do you have any other suggestion for the solution?

thanks.

>
> thanks,

      reply	other threads:[~2021-08-02  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01  5:16 Xianting Tian
2021-08-02  7:25 ` Jiri Slaby
     [not found]   ` <5ad81a0e-fbb2-a849-6db7-f5718633d282@linux.alibaba.com>
2021-08-02  8:40     ` Jiri Slaby
2021-08-02  8:55       ` Xianting Tian [this message]

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=61a6d459-338b-7e77-c78e-3a069bbfd690@linux.alibaba.com \
    --to=xianting.tian@linux.alibaba.com \
    --cc=amit@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=osandov@fb.com \
    --cc=virtualization@lists.linux-foundation.org \
    --subject='Re: [PATCH 2/2] virtio-console: remove unnecessary kmemdup()' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).