linux-kernel - Re: [PATCH v2 2/5] cpu: CPU notifier error injection

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

Message-ID: <CAC5umyjqfQpaZVq3USA61idH3--koaeKy+1zkn109t6ecR8xgQ@mail.gmail.com>
Date:	Mon, 18 Jul 2011 18:42:53 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH v2 2/5] cpu: CPU notifier error injection

2011/7/18 Américo Wang <xiyou.wangcong@...il.com>:
> On Mon, Jul 18, 2011 at 9:16 AM, Akinobu Mita <akinobu.mita@...il.com> wrote:
> ...
>> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
>> index 72e2384..cf0b4b7 100644
>> --- a/Documentation/feature-removal-schedule.txt
>> +++ b/Documentation/feature-removal-schedule.txt
>> @@ -583,3 +583,11 @@ Why:       Superseded by the UVCIOC_CTRL_QUERY ioctl.
>>  Who:   Laurent Pinchart <laurent.pinchart@...asonboard.com>
>>
>>  ----------------------------
>> +
>> +What:  Support for CPU_NOTIFIER_ERROR_INJECT (cpu-notifier-error-inject.ko)
>> +When:  3.3
>> +Why:   Replaced with more generic debugfs interface in
>> +       /sys/kernel/debug/cpu-notifier-error-inject/
>> +Who:   Akinobu Mita <akinobu.mita@...il.com>
>
> Hi, Akinobu,
>
> I think it is okay to just remove it by this patchset, no need to defer it.

The only drawback is that new machanism has no way to specify notifier
priority and the priority is hard-coded to be -1.  So it can only inject
error at the tail of notifier chain.

My plan to fix that was the kernel parameters.  But it's not flexible
as it needs to reboot for changing the priority.

So I'm now considering keeping this kernel module style instead of
initializing in late_initcall().
--
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/