From: Damien Le Moal <dlemoal@kernel.org>
To: Ajay Kaher <ajay.kaher@broadcom.com>,
axboe@kernel.dk, niklas.cassel@wdc.com, hare@suse.de,
martin.petersen@oracle.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
alexey.makhalov@broadcom.com, vasavi.sirnapalli@broadcom.com,
vamsi-krishna.brahmajosyula@broadcom.com
Subject: Re: [PATCH] block: Fix validation of ioprio level
Date: Wed, 28 Aug 2024 17:45:36 +0900 [thread overview]
Message-ID: <a5609ba3-cc35-41c5-98f1-52063f8a6eec@kernel.org> (raw)
In-Reply-To: <1724833695-22194-1-git-send-email-ajay.kaher@broadcom.com>
On 8/28/24 17:28, Ajay Kaher wrote:
> The commit eca2040972b4 introduced a backward compatibility issue in
> the function ioprio_check_cap.
>
> Before the change, if ioprio contains a level greater than 0x7, it was
> treated as -EINVAL:
>
> data = ioprio & 0x1FFF
> if data >= 0x7, return -EINVAL
>
> Since the change, if ioprio contains a level greater than 0x7 say 0x8
> it is calculated as 0x0:
>
> level = ioprio & 0x7
>
> To maintain backward compatibility the kernel should return -EINVAL in
> the above case as well.
>
> Fixes: eca2040972b4 ("scsi: block: ioprio: Clean up interface definition")
> Signed-off-by: Ajay Kaher <ajay.kaher@broadcom.com>
> ---
> block/ioprio.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/block/ioprio.c b/block/ioprio.c
> index 73301a2..f08e76b 100644
> --- a/block/ioprio.c
> +++ b/block/ioprio.c
> @@ -30,6 +30,15 @@
> #include <linux/security.h>
> #include <linux/pid_namespace.h>
>
> +static inline int ioprio_check_level(int ioprio, int max_level)
> +{
> + int data = IOPRIO_PRIO_DATA(ioprio);
> +
> + if (IOPRIO_BAD_VALUE(data, max_level))
> + return -EINVAL;
No, this cannot possibly work correctly because the prio level part of the prio
data is only 3 bits, so 0 to 7. The remaining 10 bits of the prio data are used
for priority hints (IOPRIO_HINT_XXX).
Your change will thus return an error for cases where the prio data has a level
AND also a hint (e.g. for command duration limits). This change would break
command duration limits. So NACK.
The userspace header file has the ioprio_value() that a user should use to
construct an ioprio. Bad values are checked in that function and errors will be
returned if an invalid level is passed.
> + return 0;
> +}
> +
> int ioprio_check_cap(int ioprio)
> {
> int class = IOPRIO_PRIO_CLASS(ioprio);
> @@ -49,7 +58,7 @@ int ioprio_check_cap(int ioprio)
> fallthrough;
> /* rt has prio field too */
> case IOPRIO_CLASS_BE:
> - if (level >= IOPRIO_NR_LEVELS)
> + if (ioprio_check_level(ioprio, IOPRIO_NR_LEVELS))
> return -EINVAL;
> break;
> case IOPRIO_CLASS_IDLE:
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-08-28 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 8:28 Ajay Kaher
2024-08-28 8:45 ` Damien Le Moal [this message]
2024-09-09 8:59 ` Ajay Kaher
2024-09-09 10:20 ` Damien Le Moal
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=a5609ba3-cc35-41c5-98f1-52063f8a6eec@kernel.org \
--to=dlemoal@kernel.org \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=niklas.cassel@wdc.com \
--cc=vamsi-krishna.brahmajosyula@broadcom.com \
--cc=vasavi.sirnapalli@broadcom.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
Powered by JetHome