All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Jacob Pan <jacob.pan.linux@gmail.com>,
	kernel-janitors@vger.kernel.org,
	iommu@lists.linux-foundation.org
Subject: Re: [PATCH] iommu: fix a check in iommu_check_bind_data()
Date: Tue, 03 Nov 2020 13:56:25 +0000	[thread overview]
Message-ID: <20201103135625.GK22888@8bytes.org> (raw)
In-Reply-To: <20201103101623.GA1127762@mwanda>

On Tue, Nov 03, 2020 at 01:16:23PM +0300, Dan Carpenter wrote:
> The "data->flags" variable is a u64 so if one of the high 32 bits is
> set the original code will allow it, but it should be rejected.  The
> fix is to declare "mask" as a u64 instead of a u32.
> 
> Fixes: d90573812eea ("iommu/uapi: Handle data and argsz filled by users")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
>  drivers/iommu/iommu.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied for v5.10, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Jacob Pan <jacob.pan.linux@gmail.com>,
	kernel-janitors@vger.kernel.org,
	iommu@lists.linux-foundation.org
Subject: Re: [PATCH] iommu: fix a check in iommu_check_bind_data()
Date: Tue, 3 Nov 2020 14:56:25 +0100	[thread overview]
Message-ID: <20201103135625.GK22888@8bytes.org> (raw)
In-Reply-To: <20201103101623.GA1127762@mwanda>

On Tue, Nov 03, 2020 at 01:16:23PM +0300, Dan Carpenter wrote:
> The "data->flags" variable is a u64 so if one of the high 32 bits is
> set the original code will allow it, but it should be rejected.  The
> fix is to declare "mask" as a u64 instead of a u32.
> 
> Fixes: d90573812eea ("iommu/uapi: Handle data and argsz filled by users")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
>  drivers/iommu/iommu.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied for v5.10, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-11-03 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 10:16 [PATCH] iommu: fix a check in iommu_check_bind_data() Dan Carpenter
2020-11-03 10:16 ` Dan Carpenter
2020-11-03 13:56 ` Joerg Roedel [this message]
2020-11-03 13:56   ` Joerg Roedel

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=20201103135625.GK22888@8bytes.org \
    --to=joro@8bytes.org \
    --cc=dan.carpenter@oracle.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.pan.linux@gmail.com \
    --cc=jean-philippe@linaro.org \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.