{"push_id":2369677466,"size":36,"distinct_size":36,"ref":"refs/heads/master","head":"8da5db7ddae1bed11e81ff419496cdea0ad77791","before":"97ace515f01439d4cf6e898b4094040dc12d36e7","commits":[{"sha":"49527bc0e8d207e87bf3ebe8eb8cce7353372d79","author":{"name":"Yixun Lan","email":"2786c64286e29bda92992991afe717fe5262c1fd@amlogic.com"},"message":"pinctrl: meson-axg: adjust uart_ao_b pin group naming\n\nSimply adjust the pin group to _x _y _z style, as to\nkeep the consistency in DT with previous naming scheme.\n\nFixes: 83c566806a68 (\"pinctrl: meson-axg: Add new pinctrl driver for Meson AXG SoC\")\nSigned-off-by: Yixun Lan <yixun.lan@amlogic.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/49527bc0e8d207e87bf3ebe8eb8cce7353372d79"},{"sha":"565e0450129647df5112bff3df3ffd02b0c08e32","author":{"name":"Aliaksei Karaliou","email":"e4351149f194341a446940e6aead6eac63a912b3@gmail.com"},"message":"md/raid5: simplify uninitialization of shrinker\n\nDon't use shrinker.nr_deferred to check whether shrinker was\ninitialized or not. Now this check was integrated into\nunregister_shrinker(), so it is safe to call it against\nunregistered shrinker.\n\nSigned-off-by: Aliaksei Karaliou <akaraliou.dev@gmail.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/565e0450129647df5112bff3df3ffd02b0c08e32"},{"sha":"56a64c177abd85a01c5881e195c363b7bda448f2","author":{"name":"Luis de Bethencourt","email":"9efc00209c16d128d4805749ca5906d62f798307@kernel.org"},"message":"md/raid1: Fix trailing semicolon\n\nThe trailing semicolon is an empty statement that does no operation.\nRemoving it since it doesn't do anything.\n\nSigned-off-by: Luis de Bethencourt <luisbg@kernel.org>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/56a64c177abd85a01c5881e195c363b7bda448f2"},{"sha":"3acdb7b514198d81ef7efcb2e86f498776ac10a7","author":{"name":"Markus Elfring","email":"2916b57751e3b8379170cb86139f7bb868e8eca1@users.sourceforge.net"},"message":"md-multipath: Use seq_putc() in multipath_status()\n\nA single character (closing square bracket) should be put into a sequence.\nThus use the corresponding function \"seq_putc\".\n\nThis issue was detected by using the Coccinelle software.\n\nSigned-off-by: Markus Elfring <elfring@users.sourceforge.net>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/3acdb7b514198d81ef7efcb2e86f498776ac10a7"},{"sha":"4b242e97d74192bbc5decd808c058cbc347af016","author":{"name":"Guoqing Jiang","email":"ac0d57d6fbcd5d2e156a2cc95a0fcd875905f252@suse.com"},"message":"raid10: change the size of resync window for clustered raid\n\nTo align with raid1's resync window, we need to\nset the resync window of raid10 to 32M as well.\n\nFixes: 8db87912c9a8 (\"md-cluster: Use a small window for raid10 resync\")\nReported-by: Zhilong Liu <zlliu@suse.com>\nSigned-off-by: Guoqing Jiang <gqjiang@suse.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/4b242e97d74192bbc5decd808c058cbc347af016"},{"sha":"b126194cbb799f9980b92a77e58db6ad794c8082","author":{"name":"Xiao Ni","email":"53e338f517289c78bd218c50656c5af71f3c7194@redhat.com"},"message":"MD: Free bioset when md_run fails\n\nSigned-off-by: Xiao Ni <xni@redhat.com>\nAcked-by: Guoqing Jiang <gqjiang@suse.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/b126194cbb799f9980b92a77e58db6ad794c8082"},{"sha":"4b6c1060eaa6495aa5b0032e8f2d51dd936b1257","author":{"name":"Heinz Mauelshagen","email":"2d63f023e792f084d3cf433ac0e2b5451fa335c0@redhat.com"},"message":"md: fix md_write_start() deadlock w/o metadata devices\n\nIf no metadata devices are configured on raid1/4/5/6/10\n(e.g. via dm-raid), md_write_start() unconditionally waits\nfor superblocks to be written thus deadlocking.\n\nFix introduces mddev->has_superblocks bool, defines it in md_run()\nand checks for it in md_write_start() to conditionally avoid waiting.\n\nOnce on it, check for non-existing superblocks in md_super_write().\n\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=198647\nFixes: cc27b0c78c796 (\"md: fix deadlock between mddev_suspend() and md_write_start()\")\n\nSigned-off-by: Heinz Mauelshagen <heinzm@redhat.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/4b6c1060eaa6495aa5b0032e8f2d51dd936b1257"},{"sha":"f2785b527cda46314805123ddcbc871655b7c4c4","author":{"name":"NeilBrown","email":"2d905a3497a379bccf401a15c6d441d61e66863c@suse.com"},"message":"md: document lifetime of internal rdev pointer.\n\nThe rdev pointer kept in the local 'config' for each for\nraid1, raid10, raid4/5/6 has non-obvious lifetime rules.\nSometimes RCU is needed, sometimes a lock, something nothing.\n\nAdd documentation to explain this.\n\nSigned-off-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/f2785b527cda46314805123ddcbc871655b7c4c4"},{"sha":"39772f0a7be3b3dc26c74ea13fe7847fd1522c8b","author":{"name":"NeilBrown","email":"2d905a3497a379bccf401a15c6d441d61e66863c@suse.com"},"message":"md: only allow remove_and_add_spares when no sync_thread running.\n\nThe locking protocols in md assume that a device will\nnever be removed from an array during resync/recovery/reshape.\nWhen that isn't happening, rcu or reconfig_mutex is needed\nto protect an rdev pointer while taking a refcount.  When\nit is happening, that protection isn't needed.\n\nUnfortunately there are cases were remove_and_add_spares() is\ncalled when recovery might be happening: is state_store(),\nslot_store() and hot_remove_disk().\nIn each case, this is just an optimization, to try to expedite\nremoval from the personality so the device can be removed from\nthe array.  If resync etc is happening, we just have to wait\nfor md_check_recover to find a suitable time to call\nremove_and_add_spares().\n\nThis optimization and not essential so it doesn't\nmatter if it fails.\nSo change remove_and_add_spares() to abort early if\nresync/recovery/reshape is happening, unless it is called\nfrom md_check_recovery() as part of a newly started recovery.\nThe parameter \"this\" is only NULL when called from\nmd_check_recovery() so when it is NULL, there is no need to abort.\n\nAs this can result in a NULL dereference, the fix is suitable\nfor -stable.\n\ncc: yuyufen <yuyufen@huawei.com>\nCc: Tomasz Majchrzak <tomasz.majchrzak@intel.com>\nFixes: 8430e7e0af9a (\"md: disconnect device from personality before trying to remove it.\")\nCc: stable@ver.kernel.org (v4.8+)\nSigned-off-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/39772f0a7be3b3dc26c74ea13fe7847fd1522c8b"},{"sha":"01a69cab01c184d3786af09e9339311123d63d22","author":{"name":"Yufen Yu","email":"e5190cd2ed8053d4ab01192d3cade76fc583578d@huawei.com"},"message":"md raid10: fix NULL deference in handle_write_completed()\n\nIn the case of 'recover', an r10bio with R10BIO_WriteError &\nR10BIO_IsRecover will be progressed by handle_write_completed().\nThis function traverses all r10bio->devs[copies].\nIf devs[m].repl_bio != NULL, it thinks conf->mirrors[dev].replacement\nis also not NULL. However, this is not always true.\n\nWhen there is an rdev of raid10 has replacement, then each r10bio\n->devs[m].repl_bio != NULL in conf->r10buf_pool. However, in 'recover',\neven if corresponded replacement is NULL, it doesn't clear r10bio\n->devs[m].repl_bio, resulting in replacement NULL deference.\n\nThis bug was introduced when replacement support for raid10 was\nadded in Linux 3.3.\n\nAs NeilBrown suggested:\n\tElsewhere the determination of \"is this device part of the\n\tresync/recovery\" is made by resting bio->bi_end_io.\n\tIf this is end_sync_write, then we tried to write here.\n\tIf it is NULL, then we didn't try to write.\n\nFixes: 9ad1aefc8ae8 (\"md/raid10:  Handle replacement devices during resync.\")\nCc: stable (V3.3+)\nSuggested-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Yufen Yu <yuyufen@huawei.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/01a69cab01c184d3786af09e9339311123d63d22"},{"sha":"78de41a368af26e54ba53e63629fd7f166f17cef","author":{"name":"Stefan Agner","email":"6fe76ede026e27600863a1ff38da4e776dcaecdf@agner.ch"},"message":"MAINTAINERS: add Freescale pin controllers\n\nAdd Dong Aisheng, Fabio Estevam, Shawn Guo and myself as maintainer\nand the Pengutronix kernel team as reviewer.\n\nSigned-off-by: Stefan Agner <stefan@agner.ch>\nReviewed-by: Fabio Estevam <festevam@gmail.com>\nAcked-by: Dong Aisheng <aisheng.dong@nxp.com>\nAcked-by: Lucas Stach <l.stach@pengutronix.de>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/78de41a368af26e54ba53e63629fd7f166f17cef"},{"sha":"f4bc0c813e03bdb93f5300c3e06d7a0f07f65a74","author":{"name":"Artur Paszkiewicz","email":"7b38a274cabb3b94dcfdb9cf93429a2a72995dc2@intel.com"},"message":"raid5-ppl: fix handling flush requests\n\nAdd missing bio completion. Without this any flush request would hang.\n\nFixes: 1532d9e87e8b (\"raid5-ppl: PPL support for disks with write-back cache enabled\")\nSigned-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/f4bc0c813e03bdb93f5300c3e06d7a0f07f65a74"},{"sha":"53b8d89ddbdbb0e4625a46d2cdbb6f106c52f801","author":{"name":"Arnd Bergmann","email":"72a0f6d3b182607e6d5c44b93e1abb7b23ee18f3@arndb.de"},"message":"md: raid5: avoid string overflow warning\n\ngcc warns about a possible overflow of the kmem_cache string, when adding\nfour characters to a string of the same length:\n\ndrivers/md/raid5.c: In function 'setup_conf':\ndrivers/md/raid5.c:2207:34: error: '-alt' directive writing 4 bytes into a region of size between 1 and 32 [-Werror=format-overflow=]\n  sprintf(conf->cache_name[1], \"%s-alt\", conf->cache_name[0]);\n                                  ^~~~\ndrivers/md/raid5.c:2207:2: note: 'sprintf' output between 5 and 36 bytes into a destination of size 32\n  sprintf(conf->cache_name[1], \"%s-alt\", conf->cache_name[0]);\n  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nIf I'm counting correctly, we need 11 characters for the fixed part\nof the string and 18 characters for a 64-bit pointer (when no gendisk\nis used), so that leaves three characters for conf->level, which should\nalways be sufficient.\n\nThis makes the code use snprintf() with the correct length, to\nmake the code more robust against changes, and to get the compiler\nto shut up.\n\nIn commit f4be6b43f1ac (\"md/raid5: ensure we create a unique name for\nkmem_cache when mddev has no gendisk\") from 2010, Neil said that\nthe pointer could be removed \"shortly\" once devices without gendisk\nare disallowed. I have no idea if that happened, but if it did, that\nshould probably be changed as well.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/53b8d89ddbdbb0e4625a46d2cdbb6f106c52f801"},{"sha":"7229b12f5da33d5c376ee264f063703844b8092d","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"ALSA: x86: hdmi: Add single_port option for compatible behavior\n\nThe recent support for the multiple PCM devices allowed user to use\nmultiple HDMI/DP outputs, but at the same time, the PCM stream\nassignment has been changed, too.  Due to that, the former PCM#0\n(there was only one stream in the past) is likely assigned to a\ndifferent one (e.g. PCM#2), and it ends up with the regression when\nuser sticks with the fixed configuration using the device#0.\n\nAlthough the multiple monitor support shouldn't matter when user\ndeploys the backend like PulseAudio that checks the jack detection\nstate, the behavior change isn't always acceptable for some users.\n\nAs a mitigation, this patch introduces an option to switch the\nbehavior back to the old-good-days: when the new option,\nsingle_port=1, is passed, the driver creates only a single PCM device,\nand it's assigned to the first connected one, like the earlier\nversions did.  The option is turned off as default still to support\nthe multiple monitors.\n\nFixes: 8a2d6ae1f737 (\"ALSA: x86: Register multiple PCM devices for the LPE audio card\")\nReported-and-tested-by: Hubert Mantel <mantel@metadox.de>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/7229b12f5da33d5c376ee264f063703844b8092d"},{"sha":"1ba8f9d308174e647b864c36209b4d7934d99888","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"ALSA: hda: Add a power_save blacklist\n\nOn some boards setting power_save to a non 0 value leads to clicking /\npopping sounds when ever we enter/leave powersaving mode. Ideally we would\nfigure out how to avoid these sounds, but that is not always feasible.\n\nThis commit adds a blacklist for devices where powersaving is known to\ncause problems and disables it on these devices.\n\nNote I tried to put this blacklist in userspace first:\nhttps://github.com/systemd/systemd/pull/8128\n\nBut the systemd maintainers rightfully pointed out that it would be\nimpossible to then later remove entries once we actually find a way to\nmake power-saving work on listed boards without issues. Having this list\nin the kernel will allow removal of the blacklist entry in the same commit\nwhich fixes the clicks / plops.\n\nThe blacklist only applies to the default power_save module-option value,\nif a user explicitly sets the module-option then the blacklist is not\nused.\n\n[ added an ifdef CONFIG_PM for the build error -- tiwai]\n\nBugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1525104\nBugLink: https://bugzilla.kernel.org/show_bug.cgi?id=198611\nCc: stable@vger.kernel.org\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/1ba8f9d308174e647b864c36209b4d7934d99888"},{"sha":"240a8af929c7c57dcde28682725b29cf8474e8e5","author":{"name":"Erik Veijola","email":"9f3cb5b800a9005e37da3db411d8ad38c340c640@gmail.com"},"message":"ALSA: usb-audio: Add a quirck for B&W PX headphones\n\nThe capture interface doesn't work and the playback interface only\nsupports 48 kHz sampling rate even though it advertises more rates.\n\nSigned-off-by: Erik Veijola <erik.veijola@gmail.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/240a8af929c7c57dcde28682725b29cf8474e8e5"},{"sha":"de9647efeaa9f4e8b08c002e09757fd9c55ff901","author":{"name":"Mario Limonciello","email":"c22b05eda413b8f4df933e5f3f9e3839748a9763@dell.com"},"message":"platform/x86: intel-vbtn: Only activate tablet mode switch on 2-in-1's\n\nSome laptops such as the XPS 9360 support the intel-vbtn INT33D6\ninterface but don't initialize the bit that intel-vbtn uses to\nrepresent switching tablet mode.\n\nBy running this only on real 2-in-1's it shouldn't cause false\npositives.\n\nFixes: 30323fb6d5 (\"Support tablet mode switch\")\nReported-by: Jeremy Cline <jeremy@jcline.org>\nSigned-off-by: Mario Limonciello <mario.limonciello@dell.com>\nTested-by: Jeremy Cline <jeremy@jcline.org>\nTested-by: Darren Hart (VMware) <dvhart@infradead.org>\nSigned-off-by: Darren Hart (VMware) <dvhart@infradead.org>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/de9647efeaa9f4e8b08c002e09757fd9c55ff901"},{"sha":"43a521238aca0e24d50add1db125a61bda2a3527","author":{"name":"Lidong Zhong","email":"4a5397e7d120b6a9d2fe8f00d76a178ca0a59db6@suse.com"},"message":"md-cluster: choose correct label when clustered layout is not supported\n\nr10conf is already successfully allocated before checking the layout\n\nSigned-off-by: Lidong Zhong <lzhong@suse.com>\nReviewed-by: Guoqing Jiang <gqjiang@suse.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/43a521238aca0e24d50add1db125a61bda2a3527"},{"sha":"8876391e440ba615b10eef729576e111f0315f87","author":{"name":"BingJing Chang","email":"0c30e523808481c4e0c1e09febfa0fab5acbb0ba@synology.com"},"message":"md: fix a potential deadlock of raid5/raid10 reshape\n\nThere is a potential deadlock if mount/umount happens when\nraid5_finish_reshape() tries to grow the size of emulated disk.\n\nHow the deadlock happens?\n1) The raid5 resync thread finished reshape (expanding array).\n2) The mount or umount thread holds VFS sb->s_umount lock and tries to\n   write through critical data into raid5 emulated block device. So it\n   waits for raid5 kernel thread handling stripes in order to finish it\n   I/Os.\n3) In the routine of raid5 kernel thread, md_check_recovery() will be\n   called first in order to reap the raid5 resync thread. That is,\n   raid5_finish_reshape() will be called. In this function, it will try\n   to update conf and call VFS revalidate_disk() to grow the raid5\n   emulated block device. It will try to acquire VFS sb->s_umount lock.\nThe raid5 kernel thread cannot continue, so no one can handle mount/\numount I/Os (stripes). Once the write-through I/Os cannot be finished,\nmount/umount will not release sb->s_umount lock. The deadlock happens.\n\nThe raid5 kernel thread is an emulated block device. It is responible to\nhandle I/Os (stripes) from upper layers. The emulated block device\nshould not request any I/Os on itself. That is, it should not call VFS\nlayer functions. (If it did, it will try to acquire VFS locks to\nguarantee the I/Os sequence.) So we have the resync thread to send\nresync I/O requests and to wait for the results.\n\nFor solving this potential deadlock, we can put the size growth of the\nemulated block device as the final step of reshape thread.\n\n2017/12/29:\nThanks to Guoqing Jiang <gqjiang@suse.com>,\nwe confirmed that there is the same deadlock issue in raid10. It's\nreproducible and can be fixed by this patch. For raid10.c, we can remove\nthe similar code to prevent deadlock as well since they has been called\nbefore.\n\nReported-by: Alex Wu <alexwu@synology.com>\nReviewed-by: Alex Wu <alexwu@synology.com>\nReviewed-by: Chung-Chiang Cheng <cccheng@synology.com>\nSigned-off-by: BingJing Chang <bingjingc@synology.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/8876391e440ba615b10eef729576e111f0315f87"},{"sha":"3de59bb9d551428cbdc76a9ea57883f82e350b4d","author":{"name":"Yufen Yu","email":"e5190cd2ed8053d4ab01192d3cade76fc583578d@huawei.com"},"message":"md/raid1: fix NULL pointer dereference\n\nIn handle_write_finished(), if r1_bio->bios[m] != NULL, it thinks\nthe corresponding conf->mirrors[m].rdev is also not NULL. But, it\nis not always true.\n\nEven if some io hold replacement rdev(i.e. rdev->nr_pending.count > 0),\nraid1_remove_disk() can also set the rdev as NULL. That means,\nbios[m] != NULL, but mirrors[m].rdev is NULL, resulting in NULL\npointer dereference in handle_write_finished and sync_request_write.\n\nThis patch can fix BUGs as follows:\n\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000140\n IP: [<ffffffff815bbbbd>] raid1d+0x2bd/0xfc0\n PGD 12ab52067 PUD 12f587067 PMD 0\n Oops: 0000 [#1] SMP\n CPU: 1 PID: 2008 Comm: md3_raid1 Not tainted 4.1.44+ #130\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1.fc26 04/01/2014\n Call Trace:\n  ? schedule+0x37/0x90\n  ? prepare_to_wait_event+0x83/0xf0\n  md_thread+0x144/0x150\n  ? wake_atomic_t_function+0x70/0x70\n  ? md_start_sync+0xf0/0xf0\n  kthread+0xd8/0xf0\n  ? kthread_worker_fn+0x160/0x160\n  ret_from_fork+0x42/0x70\n  ? kthread_worker_fn+0x160/0x160\n\n BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8\n IP: sync_request_write+0x9e/0x980\n PGD 800000007c518067 P4D 800000007c518067 PUD 8002b067 PMD 0\n Oops: 0000 [#1] SMP PTI\n CPU: 24 PID: 2549 Comm: md3_raid1 Not tainted 4.15.0+ #118\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1.fc26 04/01/2014\n Call Trace:\n  ? sched_clock+0x5/0x10\n  ? sched_clock_cpu+0xc/0xb0\n  ? flush_pending_writes+0x3a/0xd0\n  ? pick_next_task_fair+0x4d5/0x5f0\n  ? __switch_to+0xa2/0x430\n  raid1d+0x65a/0x870\n  ? find_pers+0x70/0x70\n  ? find_pers+0x70/0x70\n  ? md_thread+0x11c/0x160\n  md_thread+0x11c/0x160\n  ? finish_wait+0x80/0x80\n  kthread+0x111/0x130\n  ? kthread_create_worker_on_cpu+0x70/0x70\n  ? do_syscall_64+0x6f/0x190\n  ? SyS_exit_group+0x10/0x10\n  ret_from_fork+0x35/0x40\n\nReviewed-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Yufen Yu <yuyufen@huawei.com>\nSigned-off-by: Shaohua Li <sh.li@alibaba-inc.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/3de59bb9d551428cbdc76a9ea57883f82e350b4d"}]}
{"actor":{"display_login":"kraj"}}