)]}' { "log": [ { "commit": "2fd4ef85e0db9ed75c98e13953257a967ea55e03", "tree": "119dfe9f88a832f3db6ff66e631112626f268f18", "parents": [ "fb085cf1d4294824571815d487daccc0609543f0" ], "author": { "name": "Hugh Dickins", "email": "hugh@veritas.com", "time": "Wed Sep 14 06:13:02 2005 +0100" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Wed Sep 14 11:18:13 2005 -0700" }, "message": "[PATCH] error path in setup_arg_pages() misses vm_unacct_memory()\n\nPavel Emelianov and Kirill Korotaev observe that fs and arch users of\nsecurity_vm_enough_memory tend to forget to vm_unacct_memory when a\nfailure occurs further down (typically in setup_arg_pages variants).\n\nThese are all users of insert_vm_struct, and that reservation will only\nbe unaccounted on exit if the vma is marked VM_ACCOUNT: which in some\ncases it is (hidden inside VM_STACK_FLAGS) and in some cases it isn\u0027t.\n\nSo x86_64 32-bit and ppc64 vDSO ELFs have been leaking memory into\nCommitted_AS each time they\u0027re run. But don\u0027t add VM_ACCOUNT to them,\nit\u0027s inappropriate to reserve against the very unlikely case that gdb\nbe used to COW a vDSO page - we ought to do something about that in\ndo_wp_page, but there are yet other inconsistencies to be resolved.\n\nThe safe and economical way to fix this is to let insert_vm_struct do\nthe security_vm_enough_memory check when it finds VM_ACCOUNT is set.\n\nAnd the MIPS irix_brk has been calling security_vm_enough_memory before\ncalling do_brk which repeats it, doubly accounting and so also leaking.\nRemove that, and all the fs and arch calls to security_vm_enough_memory:\ngive it a less misleading name later on.\n\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-Off-By: Kirill Korotaev \u003cdev@sw.ru\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "fb085cf1d4294824571815d487daccc0609543f0", "tree": "e3a704026e65bf6fea0c7747f0fb75a506f54127", "parents": [ "32a3658533c6f4c6bf370dd730213e802464ef9b" ], "author": { "name": "Alexander Nyberg", "email": "alexn@telia.com", "time": "Wed Sep 14 18:54:06 2005 +0200" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Wed Sep 14 10:26:34 2005 -0700" }, "message": "[PATCH] Fix fs/exec.c:788 (de_thread()) BUG_ON\n\nIt turns out that the BUG_ON() in fs/exec.c: de_thread() is unreliable\nand can trigger due to the test itself being racy.\n\nde_thread() does\n \twhile (atomic_read(\u0026sig-\u003ecount) \u003e count) {\n\t}\n\t.....\n\t.....\n\tBUG_ON(!thread_group_empty(current));\n\nbut release_task does\n\twrite_lock_irq(\u0026tasklist_lock)\n\t__exit_signal\n\t\t(this is where atomic_dec(\u0026sig-\u003ecount) is run)\n\t__exit_sighand\n\t__unhash_process\n\t\ttakes write lock on tasklist_lock\n\t\tremove itself out of PIDTYPE_TGID list\n\twrite_unlock_irq(\u0026tasklist_lock)\n\nso there\u0027s a clear (although small) window between the\natomic_dec(\u0026sig-\u003ecount) and the actual PIDTYPE_TGID unhashing of the\nthread.\n\nAnd actually there is no need for all threads to have exited at this\npoint, so we simply kill the BUG_ON.\n\nBig thanks to Marc Lehmann who provided the test-case.\n\nFixes Bug 5170 (http://bugme.osdl.org/show_bug.cgi?id\u003d5170)\n\nSigned-off-by: Alexander Nyberg \u003calexn@telia.com\u003e\nCc: Roland McGrath \u003croland@redhat.com\u003e\nCc: Andrew Morton \u003cakpm@osdl.org\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nAcked-by: Andi Kleen \u003cak@suse.de\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "badf16621c1f9d1ac753be056fce11b43d6e0be5", "tree": "3fdf833fdf2e3d3a439090743539680449ec3428", "parents": [ "c0dfb2905126e9e94edebbce8d3e05001301f52d" ], "author": { "name": "Dipankar Sarma", "email": "dipankar@in.ibm.com", "time": "Fri Sep 09 13:04:10 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Sep 09 13:57:55 2005 -0700" }, "message": "[PATCH] files: break up files struct\n\nIn order for the RCU to work, the file table array, sets and their sizes must\nbe updated atomically. Instead of ensuring this through too many memory\nbarriers, we put the arrays and their sizes in a separate structure. This\npatch takes the first step of putting the file table elements in a separate\nstructure fdtable that is embedded withing files_struct. It also changes all\nthe users to refer to the file table using files_fdtable() macro. Subsequent\napplciation of RCU becomes easier after this.\n\nSigned-off-by: Dipankar Sarma \u003cdipankar@in.ibm.com\u003e\nSigned-Off-By: David Howells \u003cdhowells@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "5323125031799a7fd8602ce150c3902aedfdcba6", "tree": "43281ea094cba176e88ba50561e2a04aa8beed8c", "parents": [ "5c888d531823f8ce2853fb717ebefbcca9acdcd0" ], "author": { "name": "Roland McGrath", "email": "roland@redhat.com", "time": "Tue Jul 12 13:58:27 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Jul 12 16:01:01 2005 -0700" }, "message": "[PATCH] reset real_timer target on exec leader change\n\nWhen a noninitial thread does exec, it becomes the new group leader. If\nthere is a ITIMER_REAL timer running, it points at the old group leader and\nwhen it fires it can follow a stale pointer. The timer data needs to be\nreset to point at the exec\u0027ing thread that is becoming the group leader.\nThis has to synchronize with any concurrent firing of the timer to make\nsure that it_real_fn can never run when the data points to a thread that\nmight have been reaped already.\n\nSigned-off-by: Roland McGrath \u003croland@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "d6e711448137ca3301512cec41a2c2ce852b3d0a", "tree": "f0765ebd90fdbdf270c05fcd7f3d32b24ba56681", "parents": [ "8b0914ea7475615c7c8965c1ac8fe4069270f25c" ], "author": { "name": "Alan Cox", "email": "alan@lxorguk.ukuu.org.uk", "time": "Thu Jun 23 00:09:43 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Thu Jun 23 09:45:26 2005 -0700" }, "message": "[PATCH] setuid core dump\n\nAdd a new `suid_dumpable\u0027 sysctl:\n\nThis value can be used to query and set the core dump mode for setuid\nor otherwise protected/tainted binaries. The modes are\n\n0 - (default) - traditional behaviour. Any process which has changed\n privilege levels or is execute only will not be dumped\n\n1 - (debug) - all processes dump core when possible. The core dump is\n owned by the current user and no security is applied. This is intended\n for system debugging situations only. Ptrace is unchecked.\n\n2 - (suidsafe) - any binary which normally would not be dumped is dumped\n readable by root only. This allows the end user to remove such a dump but\n not access it directly. For security reasons core dumps in this mode will\n not overwrite one another or other files. This mode is appropriate when\n adminstrators are attempting to debug problems in a normal environment.\n\n(akpm:\n\n\u003e \u003e +EXPORT_SYMBOL(suid_dumpable);\n\u003e\n\u003e EXPORT_SYMBOL_GPL?\n\nNo problem to me.\n\n\u003e \u003e \tif (current-\u003eeuid \u003d\u003d current-\u003euid \u0026\u0026 current-\u003eegid \u003d\u003d current-\u003egid)\n\u003e \u003e \t\tcurrent-\u003emm-\u003edumpable \u003d 1;\n\u003e\n\u003e Should this be SUID_DUMP_USER?\n\nActually the feedback I had from last time was that the SUID_ defines\nshould go because its clearer to follow the numbers. They can go\neverywhere (and there are lots of places where dumpable is tested/used\nas a bool in untouched code)\n\n\u003e Maybe this should be renamed to `dump_policy\u0027 or something. Doing that\n\u003e would help us catch any code which isn\u0027t using the #defines, too.\n\nFair comment. The patch was designed to be easy to maintain for Red Hat\nrather than for merging. Changing that field would create a gigantic\ndiff because it is used all over the place.\n\n)\n\nSigned-off-by: Alan Cox \u003calan@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "c2a0f5943d8935766a42b2d0870aa4c645e3423d", "tree": "e3a0b1bd202725989d908cc4686dab4b1d9855d9", "parents": [ "c83d9945c05570ba6b8ec5460c99d1ab7c6e6671" ], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Jun 18 13:06:22 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Jun 18 13:06:22 2005 -0700" }, "message": "Clean up subthread exec\n\nMake sure we re-parent itimers, and use BUG_ON() instead of an explicit\nconditional BUG().\n" }, { "commit": "3677209239ed71d2654e73eecfab1dbec2af11a9", "tree": "125d9d7553c5f6dc6ad030e4c829a5bf71ab3ef5", "parents": [ "291c4a75ce7632ee5c565359fb875ba0597f76be" ], "author": { "name": "Paolo \u0027Blaisorblade\u0027 Giarrusso", "email": "blaisorblade@yahoo.it", "time": "Thu May 05 16:16:12 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Thu May 05 16:36:48 2005 -0700" }, "message": "[PATCH] comments on locking of task-\u003ecomm\n\nAdd some comments about task-\u003ecomm, to explain what it is near its definition\nand provide some important pointers to its uses.\n\nSigned-off-by: Paolo \u0027Blaisorblade\u0027 Giarrusso \u003cblaisorblade@yahoo.it\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "75c96f85845a6707b0f9916cb263cb3584f7d48f", "tree": "45a64d1c9bb71d7093db3a11e0f21465c2e3dec6", "parents": [ "5e198d94dd0c3ec7f6138229e2e412c2c6268c38" ], "author": { "name": "Adrian Bunk", "email": "bunk@stusta.de", "time": "Thu May 05 16:16:09 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Thu May 05 16:36:47 2005 -0700" }, "message": "[PATCH] make some things static\n\nThis patch makes some needlessly global identifiers static.\n\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\nAcked-by: Arjan van de Ven \u003carjanv@infradead.org\u003e\nAcked-by: Trond Myklebust \u003ctrond.myklebust@fys.uio.no\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }