From: Mark Salyzyn <salyzyn@android.com>
To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.kw@hitachi.com>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org,
Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>,
Seiji Aguchi <seiji.aguchi.tr@hitachi.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v4 2nd 1/4] ramoops: Add __ramoops_init_prz() as generic function
Date: Thu, 2 Feb 2017 14:13:09 -0800 [thread overview]
Message-ID: <8035b840-8f84-35c4-60e7-5d1c4c8e9b5f@android.com> (raw)
In-Reply-To: <1485827915-9620-2-git-send-email-nobuhiro.iwamatsu.kw@hitachi.com>
On 01/30/2017 05:58 PM, Nobuhiro Iwamatsu wrote:
> +
> + if (zap && *paddr + sz - cxt->phys_addr > cxt->size) {
> + dev_err(dev, "no room for %s mem region (0x%zx@0x%llx) in (0x%lx@0x%llx)\n",
> + name, sz, (unsigned long long)*paddr,
> + cxt->size, (unsigned long long)cxt->phys_addr);
> + return -ENOMEM;
> + }
> +
Why not allow this limit check for ramoops_init_prsz call?
-- Mark
next prev parent reply other threads:[~2017-02-02 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 1:58 [PATCH v4 2nd 0/4] pstore: ramoops: support multiple pmsg instances Nobuhiro Iwamatsu
2017-01-31 1:58 ` [PATCH v4 2nd 1/4] ramoops: Add __ramoops_init_prz() as generic function Nobuhiro Iwamatsu
2017-02-02 22:13 ` Mark Salyzyn [this message]
2017-02-07 8:51 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2017-02-07 16:05 ` Mark Salyzyn
2017-01-31 1:58 ` [PATCH v4 2nd 2/4] pstore: support multiple pmsg instances Nobuhiro Iwamatsu
2017-02-01 20:28 ` Kees Cook
2017-02-07 8:44 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2017-02-02 22:17 ` Mark Salyzyn
2017-02-07 8:47 ` 岩松信洋 / IWAMATSU，NOBUHIRO
2017-01-31 1:58 ` [PATCH v4 2nd 3/4] ramoops: " Nobuhiro Iwamatsu
2017-01-31 1:58 ` [PATCH v4 2nd 4/4] selftests/pstore: add testcases for " Nobuhiro Iwamatsu
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=8035b840-8f84-35c4-60e7-5d1c4c8e9b5f@android.com \
--to=salyzyn@android.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=hiraku.toyooka.gu@hitachi.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nobuhiro.iwamatsu.kw@hitachi.com \
--cc=seiji.aguchi.tr@hitachi.com \
--cc=shuahkh@osg.samsung.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®