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: <c9745450-a6d0-1944-a9af-ef9ce18fed12@collabora.com>
Date:   Wed, 13 May 2020 23:16:14 +0100
From:   Guillaume Tucker <guillaume.tucker@...labora.com>
To:     Joerg Roedel <jroedel@...e.de>
Cc:     Marek Szyprowski <m.szyprowski@...sung.com>,
        iommu@...ts.linux-foundation.org, Joerg Roedel <joro@...tes.org>,
        linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: next/master bisection: baseline.login on jetson-tk1

On 12/05/2020 16:16, Joerg Roedel wrote:
> Hi Guillaume,
> 
> thanks for the report!
> 
> On Tue, May 12, 2020 at 07:05:13AM +0100, Guillaume Tucker wrote:
>>> Summary:
>>>   Start:      4b20e7462caa6 Add linux-next specific files for 20200511
>>>   Plain log:  https://storage.kernelci.org/next/master/next-20200511/arm/tegra_defconfig/gcc-8/lab-collabora/baseline-tegra124-jetson-tk1.txt
>>>   HTML log:   https://storage.kernelci.org/next/master/next-20200511/arm/tegra_defconfig/gcc-8/lab-collabora/baseline-tegra124-jetson-tk1.html
>>>   Result:     3eeeb45c6d044 iommu: Remove add_device()/remove_device() code-paths
> 
> Okay, so it faults at
> 
> 	PC is at __iommu_probe_device+0x20/0x1b8
> 
> Can you translate that for me into a code-line, please? That would help
> finding the issue.

Sure, sorry for the delay.  I've built my own image as vmlinux is
not stored by kernelci and reproduced the problem:

  https://lava.collabora.co.uk/scheduler/job/2403076#L544

which this time gave me:

<4>[    2.540558] PC is at iommu_probe_device+0x1c/0x15c
<4>[    2.545606] LR is at of_iommu_configure+0x15c/0x1c4
<4>[    2.550736] pc : [<c092e0e4>]    lr : [<c0932c0c>]    psr: a0000013

which in turn brings us to:

(gdb) l *0xc092e0e4
0xc092e0e4 is in iommu_probe_device (drivers/iommu/iommu.c:232).
227		int ret;
228	
229		if (!dev_iommu_get(dev))
230			return -ENOMEM;
231	
232		if (!try_module_get(ops->owner)) {
233			ret = -EINVAL;
234			goto err_out;
235		}
236	


Hope this helps.

Guillaume

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ