linux, branch v2.6.14.6

Linux 2.6.14.6

2006-01-08T02:15:24Z

[PATCH] Fix onboard video on SPARC Blade 100 for 2.6.{13,14,15}

2006-01-08T02:15:09Z

I have recently been switching from using 2.4.32 on my trusty old Sparc Blade 100 to using 2.6.15 . Some of the problems I ran into were distorted video when the console was active (missing first character, skipped dots) and when running X windows (colored snow, stripes, missing pixels). A quick examination of the 2.6 versus 2.4 source for the ATY driver revealed alot of changes. A closer look at the code/data for the 64GR/XL chip revealed two minor "typos" that the rewriter(s) of the code made. The first is a incorrect clock value (230 .vs. 235) and the second is a missing flag (M64F_SDRAM_MAGIC_PLL). Making both these changes seems to have fixed my problem. I tend to think the 235 value is the correct one, as there is a 29.4 Mhz clock crystal close to the video chip and 235.2 (29.4*8) is too close to 235 to make it a coincidence. The flag for M64F_SDRAM_MAGIC_PLL was dropped during the changes made by adaplas in file revision 1.72 on the old bitkeeper repository. The change relating to the clock rate has been there forever, at least in the 2.6 tree. I'm not sure where to look for the old 2.5 tree or if anyone cares when it happened. On SPARC Blades 100's, which use the ATY MACH64GR video chipset, the clock crystal frequency is 235.2 Mhz, not 230 Mhz. The chipset also requires the use of M64F_SDRAM_MAGIC_PLL in order to setup the PLL properly for the DRAM. Signed-off-by: Luis F. Ortiz Signed-off-by: David S. Miller Signed-off-by: Chris Wright

[PATCH] UFS: inode->i_sem is not released in error path

2006-01-08T02:15:09Z

Signed-off-by: Evgeniy Polyakov Cc: akpm: obviously correct, OK for -stable immediately. Signed-off-by: Andrew Morton Signed-off-by: Chris Wright Signed-off-by: Greg Kroah-Hartman

[PATCH] sysctl: make sure to terminate strings with a NUL

2006-01-08T02:15:08Z

This is a slightly more complete fix for the previous minimal sysctl string fix. It always terminates the returned string with a NUL, even if the full result wouldn't fit in the user-supplied buffer. The returned length is the full untruncated length, so that you can tell when truncation has occurred. Signed-off-by: Linus Torvalds [chrisw: inclusive of minimal fix so it's same as upstream] Signed-off-by: Chris Wright

[PATCH] Insanity avoidance in /proc (CVE-2005-4605)

2006-01-08T02:15:08Z

Insanity avoidance in /proc The old /proc interfaces were never updated to use loff_t, and are just generally broken. Now, we should be using the seq_file interface for all of the proc files, but converting the legacy functions is more work than most people care for and has little upside.. But at least we can make the non-LFS rules explicit, rather than just insanely wrapping the offset or something. Signed-off-by: Linus Torvalds Signed-off-by: Chris Wright Signed-off-by: Greg Kroah-Hartman

[PATCH] ieee80211_crypt_tkip depends on NET_RADIO

2006-01-08T02:15:07Z

*** Warning: ".wireless_send_event" [net/ieee80211/ieee80211_crypt_tkip.ko] This bug was also reported as kerenl Bugzilla #5551. Signed-off-by: Olaf Hering Signed-off-by: Adrian Bunk Signed-off-by: Chris Wright Signed-off-by: Greg Kroah-Hartman

[PATCH] drivers/net/sungem.c: gem_remove_one mustn't be __devexit

2006-01-08T02:15:07Z

gem_remove_one() is called from the __devinit gem_init_one(). Therefore, gem_remove_one() mustn't be __devexit. This patch was already included in 2.6.15-rc7. Signed-off-by: Adrian Bunk Signed-off-by: Chris Wright Signed-off-by: Greg Kroah-Hartman

Linux 2.6.14.5

2005-12-27T00:26:33Z

[PATCH] setting ACLs on readonly mounted NFS filesystems (CVE-2005-3623)

2005-12-27T00:08:59Z

We must check for MAY_SATTR before setting acls, which includes checking for read-only exports: the lower-level setxattr operation that eventually sets the acl cannot check export-level restrictions. Bug reported by Martin Walter . Signed-off-by: Andreas Gruenbacher Signed-off-by: Greg Kroah-Hartman

[PATCH] SCSI: fix transfer direction in scsi_lib and st

2005-12-27T00:08:58Z

SCSI: fix transfer direction in scsi_lib and st scsi_prep_fn and st_init_command could issue WRITE requests with zero buffer length. This may lead to kernel panic or oops with some SCSI low-level drivers. Derived from -rc patches from Jens Axboe and James Bottomley. Patch is reassembled for -stable from patches: [SCSI] fix panic when ejecting ieee1394 ipod [SCSI] Consolidate REQ_BLOCK_PC handling path (fix ipod panic) Depends on patch "SCSI: fix transfer direction in sd (kernel panic when ejecting iPod)". Also modifies the already correct sr_init_command to fully match the corresponding -rc patch. Signed-off-by: Stefan Richter Signed-off-by: Greg Kroah-Hartman