linux-kernel - Oops in sched_mc_power_savings

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

Date:	Thu, 24 Jul 2008 05:51:22 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Andi Kleen <andi@...stfloor.org>, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org
Subject: Oops in sched_mc_power_savings_store

I have no idea how you guys intended this to work, but here's the
debugging work I've done so far.

[   89.210171] Call Trace:
[   89.210182]  [<c011c0b3>] ? sched_mc_power_savings_store+0x0/0x4a
[   89.210198]  [<c02908c0>] ? sysdev_class_store+0x38/0x40
[   89.210213]  [<c01a0b51>] ? sysfs_write_file+0xb9/0xe4

sched_mc_power_savings_store isn't a class attribute, it's a plain
attribute.  So the prototypes are different.  This is why we try to load
from address 2 -- it's actually the length parameter.

I don't know how our typing system let this one through.  I don't know if
you want to fix this by adding an extra argument to the class_attribute
show and store methods.  I don't know if sched_mc_power_savings_store
was intended to be a class attribute or not.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/