From: Wladislav Wiebe <wladislav.wiebe@nokia.com>
To: EXT Kees Cook <keescook@chromium.org>
Cc: "anton@enomsg.org" <anton@enomsg.org>,
"ccross@android.com" <ccross@android.com>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pstore: add support for 64 Bit address space
Date: Mon, 16 Nov 2015 12:38:52 +0100 [thread overview]
Message-ID: <5649C04C.8000406@nokia.com> (raw)
In-Reply-To: <CAGXu5jKo0EPi_YHap1i7P4R9+f-0xL8ot3aOKUGzKwm+PJii-g@mail.gmail.com>
Am 14.11.2015 um 00:46 schrieb EXT Kees Cook:
> On Fri, Nov 13, 2015 at 4:10 AM, Wiebe, Wladislav (Nokia - DE/Ulm)
> <wladislav.wiebe@nokia.com> wrote:
>> Some architectures has there reserved RAM in 64 Bit address space.
>> Therefore converting mem_address module parameter to ullong.
>>
>> Signed-off-by: Wladislav Wiebe <wladislav.wiebe@nokia.com>
>
> If this works correctly, I have no objection. :)
I can confirm, it works fine :-)
Thanks!
- Wladislav Wiebe
>
> Acked-by: Kees Cook <keescook@chromium.org>
>
> Thanks!
>
> -Kees
>
>> ---
>> fs/pstore/ram.c | 4 ++--
>> include/linux/pstore_ram.h | 2 +-
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
>> index 319c3a6..bd9812e 100644
>> --- a/fs/pstore/ram.c
>> +++ b/fs/pstore/ram.c
>> @@ -55,8 +55,8 @@ static ulong ramoops_pmsg_size = MIN_MEM_SIZE;
>> module_param_named(pmsg_size, ramoops_pmsg_size, ulong, 0400);
>> MODULE_PARM_DESC(pmsg_size, "size of user space message log");
>>
>> -static ulong mem_address;
>> -module_param(mem_address, ulong, 0400);
>> +static unsigned long long mem_address;
>> +module_param(mem_address, ullong, 0400);
>> MODULE_PARM_DESC(mem_address,
>> "start of reserved RAM used to store oops/panic logs");
>>
>> diff --git a/include/linux/pstore_ram.h b/include/linux/pstore_ram.h
>> index 9c9d6c1..4660aaa 100644
>> --- a/include/linux/pstore_ram.h
>> +++ b/include/linux/pstore_ram.h
>> @@ -76,7 +76,7 @@ ssize_t persistent_ram_ecc_string(struct persistent_ram_zone *prz,
>>
>> struct ramoops_platform_data {
>> unsigned long mem_size;
>> - unsigned long mem_address;
>> + phys_addr_t mem_address;
>> unsigned int mem_type;
>> unsigned long record_size;
>> unsigned long console_size;
>> --
>> 1.7.1
>>
>> Regards,
>> Wladislav Wiebe
>>
>>
>
>
>
--
Regards,
Wladislav Wiebe
next prev parent reply other threads:[~2015-11-16 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 12:10 [PATCH] pstore: add support for 64 Bit address space Wiebe, Wladislav (Nokia - DE/Ulm)
2015-11-13 23:46 ` Kees Cook
2015-11-16 11:38 ` Wladislav Wiebe [this message]
2016-01-27 9:34 ` Wladislav Wiebe
2016-01-27 15:45 ` Kees Cook
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=5649C04C.8000406@nokia.com \
--to=wladislav.wiebe@nokia.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.