linux-kernel - Re: AMD-IOMMU and problem with _

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: <5602F7BF.4020009@ahsoftware.de>
Date:	Wed, 23 Sep 2015 21:04:31 +0200
From:	Alexander Holler <holler@...oftware.de>
To:	Joerg Roedel <joro@...tes.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: AMD-IOMMU and problem with __init(data)?

Am 23.09.2015 um 17:50 schrieb Alexander Holler:
> Am 23.09.2015 um 13:43 schrieb Joerg Roedel:
>>> If it's necessary, I could try put together a small patch which
>>> kills a system (reproducible here).
>>
>> That would help too, please also send me your .config and I'll try to
>> reproduce the issue here.
>
> Will do. Later.

Done. Patch(es) and config attached. Note, while reducing the patch, 
I've noted that when I change

struct _annotated_initcall {
	initcall_t initcall;
	unsigned driver_id;
	unsigned *dependencies;
	struct device_driver *driver;
};

to

struct _annotated_initcall {
	initcall_t initcall;
	unsigned driver_id;
};

it does not crash. That's what the second patch does. So in order to 
crash a system, just use patch 0001.

Regards,

Alexander Holler

View attachment "0001-CRASH-on-AMD-with-CONFIG_AMD_IOMMU.patch" of type "text/x-patch" (2313 bytes)

View attachment "0002-NO-crash.patch" of type "text/x-patch" (632 bytes)

Download attachment "crash_amd_iommu.config.bz2" of type "application/x-bzip" (23799 bytes)