[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJ3WMUDS0svkoviLx_OOQFdjofMt3PwHdeLiouFbDVShw@mail.gmail.com>
Date: Wed, 18 Jan 2012 14:47:57 -0800
From: Kees Cook <keescook@...omium.org>
To: Seiji Aguchi <seiji.aguchi@....com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Tony Luck <tony.luck@...el.com>,
Marco Stornelli <marco.stornelli@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <greg@...ah.com>,
Randy Dunlap <rdunlap@...otime.net>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] ramoops: use pstore interface
On Wed, Jan 18, 2012 at 2:40 PM, Seiji Aguchi <seiji.aguchi@....com> wrote:
>>>> static int __exit ramoops_remove(struct platform_device *pdev)
>>>> {
>>>> +#if 0
>>>> + /* TODO(kees): We cannot unload ramoops since pstore doesn't support
>>>> + * unregistering yet.
>>>> + */
>>>
>>> Well that sucks. Is pstore getting fixed?
>>
>>Tony, any plans for changing this? I'm ready when it does! :)
>
> I have an question about this.
>
> Are there any specific usecases you need to unload ramoops?
For me, it would be useful during development. Beyond that, not that I can see.
-Kees
--
Kees Cook
ChromeOS Security
--
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/
Powered by blists - more mailing lists