linux-kernel - Re: sun4v+DMA related boot crash on 4.13-git

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: <20170711.173436.720922946430226024.davem@davemloft.net>
Date:   Tue, 11 Jul 2017 17:34:36 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     tushar.n.dave@...cle.com
Cc:     mroos@...ux.ee, sparclinux@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: sun4v+DMA related boot crash on 4.13-git

From: Tushar Dave <tushar.n.dave@...cle.com>
Date: Tue, 11 Jul 2017 15:38:21 -0700

> 
> 
> On 07/11/2017 02:48 PM, Meelis Roos wrote:
>>>>>>> I tested yesterdayd 4.12+git on sparc64 to see if the sparc merge
>>>>>>> works
>>>>>>> fine, and on all of my sun4v machines (T1000, T2000, T5120) it crashed
>>>>>>> on boot with DMA-related stacktrace (below). Allt he machines are
>>>>>>> sun4v
>>>>>>> physical machines, not VM-s. Older sun4 machines do not exhibit this
>>>>>>> problem.
>>>>>>>
>>>>>>> Maybae DMA APi realted, maybe sparc64. Will try to bisect when I get
>>>>>>> time.
>>>>>> I see whats going on with panic. I will reproduce locally. Will get
>>>>>> back
>>>>>> soon.
>>>>> This patch should fix panic. Please give it a try.
>>>>
>>>> Yes, this patch fixes it. Thank you for fixing it quickly!
>>> Thanks for testing. Patch sent for sparc-next.
>> Why sparc-next - it should go into 4.13 since 4.13 would break all
>> niagara1 and niagara2 systems otherwise?This is sparc arch fix so I
>> used sparc tree(in this case for sparc-next).
> I am open to maintainers suggestions. Thanks.

If the bug is in Linus's tree the fix must target 'sparc' not
'sparc-next'.