From: Greg KH <gregkh@linuxfoundation.org>
To: Olav Haugan <ohaugan@codeaurora.org>
Cc: ngupta@vflare.org, sjenning@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, minchan@kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success
Date: Mon, 11 Nov 2013 16:19:02 -0800 [thread overview]
Message-ID: <20131112001902.GA1043@kroah.com> (raw)
In-Reply-To: <1383875883-30597-1-git-send-email-ohaugan@codeaurora.org>
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
next prev parent reply other threads:[~2013-11-12 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 1:58 [PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success Olav Haugan
2013-11-08 16:26 ` Nitin Gupta
2013-11-12 0:19 ` Greg KH [this message]
2013-11-12 17:06 ` Olav Haugan
2013-11-19 23:26 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131112001902.GA1043@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=ohaugan@codeaurora.org \
--cc=sjenning@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).