)]}' { "log": [ { "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": "8ed965d612d9e9bc08805c75123f063cf6966311", "tree": "7a863b9cb0d408295193f888b06d40d3364a404a", "parents": [ "9cdf18279d1f4a2d075ebe924d74e6e4547f6e1b" ], "author": { "name": "Arjan van de Ven", "email": "arjan@infradead.org", "time": "Thu Mar 23 03:00:21 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Thu Mar 23 07:38:10 2006 -0800" }, "message": "[PATCH] sem2mutex: drivers: raw, connector, dcdbas, ppp_generic\n\nSemaphore to mutex conversion.\n\nThe conversion was generated via scripts, and the result was validated\nautomatically via a script as well.\n\nSigned-off-by: Arjan van de Ven \u003carjan@infradead.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Stephen Rothwell \u003csfr@canb.auug.org.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "a7f3ea728b36aff520dff1611b3ce10cff46d8fe", "tree": "a3bd942d1e2a25529ecae24bdfb16f28a89fddf2", "parents": [ "d0497614e0bd54f113041966532035edba463f8e" ], "author": { "name": "Dmitry Torokhov", "email": "dtor_core@ameritech.net", "time": "Wed Mar 22 00:07:56 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Wed Mar 22 07:53:56 2006 -0800" }, "message": "[PATCH] dcdbas: convert to the new platform device interface\n\nDo not use platform_device_register_simple() as it is going away, define\ndcdbas_driver and implement -\u003eprobe() and -\u003eremove() functions so manual\nbinding and unbinding will work with this driver.\n\nAlso switch to using attribute_group when creating sysfs attributes and\nmake sure to check and handle errors; explicitely remove attributes when\ndetaching driver.\n\nSigned-off-by: Dmitry Torokhov \u003cdtor@mail.ru\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "435a80f610b2ac38a4b5334a7ae22672de3f06bd", "tree": "ddac23d1719827a21cee10d0991ed078a8825c97", "parents": [ "85a6cd03a97f04ffff7bfedfa3172894ca9a617b" ], "author": { "name": "Doug Warzecha", "email": "Douglas_Warzecha@dell.com", "time": "Thu Mar 09 17:33:35 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Thu Mar 09 19:47:36 2006 -0800" }, "message": "[PATCH] dcdbas: dcdbas_pdev referenced after platform_device_unregister on exit\n\nsmi_data_buf_free() references dcdbas_pdev when calling\ndma_free_coherent(). In dcdbas_exit(), smi_data_buf_free() is called after\nplatform_device_unregister(dcdbas_pdev).\n\nThis patch moves platform_device_unregister(dcdbas_pdev) after\nsmi_data_buf_free() in dcdbas_exit().\n\nSigned-off-by: Doug Warzecha \u003cDouglas_Warzecha@dell.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "d052d1beff706920e82c5d55006b08e256b5df09", "tree": "dac91b70361b405ab8e15207f514a2f3e991e93d", "parents": [ "8a212ab6b8a4ccc6f3c3d1beba5f92655c576404" ], "author": { "name": "Russell King", "email": "rmk@dyn-67.arm.linux.org.uk", "time": "Sat Oct 29 19:07:23 2005 +0100" }, "committer": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Sat Oct 29 19:07:23 2005 +0100" }, "message": "Create platform_device.h to contain all the platform device details.\nConvert everyone who uses platform_bus_type to include\nlinux/platform_device.h.\n\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nAcked-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n" }, { "commit": "90563ec4129f14d19f018240d1d3ff5c0e5e6392", "tree": "93a8c5c3a0c30e27dcb4ff7ed804d68257181fe0", "parents": [ "6c54c28e69f2a374ad708fba37cbe1c5bb94e283" ], "author": { "name": "Doug Warzecha", "email": "Douglas_Warzecha@dell.com", "time": "Tue Sep 06 15:17:15 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Wed Sep 07 16:57:27 2005 -0700" }, "message": "[PATCH] dcdbas: add Dell Systems Management Base Driver with sysfs support\n\nThis patch adds the Dell Systems Management Base Driver with sysfs support.\n\nThis driver has been tested with Dell OpenManage.\n\nSigned-off-by: Doug Warzecha \u003cDouglas_Warzecha@dell.com\u003e\nCc: Greg KH \u003cgreg@kroah.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" } ] }