From: Dongsheng Yang <dongsheng.yang@easystack.cn>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Dongsheng Yang <dongsheng.yang.linux@gmail.com>
Subject: Re: [PATCH 2/7] cbd: introduce cbd_transport
Date: Wed, 24 Apr 2024 16:43:47 +0800 [thread overview]
Message-ID: <7ec61a75-79ec-94db-ebf9-58679c85edeb@easystack.cn> (raw)
In-Reply-To: <780f3ccd-5112-4948-81c3-3144c6779503@nvidia.com>
在 2024/4/24 星期三 下午 12:08, Chaitanya Kulkarni 写道:
>> +static ssize_t cbd_myhost_show(struct device *dev,
>> + struct device_attribute *attr,
>> + char *buf)
>> +{
>> + struct cbd_transport *cbdt;
>> + struct cbd_host *host;
>> +
>> + cbdt = container_of(dev, struct cbd_transport, device);
>> +
>> + host = cbdt->host;
>> + if (!host)
>> + return 0;
>> +
>> + return sprintf(buf, "%d\n", host->host_id);
>
> snprintf() ?
IMO, it will only print a decimal unsigned int, so it shouldn't overflow
the buffer.
>
>> +}
>> +
>> +static DEVICE_ATTR(my_host_id, 0400, cbd_myhost_show, NULL);
>> +
>> +enum {
>
> [...]
>
>> +
>> +static ssize_t cbd_adm_store(struct device *dev,
>> + struct device_attribute *attr,
>> + const char *ubuf,
>> + size_t size)
>> +{
>> + int ret;
>> + char *buf;
>> + struct cbd_adm_options opts = { 0 };
>> + struct cbd_transport *cbdt;
>> +
>
> reverse tree order that matches rest of your code ?
Agreed,
>
>> + if (!capable(CAP_SYS_ADMIN))
>> + return -EPERM;
>> +
>> + cbdt = container_of(dev, struct cbd_transport, device);
>> +
>> + buf = kmemdup(ubuf, size + 1, GFP_KERNEL);
>> + if (IS_ERR(buf)) {
>> + pr_err("failed to dup buf for adm option: %d", (int)PTR_ERR(buf));
>> + return PTR_ERR(buf);
>> + }
>> + buf[size] = '\0';
>> + ret = parse_adm_options(cbdt, buf, &opts);
>> + if (ret < 0) {
>> + kfree(buf);
>> + return ret;
>> + }
>> + kfree(buf);
>> +
>
> standard format is using goto out and having only on kfree()
> at the end of the function ...
Okey, having a unified error handling path is a good idea, and it's
suitable here as well, thanx.
>
>> + switch (opts.op) {
>> + case CBDT_ADM_OP_B_START:
>> + break;
>> + case CBDT_ADM_OP_B_STOP:
>> + break;
>> + case CBDT_ADM_OP_B_CLEAR:
>> + break;
>> + case CBDT_ADM_OP_DEV_START:
>> + break;
>> + case CBDT_ADM_OP_DEV_STOP:
>> + break;
>> + default:
>> + pr_err("invalid op: %d\n", opts.op);
>> + return -EINVAL;
>> + }
>> +
>> + if (ret < 0)
>> + return ret;
>> +
>> + return size;
>> +}
>> +
>
> [...]
>
>> +static struct cbd_transport *cbdt_alloc(void)
>> +{
>> + struct cbd_transport *cbdt;
>> + int ret;
>> +
>> + cbdt = kzalloc(sizeof(struct cbd_transport), GFP_KERNEL);
>> + if (!cbdt) {
>> + return NULL;
>> + }
>
> no braces needed for single statements in if ... applies rest of
> the code ...
thanx, Iwill remove unnecessary braces next version.
>
> -ck
>
>
next prev parent reply other threads:[~2024-04-24 15:52 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 7:15 [PATCH RFC 0/7] block: Introduce CBD (CXL Block Device) Dongsheng Yang
2024-04-22 7:16 ` [PATCH 1/7] block: Init for CBD(CXL " Dongsheng Yang
2024-04-22 18:39 ` Randy Dunlap
2024-04-22 22:41 ` Dongsheng Yang
2024-04-24 3:58 ` Chaitanya Kulkarni
2024-04-24 8:36 ` Dongsheng Yang
2024-04-22 7:16 ` [PATCH 2/7] cbd: introduce cbd_transport Dongsheng Yang
2024-04-24 4:08 ` Chaitanya Kulkarni
2024-04-24 8:43 ` Dongsheng Yang [this message]
2024-04-22 7:16 ` [PATCH 3/7] cbd: introduce cbd_channel Dongsheng Yang
2024-04-22 7:16 ` [PATCH 4/7] cbd: introduce cbd_host Dongsheng Yang
2024-04-25 5:51 ` [EXTERNAL] " Bharat Bhushan
2024-04-22 7:16 ` [PATCH 5/7] cbd: introuce cbd_backend Dongsheng Yang
2024-04-24 5:03 ` Chaitanya Kulkarni
2024-04-24 8:36 ` Dongsheng Yang
2024-04-25 5:46 ` [EXTERNAL] " Bharat Bhushan
2024-04-22 7:16 ` [PATCH 7/7] cbd: add related sysfs files in transport register Dongsheng Yang
2024-04-25 5:24 ` [EXTERNAL] " Bharat Bhushan
2024-04-22 22:42 ` [PATCH 6/7] cbd: introduce cbd_blkdev Dongsheng Yang
2024-04-23 7:27 ` Dongsheng Yang
2024-04-24 4:29 ` [PATCH RFC 0/7] block: Introduce CBD (CXL Block Device) Dan Williams
2024-04-24 6:33 ` Dongsheng Yang
2024-04-24 15:14 ` Gregory Price
2024-04-26 1:25 ` Dongsheng Yang
2024-04-26 13:48 ` Gregory Price
2024-04-26 14:53 ` Dongsheng Yang
2024-04-26 16:14 ` Gregory Price
2024-04-28 5:47 ` Dongsheng Yang
2024-04-28 16:44 ` Gregory Price
2024-04-28 16:55 ` John Groves
2024-05-03 9:52 ` Jonathan Cameron
2024-05-08 11:39 ` Dongsheng Yang
2024-05-08 12:11 ` Jonathan Cameron
2024-05-08 13:03 ` Dongsheng Yang
2024-05-08 15:44 ` Jonathan Cameron
2024-05-09 11:24 ` Dongsheng Yang
2024-05-09 12:21 ` Jonathan Cameron
2024-05-09 13:03 ` Dongsheng Yang
2024-05-21 18:41 ` Dan Williams
2024-05-22 6:17 ` Dongsheng Yang
2024-05-29 15:25 ` Gregory Price
2024-05-30 6:59 ` Dongsheng Yang
2024-05-30 13:38 ` Jonathan Cameron
2024-06-01 3:22 ` Dan Williams
2024-06-03 12:48 ` Jonathan Cameron
2024-06-03 17:28 ` James Morse
2024-06-04 14:26 ` Jonathan Cameron
2024-05-31 14:23 ` Gregory Price
2024-06-03 1:33 ` Dongsheng Yang
2024-04-30 0:34 ` Dan Williams
2024-04-24 18:08 ` Dan Williams
[not found] ` <539c1323-68f9-d753-a102-692b69049c20@easystack.cn>
2024-04-30 0:10 ` Dan Williams
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=7ec61a75-79ec-94db-ebf9-58679c85edeb@easystack.cn \
--to=dongsheng.yang@easystack.cn \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=dongsheng.yang.linux@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).