{"push_id":1252876145,"size":1,"distinct_size":1,"ref":"refs/heads/6.0.1","head":"4ac8a78420c936b44119e29d15d1d68fd952c507","before":"863dc2b7978581ea71b54bb77c4a466cf1b30402","commits":[{"sha":"4ac8a78420c936b44119e29d15d1d68fd952c507","author":{"name":"Tejun Heo","email":"e1d87360d7f4d7b7ebaddc11b54e50a559aaba57@kernel.org"},"message":"firewire: don't use PREPARE_DELAYED_WORK\n\ncommit 70044d71d31d6973665ced5be04ef39ac1c09a48 upstream.\n\nPREPARE_[DELAYED_]WORK() are being phased out.  They have few users\nand a nasty surprise in terms of reentrancy guarantee as workqueue\nconsiders work items to be different if they don't have the same work\nfunction.\n\nfirewire core-device and sbp2 have been been multiplexing work items\nwith multiple work functions.  Introduce fw_device_workfn() and\nsbp2_lu_workfn() which invoke fw_device->workfn and\nsbp2_logical_unit->workfn respectively and always use the two\nfunctions as the work functions and update the users to set the\n->workfn fields instead of overriding work functions using\nPREPARE_DELAYED_WORK().\n\nThis fixes a variety of possible regressions since a2c1c57be8d9\n\"workqueue: consider work function when searching for busy work items\"\ndue to which fw_workqueue lost its required non-reentrancy property.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nAcked-by: Stefan Richter <stefanr@s5r6.in-berlin.de>\nCc: linux1394-devel@lists.sourceforge.net\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/4ac8a78420c936b44119e29d15d1d68fd952c507"}]}
{"actor":{"display_login":"dblockopp"}}