From: Shukun Tan <tanshukun1@huawei.com>
To: b6da310b-e633-9f74-f7af-7791d803aaf5@huawei.com,
Zhou Wang <wangzhou1@hisilicon.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] crypto: hisilicon - allow smaller reads in debugfs
Date: Fri, 05 Jun 2020 01:19:53 +0000 [thread overview]
Message-ID: <3e9b204f-ef53-31c5-afcd-e0791224c2b0@huawei.com> (raw)
In-Reply-To: <20200602135409.GA59808@mwanda>
Hi Dan,
On 2020/6/2 21:54, Dan Carpenter wrote:
> Originally this code rejected any read less than 256 bytes. There
> is no need for this artificial limit. We should just use the normal
> helper functions to read a string from the kernel.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> v2: Use simple_read_from_buffer(). The v1 was slightly half arsed
> because I left the original check for:
>
> if (*pos)
> return 0;
>
> So it could result in partial reads. The new code means that if you
> want to read the buffer one byte at a time, that's fine or if you want
> to read it in one 256 byte chunk that's also fine. Plus it deletes 21
> lines of code and is a lot cleaner.
>
In fact, In our original design, we do not hope the user do the partial reads.
Thank you for your work, but I still insist on adding this limit.
Thanks,
Shukun
> drivers/crypto/hisilicon/qm.c | 33 ++++++---------------------------
> 1 file changed, 6 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/crypto/hisilicon/qm.c b/drivers/crypto/hisilicon/qm.c
> index 9bb263cec6c30..13ccb9e29a2e1 100644
> --- a/drivers/crypto/hisilicon/qm.c
> +++ b/drivers/crypto/hisilicon/qm.c
> @@ -1064,19 +1064,10 @@ static ssize_t qm_cmd_read(struct file *filp, char __user *buffer,
> char buf[QM_DBG_READ_LEN];
> int len;
>
> - if (*pos)
> - return 0;
> -
> - if (count < QM_DBG_READ_LEN)
> - return -ENOSPC;
> + len = scnprintf(buf, QM_DBG_READ_LEN, "%s\n",
> + "Please echo help to cmd to get help information");
>
> - len = snprintf(buf, QM_DBG_READ_LEN, "%s\n",
> - "Please echo help to cmd to get help information");
> -
> - if (copy_to_user(buffer, buf, len))
> - return -EFAULT;
> -
> - return (*pos = len);
> + return simple_read_from_buffer(buffer, count, pos, buf, len);
> }
>
> static void *qm_ctx_alloc(struct hisi_qm *qm, size_t ctx_size,
> @@ -2691,24 +2682,12 @@ static ssize_t qm_status_read(struct file *filp, char __user *buffer,
> {
> struct hisi_qm *qm = filp->private_data;
> char buf[QM_DBG_READ_LEN];
> - int val, cp_len, len;
> -
> - if (*pos)
> - return 0;
> -
> - if (count < QM_DBG_READ_LEN)
> - return -ENOSPC;
> + int val, len;
>
> val = atomic_read(&qm->status.flags);
> - len = snprintf(buf, QM_DBG_READ_LEN, "%s\n", qm_s[val]);
> - if (!len)
> - return -EFAULT;
> -
> - cp_len = copy_to_user(buffer, buf, len);
> - if (cp_len)
> - return -EFAULT;
> + len = scnprintf(buf, QM_DBG_READ_LEN, "%s\n", qm_s[val]);
>
> - return (*pos = len);
> + return simple_read_from_buffer(buffer, count, pos, buf, len);
> }
>
> static const struct file_operations qm_status_fops = {
>
next prev parent reply other threads:[~2020-06-05 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 13:54 [PATCH v2] crypto: hisilicon - allow smaller reads in debugfs Dan Carpenter
2020-06-05 1:19 ` Shukun Tan [this message]
2020-06-05 9:13 ` Dan Carpenter
2020-06-18 7:56 ` Herbert Xu
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=3e9b204f-ef53-31c5-afcd-e0791224c2b0@huawei.com \
--to=tanshukun1@huawei.com \
--cc=b6da310b-e633-9f74-f7af-7791d803aaf5@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.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;
as well as URLs for NNTP newsgroup(s).