linux-kernel - Re: [PATCH 1/1] Speedfreq-SMI call clobbers ECX

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: <200803060951.12002.langer_mann@web.de>
Date:	Thu, 6 Mar 2008 09:51:10 +0100
From:	Stephan Diestelhorst <langer_mann@....de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	davej@...emonkey.org.uk, cpufreq@...ts.linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] Speedfreq-SMI call clobbers ECX

> On, March 5th 2008 16:35:20 Ingo Molnar wrote:
> > * Stephan Diestelhorst <langer_mann@....de> wrote:
> > > @@ -184,7 +184,7 @@ static void speedstep_set_state (unsigne
> > >  		__asm__ __volatile__(
> > >  			"movl $0, %%edi\n"
> > >  			"out %%al, (%%dx)\n"
> > > -			: "=b" (new_state), "=D" (result)
> > > +			: "=b" (new_state), "=D" (result), "=c" (ecx_clobber)
> > >
> > >  			: "a" (command), "b" (function), "c" (state), "d"
> > >  			: (smi_port), "S" (0)
> > >
> > >  			);
> >
> > stupid suggestion: why not do a pusha/popa around those
> > instructions, to make sure everything is restored? This isnt a
> > fastpath and being conservative about SMI side-effects cannot
> > hurt

Stephan Diestelhorst wrote:
> That sounds like a sane thing to do to me. Should I provide a
> 'patch'? Or leave that (and the decision about it) to the
> maintainer?

H. Peter Anvin wrote: 
> You can't pusha/popa if you expect a result.  You can, of course,
> push and pop individual registers.
>
> It's also kind of odd to do "movl $0,%%edi" instead of just setting
> EDI as an input.

Whoops, HPA is correct, of course. Manually pushing / popping the 
registers is ugly, how about a larger clobber-list? Let the compiler 
figure out what it wants to save/restore. Only thing to worry about 
is EBP then.

Again, should I provide these patches? This thing just annoyed me for 
a while as I have been patching it in my personal kernels for too 
long.

Regards,
  Stephan

PS: I'm not on LKML, please CC me at your discretion.
--
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/