linux-kernel - Re: External USB disks not recognized with v6.1.8 when using Xen

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]

Date:   Wed, 1 Feb 2023 10:37:41 +0100 (CET)
From:   Christian Kujau <lists@...dbynature.de>
To:     Juergen Gross <jgross@...e.com>
cc:     Michael Kelley <mikelley@...rosoft.com>,
        Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org,
        Greg KH <gregkh@...uxfoundation.org>,
        Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: External USB disks not recognized with v6.1.8 when using Xen

On Wed, 1 Feb 2023, Juergen Gross wrote:
> I have problems understanding the behavior.
> 
> Assuming the cited error messages
> 
>   ioremap error for 0xf2520000-0xf2530000, requested 0x2, got 0x0

Yes, that and the XHCI_HCD error are only present in dmesg when it's 
running as the Xen Dom0:

+ioremap error for 0xf2520000-0xf2530000, requested 0x2, got 0x0
+xhci_hcd 0000:00:14.0: init 0000:00:14.0 fail, -14
+xhci_hcd: probe of 0000:00:14.0 failed with error -14

I don't know if it's related, but the issue is really, really gone when 
that commit is reverted. And "no external disks when running in Dom0 mode" 
(i.e. started by the Xen HV) is kind of a big issue, I'm afraid.

But I'm at a loss on the technicalities of that commit, sorry.

Christian.

> are related to the issue, this would mean that the ioremap() caller
> requested _PAGE_CACHE_MODE_UC_MINUS (type 0x2) and got _PAGE_CACHE_MODE_WB
> (type 0x0).
> 
> The patch you have reverted is modifying behavior only if the _input_ type
> is _PAGE_CACHE_MODE_WB.
> 
> Anyone having an idea what could be wrong here?
-- 
BOFH excuse #339:

manager in the cable duct