From: Muneendra Kumar M <muneendra.kumar@broadcom.com>
To: James Smart <jsmart2021@gmail.com>,
Christoph Hellwig <hch@lst.de>,
"Ewan D. Milne" <emilne@redhat.com>
Cc: linux-nvme@lists.infradead.org,
James Smart <james.smart@broadcom.com>,
stable@vger.kernel.org
Subject: RE: [PATCH] Revert "nvme-fc: fold t fc_update_appid into fc_appid_store"
Date: Wed, 3 Aug 2022 10:08:48 +0530 [thread overview]
Message-ID: <6c03a873a639253c8af685b0e4849fb5@mail.gmail.com> (raw)
In-Reply-To: <0b5001ed-050f-f5d0-72ee-3cc2ffc7f9b8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2773 bytes --]
I have tested the below changes suggested by Christoph and it is working as
expected.
Tested-by: <muneendra.kumar@broadcom.com>
-----Original Message-----
From: James Smart [mailto:jsmart2021@gmail.com]
Sent: Tuesday, August 2, 2022 2:33 AM
To: Christoph Hellwig <hch@lst.de>; Ewan D. Milne <emilne@redhat.com>
Cc: linux-nvme@lists.infradead.org; muneendra.kumar@broadcom.com;
james.smart@broadcom.com; stable@vger.kernel.org
Subject: Re: [PATCH] Revert "nvme-fc: fold t fc_update_appid into
fc_appid_store"
On 8/1/2022 11:27 AM, Christoph Hellwig wrote:
> On Mon, Aug 01, 2022 at 12:27:13PM -0400, Ewan D. Milne wrote:
>> This reverts commit c814153c83a892dfd42026eaa661ae2c1f298792.
>>
>> The commit c814153c83a8 "nvme-fc: fold t fc_update_appid into
>> fc_appid_store"
>> changed the userspace interface, because the code that decrements "count"
>> to remove a trailing '\n' in the parsing results in the decremented
>> value being incorrectly be returned from the sysfs write. Fix this by
>> revering the commit.
>
> Wouldn't something like the patch below be much simpler and cleaner:
>
>
> diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c index
> 9987797620b6d..e24ab688f00d5 100644
> --- a/drivers/nvme/host/fc.c
> +++ b/drivers/nvme/host/fc.c
> @@ -3878,6 +3878,7 @@ static int fc_parse_cgrpid(const char *buf, u64 *id)
> static ssize_t fc_appid_store(struct device *dev,
> struct device_attribute *attr, const char *buf, size_t count)
> {
> + size_t orig_count = count;
> u64 cgrp_id;
> int appid_len = 0;
> int cgrpid_len = 0;
> @@ -3902,7 +3903,7 @@ static ssize_t fc_appid_store(struct device *dev,
> ret = blkcg_set_fc_appid(app_id, cgrp_id, sizeof(app_id));
> if (ret < 0)
> return ret;
> - return count;
> + return orig_count;
> }
> static DEVICE_ATTR(appid_store, 0200, NULL, fc_appid_store);
> #endif /* CONFIG_BLK_CGROUP_FC_APPID */
>
Reviewed-by: James Smart <jsmart2021@gmail.com>
looks good on my end.
-- james
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4220 bytes --]
next prev parent reply other threads:[~2022-08-03 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 16:27 [PATCH] Revert "nvme-fc: fold t fc_update_appid into fc_appid_store" Ewan D. Milne
2022-08-01 18:27 ` Christoph Hellwig
2022-08-01 21:03 ` James Smart
2022-08-03 4:38 ` Muneendra Kumar M [this message]
2022-08-03 16:34 ` Ewan D. Milne
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=6c03a873a639253c8af685b0e4849fb5@mail.gmail.com \
--to=muneendra.kumar@broadcom.com \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=jsmart2021@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=stable@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