Re: 3.13.?: Strange / dangerous fan policy...

2014-04-12 Thread Manuel Krause
On 2014-04-11 00:51, Manuel Krause wrote: On 2014-04-07 13:45, Rafael J. Wysocki wrote: On Monday, April 07, 2014 01:17:51 AM Manuel Krause wrote: On 2014-04-06 04:43, Guenter Roeck wrote: On 04/05/2014 07:37 PM, Manuel Krause wrote: On 2014-04-01 01:47, Guenter Roeck wrote: On 03/31/2014

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread Andy Lutomirski
On Sat, Apr 12, 2014 at 5:03 PM, H. Peter Anvin h...@zytor.com wrote: No self modifying code... The far jump must be in the indirect form anyhow. The CS:EIP must be accessible from user mode, but not necessarily from compatibility mode. So the trampoline (the jump) and data (CS:EIP) can live

Re: [PATCH] Route keyboard LEDs through the generic LEDs layer.

2014-04-12 Thread Dmitry Torokhov
On Fri, Apr 11, 2014 at 08:12:02AM +0200, Samuel Thibault wrote: Hello, I'm sorry this went out with a few mistakes. Samuel Thibault, le Wed 09 Apr 2014 01:33:06 +0200, a écrit : Dmitry Torokhov, le Tue 08 Apr 2014 01:39:40 -0700, a écrit : It is not about the VT, I am talking about

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread Andy Lutomirski
On Sat, Apr 12, 2014 at 6:25 PM, Andy Lutomirski l...@amacapital.net wrote: On Sat, Apr 12, 2014 at 5:03 PM, H. Peter Anvin h...@zytor.com wrote: A signal arriving while in the user space trampoline could seriously complicate life. Agreed. Maybe I don't agree. Have signals ever worked

Re: [PATCH] Route keyboard LEDs through the generic LEDs layer.

2014-04-12 Thread Dmitry Torokhov
On Sat, Apr 12, 2014 at 12:09:34PM +0200, Pavel Machek wrote: Hi! This permits to reassign keyboard LEDs to something else than keyboard leds state, by adding keyboard led and modifier triggers connected to a series of VT input LEDs, themselves connected to VT input

[PATCH RFC] blkcg: prepare blkcg knobs for default hierarchy

2014-04-12 Thread Tejun Heo
Hello, Unified hierarchy has finally been posted. http://thread.gmane.org/gmane.linux.kernel.containers/27601 It took a lot longer than I originally anticipated and over the course quite a few aspects of the initial design have changed, hopefully, for the better. One of the areas which has

Re: [GIT] kbuild misc changes for v3.15-rc1

2014-04-12 Thread Linus Torvalds
On Wed, Apr 9, 2014 at 8:59 AM, Michal Marek mma...@suse.cz wrote: here is the non-critical part of kbuild: Michal, please make your pull request script clearly say both git and pull somewhere. Your emails don't trigger my search criteria, so they end up not being visible in my list of pull

new module to check constant memory for corruption

2014-04-12 Thread Alexander . Kleinsorge
ramcheck kernel module new module to check constant memory for corruption detect corruption of constant kernel memory (text and data) periodically. runtime costs about 1..2 ms per sec (about 10 mb with 5 mb/ms), which is distributed over 8 (BLOCKS) time partitions (less than half ms per sec). in

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread Andi Kleen
Linus Torvalds torva...@linux-foundation.org writes: On Fri, Apr 11, 2014 at 11:27 AM, Brian Gerst brge...@gmail.com wrote: Is this bug really still present in modern CPUs? This change breaks running 16-bit apps in Wine. I have a few really old games I like to play on occasion, and I don't

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread Andi Kleen
H. Peter Anvin h...@zytor.com writes: But yes, we can make it configurable, but the default should almost certainly be off. Why? Either it works or it doesn't. If it works it doesn't make any sense to have a sysctl. -Andi -- a...@linux.intel.com -- Speaking for myself only -- To

Re: new module to check constant memory for corruption

2014-04-12 Thread Andi Kleen
alexander.kleinso...@gmx.de writes: ramcheck kernel module new module to check constant memory for corruption detect corruption of constant kernel memory (text and data) periodically. runtime costs about 1..2 ms per sec (about 10 mb with 5 mb/ms), which is distributed over 8 (BLOCKS) time

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread H. Peter Anvin
I would think any sensible application with 16-bit segments would be using sigaltstack. Does anyone know what Wine does? On April 12, 2014 6:29:11 PM PDT, Andy Lutomirski l...@amacapital.net wrote: On Sat, Apr 12, 2014 at 6:25 PM, Andy Lutomirski l...@amacapital.net wrote: On Sat, Apr 12, 2014

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread H. Peter Anvin
It leaks security sensitive information to userspace and corrupts the upper half of ESP because it lacks the equivalent of the espfix workaround. On April 12, 2014 7:56:48 PM PDT, Andi Kleen a...@firstfloor.org wrote: H. Peter Anvin h...@zytor.com writes: But yes, we can make it configurable,

Re: new module to check constant memory for corruption

2014-04-12 Thread Valdis . Kletnieks
On Sun, 13 Apr 2014 03:33:10 +0200, alexander.kleinso...@gmx.de said: printk(KERN_EMERG MODNAME error: const kernel memory is broken (%08lx != 0), please reboot!, g_SumLast); Make a list of all the things that can dynamically modify kernel text while it's running, starting with

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread Linus Torvalds
On Sat, Apr 12, 2014 at 7:56 PM, Andi Kleen a...@firstfloor.org wrote: Why? Either it works or it doesn't. If it works it doesn't make any sense to have a sysctl. BS. It works exactly like mmap() at NULL works. It is a potential security leak, because x86-64 screwed up the architecture

Re: [PATCH v4] fs: FAT: Add support for DOS 1.x formatted volumes

2014-04-12 Thread OGAWA Hirofumi
Conrad Meyer ceme...@uw.edu writes: Hi, Sorry for late reply. + + bd_sects = part_nr_sects_read(sb-s_bdev-bd_part); This would be better to use i_read_size(sb-s_bdev-bd_inode-i_size) + if (!fat_bpb_is_zero(b)) { + fat_msg(sb, KERN_ERR, %s; DOS 2.x BPB

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

2014-04-12 Thread H. Peter Anvin
On 04/11/2014 02:53 PM, Andy Lutomirski wrote: If you want a fully correct solution, you can use a fancier allocation policy that can fit quite a few cpus per 4G :) The more I think about this, I think this might actually be a reasonable option, *IF* someone is willing to deal with actually

Re: [PATCH v4 1/7] drivers: input: keyboard: st-keyscan: add keyscan driver

2014-04-12 Thread Dmitry Torokhov
Hi Gabriel, On Fri, Apr 11, 2014 at 05:07:30PM +0200, Gabriel FERNANDEZ wrote: This patch adds ST Keyscan driver to use the keypad hw a subset of ST boards provide. Specific board setup will be put in the given dt. Signed-off-by: Gabriel Fernandez gabriel.fernan...@linaro.org

Re: [RFC][PATCH] vfs: In mntput run deactivate_super on a shallow stack.

2014-04-12 Thread Al Viro
On Sat, Apr 12, 2014 at 03:15:39PM -0700, Eric W. Biederman wrote: Can you explain which scenario you are thinking about with respect to a failed modprobe? Completely made up example: static struct file_system_type foofs = { .mount = mount_foo, .kill_sb = kill_foo, }; static

Re: [RFC][PATCH] vfs: In mntput run deactivate_super on a shallow stack.

2014-04-12 Thread Al Viro
On Sun, Apr 13, 2014 at 06:39:56AM +0100, Al Viro wrote: type = get_fs_type(proc); ns = kmalloc(...); /* fill *ns */ mnt = kern_mount_data(type, p); s/p/ns/ ... if (error) { kern_unmount(mnt); kfree(p); ditto.

<    1   2   3