litmus-rt.git, branch v2.6.17-rc3 The LITMUS^RT kernel. Linux v2.6.17-rc3 2006-04-27T02:19:25+00:00 Linus Torvalds torvalds@g5.osdl.org 2006-04-27T02:19:25+00:00 2be4d50295e2b6f62c07b614e1b103e280dddb84 






Merge master.kernel.org:/home/rmk/linux-2.6-mmc
2006-04-26T22:45:27+00:00

Linus Torvalds
torvalds@g5.osdl.org

2006-04-26T22:45:27+00:00

a82642fa190029a438c0d09edb0e5463a0fe9e1e

* master.kernel.org:/home/rmk/linux-2.6-mmc:
  [MMC] pxamci: fix data timeout calculation





* master.kernel.org:/home/rmk/linux-2.6-mmc:
  [MMC] pxamci: fix data timeout calculation







Merge master.kernel.org:/home/rmk/linux-2.6-arm
2006-04-26T22:45:02+00:00

Linus Torvalds
torvalds@g5.osdl.org

2006-04-26T22:45:02+00:00

58f8236bed448273cd7f9ae02c09467853303484

* master.kernel.org:/home/rmk/linux-2.6-arm:
  [ARM] nommu: trivial fixups for head-nommu.S and the Makefile
  [ARM] vfp: fix leak of VFP_NAN_FLAG into FPSCR
  [ARM] 3484/1: Correct AEABI CFLAGS for correct enum handling





* master.kernel.org:/home/rmk/linux-2.6-arm:
  [ARM] nommu: trivial fixups for head-nommu.S and the Makefile
  [ARM] vfp: fix leak of VFP_NAN_FLAG into FPSCR
  [ARM] 3484/1: Correct AEABI CFLAGS for correct enum handling







Merge nommu tree
2006-04-26T20:18:45+00:00

Russell King
rmk@dyn-67.arm.linux.org.uk

2006-04-26T20:18:45+00:00

f13d241bc300802a2576dc3e2dfb51492a9a88b4












[PATCH] Remove __devinit and __cpuinit from notifier_call definitions
2006-04-26T15:30:03+00:00

Chandra Seetharaman
sekharan@us.ibm.com

2006-04-25T02:35:21+00:00

83d722f7e198b034699b1500d98729beff930efd

Few of the notifier_chain_register() callers use __init in the definition
of notifier_call.  It is incorrect as the function definition should be
available after the initializations (they do not unregister them during
initializations).

This patch fixes all such usages to _not_ have the notifier_call __init
section.

Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>





Few of the notifier_chain_register() callers use __init in the definition
of notifier_call.  It is incorrect as the function definition should be
available after the initializations (they do not unregister them during
initializations).

This patch fixes all such usages to _not_ have the notifier_call __init
section.

Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>







[PATCH] Remove __devinitdata from notifier block definitions
2006-04-26T15:27:50+00:00

Chandra Seetharaman
sekharan@us.ibm.com

2006-04-25T02:35:15+00:00

649bbaa484bcdce94f40a1b97a6a2ded0549e8a2

Few of the notifier_chain_register() callers use __devinitdata in the
definition of notifier_block data structure.  It is incorrect as the
data structure should be available after the initializations (they do
not unregister them during initializations).

This was leading to an oops when notifier_chain_register() call is
invoked for those callback chains after initialization.

This patch fixes all such usages to _not_ have the notifier_block data
structure in the init data section.

Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>





Few of the notifier_chain_register() callers use __devinitdata in the
definition of notifier_block data structure.  It is incorrect as the
data structure should be available after the initializations (they do
not unregister them during initializations).

This was leading to an oops when notifier_chain_register() call is
invoked for those callback chains after initialization.

This patch fixes all such usages to _not_ have the notifier_block data
structure in the init data section.

Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>







[PATCH] LSM: add missing hook to do_compat_readv_writev()
2006-04-26T14:52:21+00:00

James Morris
jmorris@namei.org

2006-04-26T06:45:03+00:00

e7edf9cdeddc0cff125e8e658216efb2ff2b2219

This patch addresses a flaw in LSM, where there is no mediation of readv()
and writev() in for 32-bit compatible apps using a 64-bit kernel.

This bug was discovered and fixed initially in the native readv/writev
code [1], but was not fixed in the compat code.  Thanks to Al for spotting
this one.

  [1] http://lwn.net/Articles/154282/

Signed-off-by: James Morris <jmorris@namei.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>





This patch addresses a flaw in LSM, where there is no mediation of readv()
and writev() in for 32-bit compatible apps using a 64-bit kernel.

This bug was discovered and fixed initially in the native readv/writev
code [1], but was not fixed in the compat code.  Thanks to Al for spotting
this one.

  [1] http://lwn.net/Articles/154282/

Signed-off-by: James Morris <jmorris@namei.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>







[PATCH] protect ext3 ioctl modifying append_only, immutable, etc. with i_mutex
2006-04-26T14:52:21+00:00

Al Viro
viro@ftp.linux.org.uk

2006-04-26T06:32:40+00:00

a090d9132c1e53e3517111123680c15afb25c0a4

All modifications of ->i_flags in inodes that might be visible to
somebody else must be under ->i_mutex.  That patch fixes ext3 ioctl()
setting S_APPEND and friends.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>





All modifications of ->i_flags in inodes that might be visible to
somebody else must be under ->i_mutex.  That patch fixes ext3 ioctl()
setting S_APPEND and friends.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>







[PATCH] fix mips sys32_p{read,write}
2006-04-26T14:52:21+00:00

Al Viro
viro@ftp.linux.org.uk

2006-04-26T06:28:09+00:00

6ad0013b316367671ef316cff91ab2d912e309c9

Switched to use of sys_pread64()/sys_pwrite64() rather than keep duplicating
their guts; among the little things that had been missing there were such as
	ret = security_file_permission (file, MAY_READ);
Gotta love the LSM robustness, right?

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>





Switched to use of sys_pread64()/sys_pwrite64() rather than keep duplicating
their guts; among the little things that had been missing there were such as
	ret = security_file_permission (file, MAY_READ);
Gotta love the LSM robustness, right?

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>







[PATCH] forgotten ->b_data in memcpy() call in ext3/resize.c (oopsable)
2006-04-26T14:52:21+00:00

Al Viro
viro@ftp.linux.org.uk

2006-04-26T06:26:09+00:00

de0bb97aff6743f71abb8ec581238e2bdae9cdd1

sbi->s_group_desc is an array of pointers to buffer_head.  memcpy() of
buffer size from address of buffer_head is a bad idea - it will generate
junk in any case, may oops if buffer_head is close to the end of slab
page and next page is not mapped and isn't what was intended there.
IOW, ->b_data is missing in that call.  Fortunately, result doesn't go
into the primary on-disk data structures, so only backup ones get crap
written to them; that had allowed this bug to remain unnoticed until
now.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>





sbi->s_group_desc is an array of pointers to buffer_head.  memcpy() of
buffer size from address of buffer_head is a bad idea - it will generate
junk in any case, may oops if buffer_head is close to the end of slab
page and next page is not mapped and isn't what was intended there.
IOW, ->b_data is missing in that call.  Fortunately, result doesn't go
into the primary on-disk data structures, so only backup ones get crap
written to them; that had allowed this bug to remain unnoticed until
now.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>