]> git.karo-electronics.de Git - karo-tx-linux.git/commit
Revert "tty: fix a little bug in scrup, vt.c"
authorLinus Torvalds <torvalds@linux-foundation.org>
Mon, 7 Jun 2010 03:44:04 +0000 (20:44 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Mon, 7 Jun 2010 03:44:04 +0000 (20:44 -0700)
commit386f40c86d6c8d5b717ef20620af1a750d0dacb4
tree6cd79f6dba461948b2cbaa0ca1e725a36ffd1d63
parente44a21b7268a022c7749f521c06214145bd161e4
Revert "tty: fix a little bug in scrup, vt.c"

This reverts commit 962400e8fd29981a7b166e463dd143b6ac6a3e76, which was
entirely bogus.

The code used to multiply the character offset by "vc->vc_cols", and
that's actually correct, because 'd' itself is an 'unsigned short'.  So
the pointer arithmetic already takes the size of a VGA character into
account.  Changing it to use vc_size_row (which is just "vc_cols"
shifted up to take the size of the character into account) ends up
multiplying with the VGA character size twice.

This got reported as bugs for various other subsystems, because what it
actually results in is writing the 16-bit vc_video_erase_char pattern
(usually 0x0720: 0x07 is the default attribute, 0x20 is ASCII space)
into some random other allocation.

So Markus ended up reporting this as a ext4 bug, while to Torsten Kaiser
it looked like a problem with KMS or libata.  Jeff Chua saw it in
different places.

And finally - Justin Mattock had slab poisoning enabled, and saw it as a
slab poison overwritten.  And bisected and reverted this to verify the
buggy commit.

Reported-by: Markus Trippelsdorf <markus@trippelsdorf.de>
Reported-by: Torsten Kaiser <just.for.lkml@googlemail.com>
Reported-by: Jeff Chua <jeff.chua.linux@gmail.com>
Reported-by: Justin P. Mattock <justinmattock@gmail.com>
Reported-bisected-and-tested-by: Justin P. Mattock <justinmattock@gmail.com>
Acked-by: Dave Airlie <airlied@redhat.com>
Cc: Frank Pan <frankpzh@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
drivers/char/vt.c