From: Will Deacon <will@kernel.org>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org
Cc: Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, robin.murphy@arm.com,
linuxarm@huawei.com, kernel-team@android.com
Subject: Re: [PATCH] iommu: Check return of __iommu_attach_device()
Date: Mon, 23 Nov 2020 15:47:00 +0000 [thread overview]
Message-ID: <160614346318.875972.5810044376174592959.b4-ty@kernel.org> (raw)
In-Reply-To: <20201119165846.34180-1-shameerali.kolothum.thodi@huawei.com>
On Thu, 19 Nov 2020 16:58:46 +0000, Shameer Kolothum wrote:
> Currently iommu_create_device_direct_mappings() is called
> without checking the return of __iommu_attach_device(). This
> may result in failures in iommu driver if dev attach returns
> error.
Applied to arm64 (for-next/iommu/fixes), thanks!
[1/1] iommu: Check return of __iommu_attach_device()
https://git.kernel.org/arm64/c/77c38c8cf52e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org
Cc: Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, joro@8bytes.org, robin.murphy@arm.com,
linuxarm@huawei.com, kernel-team@android.com
Subject: Re: [PATCH] iommu: Check return of __iommu_attach_device()
Date: Mon, 23 Nov 2020 15:47:00 +0000 [thread overview]
Message-ID: <160614346318.875972.5810044376174592959.b4-ty@kernel.org> (raw)
In-Reply-To: <20201119165846.34180-1-shameerali.kolothum.thodi@huawei.com>
On Thu, 19 Nov 2020 16:58:46 +0000, Shameer Kolothum wrote:
> Currently iommu_create_device_direct_mappings() is called
> without checking the return of __iommu_attach_device(). This
> may result in failures in iommu driver if dev attach returns
> error.
Applied to arm64 (for-next/iommu/fixes), thanks!
[1/1] iommu: Check return of __iommu_attach_device()
https://git.kernel.org/arm64/c/77c38c8cf52e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-23 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 16:58 [PATCH] iommu: Check return of __iommu_attach_device() Shameer Kolothum
2020-11-19 16:58 ` Shameer Kolothum
2020-11-20 11:15 ` Will Deacon
2020-11-20 11:15 ` Will Deacon
2020-11-20 14:07 ` Robin Murphy
2020-11-20 14:07 ` Robin Murphy
2020-11-20 16:53 ` Shameerali Kolothum Thodi
2020-11-20 16:53 ` Shameerali Kolothum Thodi
2020-11-23 15:47 ` Will Deacon [this message]
2020-11-23 15:47 ` Will Deacon
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=160614346318.875972.5810044376174592959.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.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 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.