linux-kernel - Re: "x86: allocate space within a region top-down" causes bar0 access issue

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 for Android: free password hash cracker in your pocket

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

Message-Id: <201012171316.12761.bjorn.helgaas@hp.com>
Date:	Fri, 17 Dec 2010 13:16:12 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Jon Mason <jon.mason@...r.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Ramkrishna Vepa <ramkrishna.vepa@...r.com>
Subject: Re: "x86: allocate space within a region top-down" causes bar0 access issue

On Friday, December 17, 2010 12:44:58 pm Jon Mason wrote:
> The following patch is causing problem with the vxge driver/adapter on
> HP x86-64 systems. Reads to bar0 to return 0xffffffffffffffff instead
> of their intended value.  This prevents the vxge module from loading
> by failing sanity checks in the driver for certain values in bar0.  We
> are not seeing any issues with this patch on non-HP systems in our
> lab.
> 
> Can this patch be removed from 2.6.37 until a better solution can be
> found?

There were several issues related to that patch, and it's about to
be reverted.  I am curious about the failure you're seeing, though,
and I'd like to understand the cause and make sure it's one of the
issues I've already investigated.

Can you send me the complete dmesg log of a failing boot?

Thanks,
  Bjorn
--
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/