linux-kernel - Re: [PATCH] iommu-common: Do not try to deref a null iommu->lazy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150917142644.a7a3c272be10280028c5ad3a@linux-foundation.org>
Date:	Thu, 17 Sep 2015 14:26:44 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Sowmini Varadhan <sowmini.varadhan@...cle.com>
Cc:	linux-kernel@...r.kernel.org, benh@...nel.crashing.org,
	linux@...ck-us.net, davem@...emloft.net
Subject: Re: [PATCH] iommu-common: Do not try to deref a null
 iommu->lazy_flush() pointer when n < pool->hint

On Wed, 16 Sep 2015 21:50:43 -0400 Sowmini Varadhan <sowmini.varadhan@...cle.com> wrote:

> The check for invoking iommu->lazy_flush() from iommu_tbl_range_alloc()
> has to be refactored so that we only call ->lazy_flush() if it is non-null.

Patch looks good.

But I don't know which kernel versions need the fix.  So, when fixing a
bug please always describe the end-user visible effects of that bug. 
Under what circumstances did your kernel crash?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/