From: Shawn Lin <shawn.lin@rock-chips.com>
To: Seshagiri Holi <sholi@nvidia.com>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@rock-chips.com, shawn.lin@kernel-upstream.org,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: block: fix ABI regression of mmc_blk_ioctl
Date: Mon, 7 Mar 2016 15:16:57 +0800 [thread overview]
Message-ID: <56DD2AE9.7000708@rock-chips.com> (raw)
In-Reply-To: <4aa8686868a640499a9313f4a77ddc46@bgmail102.nvidia.com>
On 2016/3/7 15:04, Seshagiri Holi wrote:
> Hi Shawn,
> I am not sure how why blkdev_roset is iocl function call is landing in mmc_blk_ioctl. Could it be a IOCTL mapping issue ?
> Regards
> Seshagiri
>
Really no.
blkdev_ioctl-> case BLKROSET ->
blkdev_roset -> __blkdev_driver_ioctl ->disk->fops->ioctl
If mmc_blk_ioctl return -EINVAL, that will fails
the check of !is_unrecognized_ioctl. Then the code will continue
to work. But commit: a5f5774c55a2 ("mmc: block: Add new ioctl to send
multi commands") changes the behaviour to check the cmd(BLKROSET) with
CAP_SYS_RAWIO firstly. So blkdev_ioctl finally get -EPERM instead of
-EINVAL. So the result you can find:
remount of /system failed;
couldn't make block device writable: Operation not permitted
openat(AT_FDCWD, "/dev/block/platform/ff420000.dwmmc/by-name/system",
O_RDONLY) = 3 ioctl(3, BLKROSET, 0) = -1 EPERM (Operation not permitted)
>
> -----Original Message-----
> From: Shawn Lin [mailto:shawn.lin@rock-chips.com]
> Sent: Monday, March 07, 2016 11:54 AM
> To: Ulf Hansson
> Cc: Seshagiri Holi; Jonathan Hunter; Shawn Lin; stable@vger.kernel.org; #@263.net; 4.4.x@263.net
> Subject: [PATCH] mmc: block: fix ABI regression of mmc_blk_ioctl
>
> We should return -EINVAL if cmd is not MMC_IOC_CMD or MMC_IOC_MULTI_CMD, otherwise blkdev_roset will return -EPERM.
>
> Android-adb calls make_block_device_writable with ioctl(BLKROSET), which will return error, make remount failed:
> remount of /system failed;
> couldn't make block device writable: Operation not permitted
>
> openat(AT_FDCWD, "/dev/block/platform/ff420000.dwmmc/by-name/system", O_RDONLY) = 3 ioctl(3, BLKROSET, 0) = -1 EPERM (Operation not permitted)
>
> Fixes: a5f5774c55a2 ("mmc: block: Add new ioctl to send multi commands")
> Cc: <stable@vger.kernel.org> # 4.4.x
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> ---
>
> drivers/mmc/card/block.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c index 47bc87d..170f099 100644
> --- a/drivers/mmc/card/block.c
> +++ b/drivers/mmc/card/block.c
> @@ -688,6 +688,9 @@ cmd_err:
> static int mmc_blk_ioctl(struct block_device *bdev, fmode_t mode,
> unsigned int cmd, unsigned long arg)
> {
> + if (cmd != MMC_IOC_CMD && cmd != MMC_IOC_MULTI_CMD)
> + return -EINVAL;
> +
> /*
> * The caller must have CAP_SYS_RAWIO, and must be calling this on the
> * whole block device, not on a partition. This prevents overspray
> --
> 2.3.7
>
>
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain
> confidential information. Any unauthorized review, use, disclosure or distribution
> is prohibited. If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
>
>
>
--
Best Regards
Shawn Lin
next parent reply other threads:[~2016-03-07 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457331857-4953-1-git-send-email-shawn.lin@rock-chips.com>
[not found] ` <4aa8686868a640499a9313f4a77ddc46@bgmail102.nvidia.com>
2016-03-07 7:16 ` Shawn Lin [this message]
2016-03-07 11:46 ` [PATCH] mmc: block: fix ABI regression of mmc_blk_ioctl Seshagiri Holi
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=56DD2AE9.7000708@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=jonathanh@nvidia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@kernel-upstream.org \
--cc=sholi@nvidia.com \
--cc=ulf.hansson@linaro.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