)]}' { "log": [ { "commit": "74a0b5762713a26496db72eac34fbbed46f20fce", "tree": "4a14df7c07ebc16283454f33713519a0e10b5c43", "parents": [ "d5a7430ddcdb598261d70f7eb1bf450b5be52085" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue Oct 16 01:24:07 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Oct 16 09:42:50 2007 -0700" }, "message": "x86: optimize page faults like all other achitectures and kill notifier cruft\n\nx86(-64) are the last architectures still using the page fault notifier\ncruft for the kprobes page fault hook. This patch converts them to the\nproper direct calls, and removes the now unused pagefault notifier bits\naswell as the cruft in kprobes.c that was related to this mess.\n\nI know Andi didn\u0027t really like this, but all other architecture maintainers\nagreed the direct calls are much better and besides the obvious cruft\nremoval a common way of dealing with kprobes across architectures is\nimportant aswell.\n\n[akpm@linux-foundation.org: build fix]\n[akpm@linux-foundation.org: fix sparc64]\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nCc: Andi Kleen \u003cak@suse.de\u003e\nCc: \u003clinux-arch@vger.kernel.org\u003e\nCc: Prasanna S Panchamukhi \u003cprasanna@in.ibm.com\u003e\nCc: Ananth N Mavinakayanahalli \u003cananth@in.ibm.com\u003e\nCc: Anil S Keshavamurthy \u003canil.s.keshavamurthy@intel.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "a1aadd55fb43e31407aecc4ebaf0258130a98238", "tree": "e0d8b70de1e8e61f97d8e78528b5637b6d1f6e48", "parents": [ "b68a890fa3cd977365fda2b1f1ec4e8dc58baddf" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Wed May 23 14:57:49 2007 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@sunset.davemloft.net", "time": "Tue May 29 02:49:14 2007 -0700" }, "message": "[SPARC64]: Kill unused DIE_PAGE_FAULT enum value.\n\nsparc64 got rid of the pagefault notifiers, so the enum value for them\ncan go away aswell.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "127cda1e8cc282de1ca7a9dcc3866841977b9fcc", "tree": "800169fa92dc96160044d914ca1ca9fea60339ea", "parents": [ "6c1142602c9c8faedbc1321892a169652a173fc7" ], "author": { "name": "David S. Miller", "email": "davem@sunset.davemloft.net", "time": "Tue May 08 18:25:14 2007 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@sunset.davemloft.net", "time": "Tue May 08 18:25:14 2007 -0700" }, "message": "[SPARC64]: Optimize fault kprobe handling just like powerpc.\n\nAnd eliminate DIE_GPF while we\u0027re at it.\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "1eeb66a1bb973534dc3d064920a5ca683823372e", "tree": "19c22d611e6adefb352dbc107b859e4d13ba38c1", "parents": [ "e3869792990f708c97be5877499cada70d469bd3" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue May 08 00:27:03 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue May 08 11:15:04 2007 -0700" }, "message": "move die notifier handling to common code\n\nThis patch moves the die notifier handling to common code. Previous\nvarious architectures had exactly the same code for it. Note that the new\ncode is compiled unconditionally, this should be understood as an appel to\nthe other architecture maintainer to implement support for it aswell (aka\nsprinkling a notify_die or two in the proper place)\n\narm had a notifiy_die that did something totally different, I renamed it to\narm_notify_die as part of the patch and made it static to the file it\u0027s\ndeclared and used at. avr32 used to pass slightly less information through\nthis interface and I brought it into line with the other architectures.\n\n[akpm@linux-foundation.org: build fix]\n[akpm@linux-foundation.org: fix vmalloc_sync_all bustage]\n[bryan.wu@analog.com: fix vmalloc_sync_all in nommu]\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nCc: \u003clinux-arch@vger.kernel.org\u003e\nCc: Russell King \u003crmk@arm.linux.org.uk\u003e\nSigned-off-by: Bryan Wu \u003cbryan.wu@analog.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "d98f8f05188b45168db43df8ddc9feeb0b1cd512", "tree": "505edc88aa4e8ec3593d7a218c470e7cb9640fb7", "parents": [ "4f9e87c0454059e80f3811f95ad9f40ed28c69a2" ], "author": { "name": "Anil S Keshavamurthy", "email": "anil.s.keshavamurthy@intel.com", "time": "Mon Jun 26 00:25:27 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:22 2006 -0700" }, "message": "[PATCH] Notify page fault call chain for sparc64\n\nOverloading of page fault notification with the notify_die() has performance\nissues(since the only interested components for page fault is kprobes and/or\nkdb) and hence this patch introduces the new notifier call chain exclusively\nfor page fault notifications their by avoiding notifying unnecessary\ncomponents in the do_page_fault() code path.\n\nSigned-off-by: Anil S Keshavamurthy \u003canil.s.keshavamurthy@intel.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "e041c683412d5bf44dc2b109053e3b837b71742d", "tree": "9d271066ef379da0c0fb3b8cb4137abd5d2ebba0", "parents": [ "76b81e2b0e2241accebcc68e126bc5ab958661b9" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Mon Mar 27 01:16:30 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Mar 27 08:44:50 2006 -0800" }, "message": "[PATCH] Notifier chain update: API changes\n\nThe kernel\u0027s implementation of notifier chains is unsafe. There is no\nprotection against entries being added to or removed from a chain while the\nchain is in use. The issues were discussed in this thread:\n\n http://marc.theaimsgroup.com/?l\u003dlinux-kernel\u0026m\u003d113018709002036\u0026w\u003d2\n\nWe noticed that notifier chains in the kernel fall into two basic usage\nclasses:\n\n\t\"Blocking\" chains are always called from a process context\n\tand the callout routines are allowed to sleep;\n\n\t\"Atomic\" chains can be called from an atomic context and\n\tthe callout routines are not allowed to sleep.\n\nWe decided to codify this distinction and make it part of the API. Therefore\nthis set of patches introduces three new, parallel APIs: one for blocking\nnotifiers, one for atomic notifiers, and one for \"raw\" notifiers (which is\nreally just the old API under a new name). New kinds of data structures are\nused for the heads of the chains, and new routines are defined for\nregistration, unregistration, and calling a chain. The three APIs are\nexplained in include/linux/notifier.h and their implementation is in\nkernel/sys.c.\n\nWith atomic and blocking chains, the implementation guarantees that the chain\nlinks will not be corrupted and that chain callers will not get messed up by\nentries being added or removed. For raw chains the implementation provides no\nguarantees at all; users of this API must provide their own protections. (The\nidea was that situations may come up where the assumptions of the atomic and\nblocking APIs are not appropriate, so it should be possible for users to\nhandle these things in their own way.)\n\nThere are some limitations, which should not be too hard to live with. For\natomic/blocking chains, registration and unregistration must always be done in\na process context since the chain is protected by a mutex/rwsem. Also, a\ncallout routine for a non-raw chain must not try to register or unregister\nentries on its own chain. (This did happen in a couple of places and the code\nhad to be changed to avoid it.)\n\nSince atomic chains may be called from within an NMI handler, they cannot use\nspinlocks for synchronization. Instead we use RCU. The overhead falls almost\nentirely in the unregister routine, which is okay since unregistration is much\nless frequent that calling a chain.\n\nHere is the list of chains that we adjusted and their classifications. None\nof them use the raw API, so for the moment it is only a placeholder.\n\n ATOMIC CHAINS\n -------------\narch/i386/kernel/traps.c:\t\ti386die_chain\narch/ia64/kernel/traps.c:\t\tia64die_chain\narch/powerpc/kernel/traps.c:\t\tpowerpc_die_chain\narch/sparc64/kernel/traps.c:\t\tsparc64die_chain\narch/x86_64/kernel/traps.c:\t\tdie_chain\ndrivers/char/ipmi/ipmi_si_intf.c:\txaction_notifier_list\nkernel/panic.c:\t\t\t\tpanic_notifier_list\nkernel/profile.c:\t\t\ttask_free_notifier\nnet/bluetooth/hci_core.c:\t\thci_notifier\nnet/ipv4/netfilter/ip_conntrack_core.c:\tip_conntrack_chain\nnet/ipv4/netfilter/ip_conntrack_core.c:\tip_conntrack_expect_chain\nnet/ipv6/addrconf.c:\t\t\tinet6addr_chain\nnet/netfilter/nf_conntrack_core.c:\tnf_conntrack_chain\nnet/netfilter/nf_conntrack_core.c:\tnf_conntrack_expect_chain\nnet/netlink/af_netlink.c:\t\tnetlink_chain\n\n BLOCKING CHAINS\n ---------------\narch/powerpc/platforms/pseries/reconfig.c:\tpSeries_reconfig_chain\narch/s390/kernel/process.c:\t\tidle_chain\narch/x86_64/kernel/process.c\t\tidle_notifier\ndrivers/base/memory.c:\t\t\tmemory_chain\ndrivers/cpufreq/cpufreq.c\t\tcpufreq_policy_notifier_list\ndrivers/cpufreq/cpufreq.c\t\tcpufreq_transition_notifier_list\ndrivers/macintosh/adb.c:\t\tadb_client_list\ndrivers/macintosh/via-pmu.c\t\tsleep_notifier_list\ndrivers/macintosh/via-pmu68k.c\t\tsleep_notifier_list\ndrivers/macintosh/windfarm_core.c\twf_client_list\ndrivers/usb/core/notify.c\t\tusb_notifier_list\ndrivers/video/fbmem.c\t\t\tfb_notifier_list\nkernel/cpu.c\t\t\t\tcpu_chain\nkernel/module.c\t\t\t\tmodule_notify_list\nkernel/profile.c\t\t\tmunmap_notifier\nkernel/profile.c\t\t\ttask_exit_notifier\nkernel/sys.c\t\t\t\treboot_notifier_list\nnet/core/dev.c\t\t\t\tnetdev_chain\nnet/decnet/dn_dev.c:\t\t\tdnaddr_chain\nnet/ipv4/devinet.c:\t\t\tinetaddr_chain\n\nIt\u0027s possible that some of these classifications are wrong. If they are,\nplease let us know or submit a patch to fix them. Note that any chain that\ngets called very frequently should be atomic, because the rwsem read-locking\nused for blocking chains is very likely to incur cache misses on SMP systems.\n(However, if the chain\u0027s callout routines may sleep then the chain cannot be\natomic.)\n\nThe patch set was written by Alan Stern and Chandra Seetharaman, incorporating\nmaterial written by Keith Owens and suggestions from Paul McKenney and Andrew\nMorton.\n\n[jes@sgi.com: restructure the notifier chain initialization macros]\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Chandra Seetharaman \u003csekharan@us.ibm.com\u003e\nSigned-off-by: Jes Sorensen \u003cjes@sgi.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "b2b18660066997420b716c1881a6be8b82700d97", "tree": "7c6eb8e7b8163e3d332bd4a4efe2ae5b5cfabdd2", "parents": [ "ae67cd643e9e64217fd92457324625c67fec6e35" ], "author": { "name": "Paul E. McKenney", "email": "paulmck@us.ibm.com", "time": "Sat Jun 25 14:55:38 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Jun 25 16:24:38 2005 -0700" }, "message": "[PATCH] RCU: clean up a few remaining synchronize_kernel() calls\n\n2.6.12-rc6-mm1 has a few remaining synchronize_kernel()s, some (but not\nall) in comments. This patch changes these synchronize_kernel() calls (and\ncomments) to synchronize_rcu() or synchronize_sched() as follows:\n\n- arch/x86_64/kernel/mce.c mce_read(): change to synchronize_sched() to\n handle races with machine-check exceptions (synchronize_rcu() would not cut\n it given RCU implementations intended for hardcore realtime use.\n\n- drivers/input/serio/i8042.c i8042_stop(): change to synchronize_sched() to\n handle races with i8042_interrupt() interrupt handler. Again,\n synchronize_rcu() would not cut it given RCU implementations intended for\n hardcore realtime use.\n\n- include/*/kdebug.h comments: change to synchronize_sched() to handle races\n with NMIs. As before, synchronize_rcu() would not cut it...\n\n- include/linux/list.h comment: change to synchronize_rcu(), since this\n comment is for list_del_rcu().\n\n- security/keys/key.c unregister_key_type(): change to synchronize_rcu(),\n since this is interacting with RCU read side.\n\n- security/keys/process_keys.c install_session_keyring(): change to\n synchronize_rcu(), since this is interacting with RCU read side.\n\nSigned-off-by: \"Paul E. McKenney\" \u003cpaulmck@us.ibm.com\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" } ] }