linux-kernel - Re: [PATCH] pstore: pass reason to backend write callback

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] [day] [month] [year] [list]

Message-ID: <CAGXu5j+hxaoz4=vmcJfsjbma09QBmv3ErQG+CZkV1mFGi=K++w@mail.gmail.com>
Date:	Wed, 16 Nov 2011 09:55:07 -0800
From:	Kees Cook <keescook@...omium.org>
To:	Chen Gong <gong.chen@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, Tony Luck <tony.luck@...el.com>,
	Matthew Garrett <mjg@...hat.com>
Subject: Re: [PATCH] pstore: pass reason to backend write callback

On Tue, Nov 15, 2011 at 6:59 PM, Chen Gong <gong.chen@...ux.intel.com> wrote:
> 于 2011/11/15 7:29, Kees Cook 写道:
>> This allows a backend to filter on the dmesg reason as well as the pstore
>> reason. When ramoops is switched to pstore, this is needed since it has
>> no interest in storing non-crash dmesg details.
> We ever talked about it here: https://lkml.org/lkml/2011/9/20/468.
> Matthew's patch is good enough if pstore_write can be cleaned.

Ah, thanks for the URL. Yeah, it looks like it would be sane to just
remove pstore_write completely. I will send an updated patch.

Thanks!

-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/