linux-kernel - Re: [RFC] arch generic way to trigger unknown NMIs

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: <20101007072641.GE5010@basil.fritz.box>
Date:	Thu, 7 Oct 2010 09:26:41 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Don Zickus <dzickus@...hat.com>
Cc:	mingo@...e.hu, fweisbec@...il.com, andi@...stfloor.org,
	robert.richter@....com, gorcunov@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] arch generic way to trigger unknown NMIs


Having a regression test for this is good, but it would 
be also good if it wasn't a private one but in some public
git repository.

>  static struct jprobe lkdtm;
> @@ -340,6 +343,9 @@ static void lkdtm_do_action(enum ctype which)
>  		set_current_state(TASK_UNINTERRUPTIBLE);
>  		schedule();
>  		break;
> +	case NMI:
> +		apic->send_IPI_allbutself(NMI_VECTOR);
> +		break;
>  	case NONE:
>  	default:
>  		break;
> 
> Anyone have any thoughts?  Maybe there is an easier way?

Do you really want the NMI on all CPUs - 1? Normally it's directed to
a single one.

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