linux.git/drivers/char/vt.c, branch v2.6.32

tty: vt: use printk_once

2009-09-19T20:13:35+00:00

Signed-off-by: Marcin Slusarz 
Signed-off-by: Greg Kroah-Hartman

tty: handle VT specific compat ioctls in vt driver

2009-09-19T20:13:35+00:00

The VT specific compat_ioctl handlers are the only ones
in common code that require the BKL. Moving them into
the vt driver lets us remove the BKL from the other handlers
and cleans up the code.

Signed-off-by: Arnd Bergmann 
Signed-off-by: Greg Kroah-Hartman

vt: add an event interface

2009-09-19T20:13:24+00:00

This is needed and requested in various forms for ConsoleKit, screenblank
handling and the like so do the job with a single interface. Also build the
interface so that unlike VT_WAITACTIVE and friends it won't miss events.

FIXME: Should this be a waitactive ioctl or a new device file you can poll
and read events from. We need the code anyway to fix up the existing broken
wait for console switch logic but the ConsoleKit people would prefer the
new device to the ioctl we have here

Signed-off-by: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

tty: includecheck fix: drivers/char, vt.c

2009-09-19T20:13:11+00:00

fix the following 'make includecheck' warning:

  drivers/char/vt.c: linux/device.h is included more than once.

Signed-off-by: Jaswinder Singh Rajput 
Signed-off-by: Greg Kroah-Hartman

sparc: Kill PROM console driver.

2009-09-16T00:04:38+00:00

Many years ago when this driver was written, it had a use, but these
days it's nothing but trouble and distributions should not enable it
in any situation.

Pretty much every console device a sparc machine could see has a
bonafide real driver, making the PROM console hack unnecessary.

If any new device shows up, we should write a driver instead of
depending upon this crutch to save us.  We've been able to take care
of this even when no chip documentation exists (sunxvr500, sunxvr2500)
so there are no excuses.

Signed-off-by: David S. Miller

vt: drop bootmem/slab memory distinction

2009-07-16T16:19:16+00:00

Bootmem is not used for the vt screen buffer anymore as slab is now
available at the time the console is initialized.

Get rid of the now superfluous distinction between slab and bootmem,
it's always slab.

This also fixes a kmalloc leak which Catalin described thusly:

Commit a5f4f52e ("vt: use kzalloc() instead of the bootmem allocator")
replaced the alloc_bootmem() with kzalloc() but didn't set vc_kmalloced to
1 and the memory block is later leaked.  The corresponding kmemleak trace:

unreferenced object 0xdf828000 (size 8192):
  comm "swapper", pid 0, jiffies 4294937296
  backtrace:
    [] __save_stack_trace+0x17/0x1c
    [] log_early+0x55/0x84
    [] kmemleak_alloc+0x33/0x3c
    [] __kmalloc+0xd7/0xe4
    [] con_init+0xbf/0x1b8
    [] console_init+0x11/0x20
    [] start_kernel+0x137/0x1e4

Signed-off-by: Johannes Weiner 
Reviewed-by: Pekka Enberg 
Tested-by: Catalin Marinas 
Signed-off-by: Andrew Morton 
Signed-off-by: Alan Cox 
Signed-off-by: Linus Torvalds

headers: smp_lock.h redux

2009-07-12T19:22:34+00:00

* Remove smp_lock.h from files which don't need it (including some headers!)
* Add smp_lock.h to files which do need it
* Make smp_lock.h include conditional in hardirq.h
  It's needed only for one kernel_locked() usage which is under CONFIG_PREEMPT

  This will make hardirq.h inclusion cheaper for every PREEMPT=n config
  (which includes allmodconfig/allyesconfig, BTW)

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Linus Torvalds

console: make blank timeout value a boot option

2009-06-17T02:47:52+00:00

The console blank timer is currently hardcoded to 10*60 seconds which
might be annoying on systems with no input devices attached to wake up the
console again.  Especially during development, disabling the screen saver
can be handy - for example when debugging the root fs mount mechanism or
other scenarios where no userspace program could be started to do that at
runtime from userspace.

This patch defines a core_param for the variable in charge which allows
users to entirely disable the blank feature at boot time by setting it 0.
The value can still be overwritten at runtime using the standard ioctl
call - this just allows to conditionally change the default.

Signed-off-by: Daniel Mack 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kmemleak: Remove the kmemleak.h include in drivers/char/vt.c

2009-06-12T08:30:10+00:00

This file is no longer annotated for false positives but the kmemleak.h
include was still present.

Signed-off-by: Catalin Marinas 
Acked-by: Alan Cox

Merge branch 'for-linus' of git://linux-arm.org/linux-2.6

2009-06-11T21:15:57+00:00

* 'for-linus' of git://linux-arm.org/linux-2.6:
  kmemleak: Add the corresponding MAINTAINERS entry
  kmemleak: Simple testing module for kmemleak
  kmemleak: Enable the building of the memory leak detector
  kmemleak: Remove some of the kmemleak false positives
  kmemleak: Add modules support
  kmemleak: Add kmemleak_alloc callback from alloc_large_system_hash
  kmemleak: Add the vmalloc memory allocation/freeing hooks
  kmemleak: Add the slub memory allocation/freeing hooks
  kmemleak: Add the slob memory allocation/freeing hooks
  kmemleak: Add the slab memory allocation/freeing hooks
  kmemleak: Add documentation on the memory leak detector
  kmemleak: Add the base support

Manual conflict resolution (with the slab/earlyboot changes) in:
	drivers/char/vt.c
	init/main.c
	mm/slab.c