linux-kernel - Re: [PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success

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:	Mon, 11 Nov 2013 16:19:02 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Olav Haugan <ohaugan@...eaurora.org>
Cc:	ngupta@...are.org, sjenning@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, minchan@...nel.org,
	linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success

On Thu, Nov 07, 2013 at 05:58:03PM -0800, Olav Haugan wrote:
> zsmalloc encodes a handle using the pfn and an object
> index. On hardware platforms with physical memory starting
> at 0x0 the pfn can be 0. This causes the encoded handle to be
> 0 and is incorrectly interpreted as an allocation failure.

Please list the known hardware platforms that have this issue, so that
people have a chance to know if this patch is relevant for them or not.

For example, should I include this in the stable releases because it
affects systems that are shipping?  Or is it just in "future" chips and
it doesn't need to go there or not?

Please make it easy for me to do this type of determination, I already
asked you this question before, why didn't you include the information
here as well (hint, that is why I asked you...)

greg k-h
--
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/