{ "_class" : "hudson.model.FreeStyleBuild", "actions" : [ { "_class" : "hudson.model.ParametersAction", "parameters" : [ { "_class" : "hudson.model.StringParameterValue", "name" : "release", "value" : "leste" }, { "_class" : "hudson.model.StringParameterValue", "name" : "distribution", "value" : "beowulf" } ] }, { "_class" : "hudson.model.CauseAction", "causes" : [ { "_class" : "hudson.model.Cause$UserIdCause", "shortDescription" : "Started by user Ivan J.", "userId" : "parazyd", "userName" : "Ivan J." } ] }, { }, { "_class" : "hudson.plugins.git.util.BuildData", "buildsByBranchName" : { "refs/remotes/origin/maemo/ascii" : { "_class" : "hudson.plugins.git.util.Build", "buildNumber" : 64, "buildResult" : None, "marked" : { "SHA1" : "984583c461d40eaaf7621533d2b772af5bf94bc9", "branch" : [ { "SHA1" : "984583c461d40eaaf7621533d2b772af5bf94bc9", "name" : "refs/remotes/origin/maemo/ascii" } ] }, "revision" : { "SHA1" : "984583c461d40eaaf7621533d2b772af5bf94bc9", "branch" : [ { "SHA1" : "984583c461d40eaaf7621533d2b772af5bf94bc9", "name" : "refs/remotes/origin/maemo/ascii" } ] } }, "refs/remotes/origin/maemo/beowulf" : { "_class" : "hudson.plugins.git.util.Build", "buildNumber" : 71, "buildResult" : None, "marked" : { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "branch" : [ { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "name" : "refs/remotes/origin/maemo/beowulf" } ] }, "revision" : { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "branch" : [ { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "name" : "refs/remotes/origin/maemo/beowulf" } ] } }, "refs/remotes/origin/maemo/ascii-devel" : { "_class" : "hudson.plugins.git.util.Build", "buildNumber" : 58, "buildResult" : None, "marked" : { "SHA1" : "3abb5565ac9f862f16abf132fa8925eca5d41e32", "branch" : [ { "SHA1" : "3abb5565ac9f862f16abf132fa8925eca5d41e32", "name" : "refs/remotes/origin/maemo/ascii-devel" } ] }, "revision" : { "SHA1" : "3abb5565ac9f862f16abf132fa8925eca5d41e32", "branch" : [ { "SHA1" : "3abb5565ac9f862f16abf132fa8925eca5d41e32", "name" : "refs/remotes/origin/maemo/ascii-devel" } ] } }, "refs/remotes/origin/maemo/beowulf-devel" : { "_class" : "hudson.plugins.git.util.Build", "buildNumber" : 70, "buildResult" : None, "marked" : { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "branch" : [ { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "name" : "refs/remotes/origin/maemo/beowulf-devel" } ] }, "revision" : { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "branch" : [ { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "name" : "refs/remotes/origin/maemo/beowulf-devel" } ] } } }, "lastBuiltRevision" : { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "branch" : [ { "SHA1" : "16171baac6109885bedb2b52e0377c36f75449df", "name" : "refs/remotes/origin/maemo/beowulf" } ] }, "remoteUrls" : [ "https://github.com/maemo-leste/n9xx-linux" ], "scmName" : "" }, { "_class" : "hudson.plugins.git.GitTagAction" }, { }, { "_class" : "hudson.plugins.parameterizedtrigger.BuildInfoExporterAction" }, { }, { } ], "artifacts" : [ { "displayPath" : "n9xx-linux_5.1.22-1+2m7.1.debian.tar.xz", "fileName" : "n9xx-linux_5.1.22-1+2m7.1.debian.tar.xz", "relativePath" : "n9xx-linux_5.1.22-1+2m7.1.debian.tar.xz" }, { "displayPath" : "n9xx-linux_5.1.22-1+2m7.1.dsc", "fileName" : "n9xx-linux_5.1.22-1+2m7.1.dsc", "relativePath" : "n9xx-linux_5.1.22-1+2m7.1.dsc" }, { "displayPath" : "n9xx-linux_5.1.22-1+2m7.1_source.buildinfo", "fileName" : "n9xx-linux_5.1.22-1+2m7.1_source.buildinfo", "relativePath" : "n9xx-linux_5.1.22-1+2m7.1_source.buildinfo" }, { "displayPath" : "n9xx-linux_5.1.22.orig.tar.gz", "fileName" : "n9xx-linux_5.1.22.orig.tar.gz", "relativePath" : "n9xx-linux_5.1.22.orig.tar.gz" } ], "building" : False, "description" : None, "displayName" : "#71", "duration" : 2788766, "estimatedDuration" : 2992220, "executor" : None, "fullDisplayName" : "n9xx-linux-source #71", "id" : "71", "keepLog" : False, "number" : 71, "queueId" : 830, "result" : "SUCCESS", "timestamp" : 1593219198931, "url" : "https://phoenix.maemo.org/job/n9xx-linux-source/71/", "builtOn" : "", "changeSet" : { "_class" : "hudson.plugins.git.GitChangeSetList", "items" : [ { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/hda/ext/hdac_ext_bus.c" ], "commitId" : "69b418b02a6c5defcc08d5529a253c30bbdb6ac3", "timestamp" : 1562745145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hdac: fix memory release for SST and SOF drivers\u000a\u000a[ Upstream commit 6d647b736a6b1cbf2f8deab0e6a94c34a6ea9d60 ]\u000a\u000aDuring the integration of HDaudio support, we changed the way in which\u000awe get hdev in snd_hdac_ext_bus_device_init() to use one preallocated\u000awith devm_kzalloc(), however it still left kfree(hdev) in\u000asnd_hdac_ext_bus_device_exit(). It leads to oopses when trying to\u000armmod and modprobe. Fix it, by just removing kfree call.\u000a\u000aSOF also uses some of the snd_hdac_ functions for HDAudio support but\u000aallocated the memory with kzalloc. A matching fix is provided\u000aseparately to align all users of the snd_hdac_ library.\u000a\u000aFixes: 6298542fa33b (\"ALSA: hdac: remove memory allocation from snd_hdac_ext_bus_device_init\")\u000aReviewed-by: Takashi Iwai \u000aSigned-off-by: Amadeusz Sławiński \u000aSigned-off-by: Pierre-Louis Bossart \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:25 +0200", "id" : "69b418b02a6c5defcc08d5529a253c30bbdb6ac3", "msg" : "ALSA: hdac: fix memory release for SST and SOF drivers", "paths" : [ { "editType" : "edit", "file" : "sound/hda/ext/hdac_ext_bus.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/codecs/rt274.c" ], "commitId" : "b6cb887f36a1d06e0f3e139188bacc80ef02f126", "timestamp" : 1562745145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "SoC: rt274: Fix internal jack assignment in set_jack callback\u000a\u000a[ Upstream commit 04268bf2757a125616b6c2140e6250f43b7b737a ]\u000a\u000aWhen we call snd_soc_component_set_jack(component, NULL, NULL) we should\u000aset rt274->jack to passed jack, so when interrupt is triggered it calls\u000asnd_soc_jack_report(rt274->jack, ...) with proper value.\u000a\u000aThis fixes problem in machine where in register, we call\u000asnd_soc_register(component, &headset, NULL), which just calls\u000art274_mic_detect via callback.\u000aNow when machine driver is removed \"headset\" will be gone, so we\u000aneed to tell codec driver that it's gone with:\u000asnd_soc_register(component, NULL, NULL), but we also need to be able\u000ato handle NULL jack argument here gracefully.\u000aIf we don't set it to NULL, next time the rt274_irq runs it will call\u000asnd_soc_jack_report with first argument being invalid pointer and there\u000awill be Oops.\u000a\u000aSigned-off-by: Amadeusz Sławiński \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:25 +0200", "id" : "b6cb887f36a1d06e0f3e139188bacc80ef02f126", "msg" : "SoC: rt274: Fix internal jack assignment in set_jack callback", "paths" : [ { "editType" : "edit", "file" : "sound/soc/codecs/rt274.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/hpsa_cmd.h", "drivers/scsi/hpsa.c" ], "commitId" : "f55e3e088fcf989411d8bceb9969e8e1daaaf0aa", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: hpsa: correct ioaccel2 chaining\u000a\u000a[ Upstream commit 625d7d3518875c4d303c652a198feaa13d9f52d9 ]\u000a\u000a- set ioaccel2_sg_element member 'chain_indicator' to IOACCEL2_LAST_SG for\u000a the last s/g element.\u000a\u000a- set ioaccel2_sg_element member 'chain_indicator' to IOACCEL2_CHAIN when\u000a chaining.\u000a\u000aReviewed-by: Bader Ali - Saleh \u000aReviewed-by: Scott Teel \u000aReviewed-by: Matt Perricone \u000aSigned-off-by: Don Brace \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "f55e3e088fcf989411d8bceb9969e8e1daaaf0aa", "msg" : "scsi: hpsa: correct ioaccel2 chaining", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/hpsa_cmd.h" }, { "editType" : "edit", "file" : "drivers/scsi/hpsa.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpio-pca953x.c" ], "commitId" : "ebae5c66fa67cfd5cdd5c7ef8f76cdf08a4391e3", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpio: pca953x: hack to fix 24 bit gpio expanders\u000a\u000a[ Upstream commit 3b00691cc46a4089368a008b30655a8343411715 ]\u000a\u000a24 bit expanders use REG_ADDR_AI in combination with register addressing. This\u000aconflicts with regmap which takes this bit as part of the register number,\u000ai.e. a second cache entry is defined for accessed with REG_ADDR_AI being\u000aset although on the chip it is the same register as with REG_ADDR_AI being\u000acleared.\u000a\u000aThe problem was introduced by\u000a\u000a\u0009commit b32cecb46bdc (\"gpio: pca953x: Extract the register address mangling to single function\")\u000a\u000abut only became visible by\u000a\u000a\u0009commit 8b9f9d4dc511 (\"regmap: verify if register is writeable before writing operations\")\u000a\u000abecause before, the regmap size was effectively ignored and\u000apca953x_writeable_register() did know to ignore REG_ADDR_AI. Still, there\u000awere two separate cache entries created.\u000a\u000aSince the use of REG_ADDR_AI seems to be static we can work around this\u000aissue by simply increasing the size of the regmap to cover the \"virtual\"\u000aregisters with REG_ADDR_AI being set. This only means that half of the\u000aregmap buffer will be unused.\u000a\u000aReported-by: H. Nikolaus Schaller \u000aSuggested-by: Linus Walleij \u000aSigned-off-by: H. Nikolaus Schaller \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "ebae5c66fa67cfd5cdd5c7ef8f76cdf08a4391e3", "msg" : "gpio: pca953x: hack to fix 24 bit gpio expanders", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpio-pca953x.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/drm_panel_orientation_quirks.c" ], "commitId" : "eabfa988ceec0ff630f04b4669b30018a7dad300", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm: panel-orientation-quirks: Add quirk for GPD pocket2\u000a\u000a[ Upstream commit 15abc7110a77555d3bf72aaef46d1557db0a4ac5 ]\u000a\u000aGPD has done it again, make a nice device (good), use way too generic\u000aDMI strings (bad) and use a portrait screen rotated 90 degrees (ugly).\u000a\u000aBecause of the too generic DMI strings this entry is also doing bios-date\u000amatching, so the gpd_pocket2 data struct may very well need to be updated\u000awith some extra bios-dates in the future.\u000a\u000aChanges in v2:\u000a-Add one more known BIOS date to the list of BIOS dates\u000a\u000aCc: Jurgen Kramer \u000aReported-by: Jurgen Kramer \u000aAcked-by: Maxime Ripard \u000aSigned-off-by: Hans de Goede \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20190524125759.14131-1-hdegoede@redhat.com\u000a(cherry picked from commit 6dab9102dd7b144e5723915438e0d6c473018cd0)\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "eabfa988ceec0ff630f04b4669b30018a7dad300", "msg" : "drm: panel-orientation-quirks: Add quirk for GPD pocket2", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/drm_panel_orientation_quirks.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/drm_panel_orientation_quirks.c" ], "commitId" : "0a1c42cf2a9a0f799bc834f9c15156d28a6c6089", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm: panel-orientation-quirks: Add quirk for GPD MicroPC\u000a\u000a[ Upstream commit 652b8b086538c8a10de5aa5cbdaef79333b46358 ]\u000a\u000aGPD has done it again, make a nice device (good), use way too generic\u000aDMI strings (bad) and use a portrait screen rotated 90 degrees (ugly).\u000a\u000aBecause of the too generic DMI strings this entry is also doing bios-date\u000amatching, so the gpd_micropc data struct may very well need to be updated\u000awith some extra bios-dates in the future.\u000a\u000aAcked-by: Maxime Ripard \u000aSigned-off-by: Hans de Goede \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20190524125759.14131-2-hdegoede@redhat.com\u000a(cherry picked from commit f2f2bb60d998abde10de7e483ef9e17639892450)\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "0a1c42cf2a9a0f799bc834f9c15156d28a6c6089", "msg" : "drm: panel-orientation-quirks: Add quirk for GPD MicroPC", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/drm_panel_orientation_quirks.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/soc-core.c" ], "commitId" : "c7e65a33d75d5aafcf18d9cf84786bc4436a0ba5", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: core: Fix deadlock in snd_soc_instantiate_card()\u000a\u000a[ Upstream commit 495f926c68ddb905a7a0192963096138c6a934e1 ]\u000a\u000aMove the client_mutex lock to snd_soc_unbind_card() before\u000aremoving link components. This prevents the deadlock\u000ain the error path in snd_soc_instantiate_card().\u000a\u000aFixes: 34ac3c3eb8 (ASoC: core: lock client_mutex while removing\u000alink components)\u000aReported-by: kernelci.org bot \u000aSigned-off-by: Ranjani Sridharan \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "c7e65a33d75d5aafcf18d9cf84786bc4436a0ba5", "msg" : "ASoC: core: Fix deadlock in snd_soc_instantiate_card()", "paths" : [ { "editType" : "edit", "file" : "sound/soc/soc-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/intel/atom/sst/sst_pvt.c" ], "commitId" : "c2784e57271e415bca7b6ae8caedb87ad27724a8", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: Intel: sst: fix kmalloc call with wrong flags\u000a\u000a[ Upstream commit 3da428ff2aa5a5191ba2f1630eea75f03242f3f2 ]\u000a\u000aWhen calling kmalloc with GFP_KERNEL in case CONFIG_SLOB is unset,\u000akmem_cache_alloc_trace is called.\u000a\u000aIn case CONFIG_TRACING is set, kmem_cache_alloc_trace will ball\u000aslab_alloc, which will call slab_pre_alloc_hook which might_sleep_if.\u000a\u000aThe context in which it is called in this case, the\u000aintel_sst_interrupt_mrfld, calling a sleeping kmalloc generates a BUG():\u000a\u000aFixes: 972b0d456e64 (\"ASoC: Intel: remove GFP_ATOMIC, use GFP_KERNEL\")\u000a\u000a[ 20.250671] BUG: sleeping function called from invalid context at mm/slab.h:422\u000a[ 20.250683] in_atomic(): 1, irqs_disabled(): 1, pid: 1791, name: Chrome_IOThread\u000a[ 20.250690] CPU: 0 PID: 1791 Comm: Chrome_IOThread Tainted: G W 4.19.43 #61\u000a[ 20.250693] Hardware name: GOOGLE Kefka, BIOS Google_Kefka.7287.337.0 03/02/2017\u000a[ 20.250697] Call Trace:\u000a[ 20.250704] \u000a[ 20.250716] dump_stack+0x7e/0xc3\u000a[ 20.250725] ___might_sleep+0x12a/0x140\u000a[ 20.250731] kmem_cache_alloc_trace+0x53/0x1c5\u000a[ 20.250736] ? update_cfs_rq_load_avg+0x17e/0x1aa\u000a[ 20.250740] ? cpu_load_update+0x6c/0xc2\u000a[ 20.250746] sst_create_ipc_msg+0x2d/0x88\u000a[ 20.250752] intel_sst_interrupt_mrfld+0x12a/0x22c\u000a[ 20.250758] __handle_irq_event_percpu+0x133/0x228\u000a[ 20.250764] handle_irq_event_percpu+0x35/0x7a\u000a[ 20.250768] handle_irq_event+0x36/0x55\u000a[ 20.250773] handle_fasteoi_irq+0xab/0x16c\u000a[ 20.250779] handle_irq+0xd9/0x11e\u000a[ 20.250785] do_IRQ+0x54/0xe0\u000a[ 20.250791] common_interrupt+0xf/0xf\u000a[ 20.250795] \u000a[ 20.250800] RIP: 0010:__lru_cache_add+0x4e/0xad\u000a[ 20.250806] Code: 00 01 48 c7 c7 b8 df 01 00 65 48 03 3c 25 28 f1 00 00 48 8b 48 08 48 89 ca 48 ff ca f6 c1 01 48 0f 44 d0 f0 ff 42 34 0f b6 0f <89> ca fe c2 88 17 48 89 44 cf 08 80 fa 0f 74 0e 48 8b 08 66 85 c9\u000a[ 20.250809] RSP: 0000:ffffa568810bfd98 EFLAGS: 00000202 ORIG_RAX: ffffffffffffffd6\u000a[ 20.250814] RAX: ffffd3b904eb1940 RBX: ffffd3b904eb1940 RCX: 0000000000000004\u000a[ 20.250817] RDX: ffffd3b904eb1940 RSI: ffffa10ee5c47450 RDI: ffffa10efba1dfb8\u000a[ 20.250821] RBP: ffffa568810bfda8 R08: ffffa10ef9c741c1 R09: dead000000000100\u000a[ 20.250824] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa10ee8d52a40\u000a[ 20.250827] R13: ffffa10ee8d52000 R14: ffffa10ee5c47450 R15: 800000013ac65067\u000a[ 20.250835] lru_cache_add_active_or_unevictable+0x4e/0xb8\u000a[ 20.250841] handle_mm_fault+0xd98/0x10c4\u000a[ 20.250848] __do_page_fault+0x235/0x42d\u000a[ 20.250853] ? page_fault+0x8/0x30\u000a[ 20.250858] do_page_fault+0x3d/0x17a\u000a[ 20.250862] ? page_fault+0x8/0x30\u000a[ 20.250866] page_fault+0x1e/0x30\u000a[ 20.250872] RIP: 0033:0x7962fdea9304\u000a[ 20.250875] Code: 0f 11 4c 17 f0 c3 48 3b 15 f1 26 31 00 0f 83 e2 00 00 00 48 39 f7 72 0f 74 12 4c 8d 0c 16 4c 39 cf 0f 82 63 01 00 00 48 89 d1 a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6\u000a[ 20.250879] RSP: 002b:00007962f4db5468 EFLAGS: 00010206\u000a[ 20.250883] RAX: 00003c8cc9d47008 RBX: 0000000000000000 RCX: 0000000000001b48\u000a[ 20.250886] RDX: 0000000000002b40 RSI: 00003c8cc9551000 RDI: 00003c8cc9d48000\u000a[ 20.250890] RBP: 00007962f4db5820 R08: 0000000000000000 R09: 00003c8cc9552b48\u000a[ 20.250893] R10: 0000562dd1064d30 R11: 00003c8cc825b908 R12: 00003c8cc966d3c0\u000a[ 20.250896] R13: 00003c8cc9e280c0 R14: 0000000000000000 R15: 0000000000000000\u000a\u000aSigned-off-by: Alex Levin \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "c2784e57271e415bca7b6ae8caedb87ad27724a8", "msg" : "ASoC: Intel: sst: fix kmalloc call with wrong flags", "paths" : [ { "editType" : "edit", "file" : "sound/soc/intel/atom/sst/sst_pvt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/platform/x86/asus-nb-wmi.c", "drivers/platform/x86/asus-wmi.h", "drivers/platform/x86/asus-wmi.c" ], "commitId" : "f1585ebaee71e67e8f46d6d640df9d00fb0c4b70", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "platform/x86: asus-wmi: Only Tell EC the OS will handle display hotkeys from asus_nb_wmi\u000a\u000a[ Upstream commit 401fee8195d401b2b94dee57383f627050724d5b ]\u000a\u000aCommit 78f3ac76d9e5 (\"platform/x86: asus-wmi: Tell the EC the OS will\u000ahandle the display off hotkey\") causes the backlight to be permanently off\u000aon various EeePC laptop models using the eeepc-wmi driver (Asus EeePC\u000a1015BX, Asus EeePC 1025C).\u000a\u000aThe asus_wmi_set_devstate(ASUS_WMI_DEVID_BACKLIGHT, 2, NULL) call added\u000aby that commit is made conditional in this commit and only enabled in\u000athe quirk_entry structs in the asus-nb-wmi driver fixing the broken\u000adisplay / backlight on various EeePC laptop models.\u000a\u000aCc: João Paulo Rechi Vita \u000aFixes: 78f3ac76d9e5 (\"platform/x86: asus-wmi: Tell the EC the OS will handle the display off hotkey\")\u000aSigned-off-by: Hans de Goede \u000aSigned-off-by: Andy Shevchenko \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "f1585ebaee71e67e8f46d6d640df9d00fb0c4b70", "msg" : "platform/x86: asus-wmi: Only Tell EC the OS will handle display hotkeys from asus_nb_wmi", "paths" : [ { "editType" : "edit", "file" : "drivers/platform/x86/asus-wmi.c" }, { "editType" : "edit", "file" : "drivers/platform/x86/asus-wmi.h" }, { "editType" : "edit", "file" : "drivers/platform/x86/asus-nb-wmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/platform/x86/intel-vbtn.c" ], "commitId" : "b551985b981f3a1e0ca17374eba340d9df2d79a3", "timestamp" : 1562745146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "platform/x86: intel-vbtn: Report switch events when event wakes device\u000a\u000a[ Upstream commit cb1921b17adbe6509538098ac431033378cd7165 ]\u000a\u000aWhen a switch event, such as tablet mode/laptop mode or docked/undocked,\u000awakes a device make sure that the value of the swich is reported.\u000aWithout when a device is put in tablet mode from laptop mode when it is\u000asuspended or vice versa the device will wake up but mode will be\u000aincorrect.\u000a\u000aTested by suspending a device in laptop mode and putting it in tablet\u000amode, the device resumes and is in tablet mode. When suspending the\u000adevice in tablet mode and putting it in laptop mode the device resumes\u000aand is in laptop mode.\u000a\u000aSigned-off-by: Mathew King \u000aReviewed-by: Jett Rink \u000aReviewed-by: Mario Limonciello \u000aSigned-off-by: Andy Shevchenko \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:26 +0200", "id" : "b551985b981f3a1e0ca17374eba340d9df2d79a3", "msg" : "platform/x86: intel-vbtn: Report switch events when event wakes device", "paths" : [ { "editType" : "edit", "file" : "drivers/platform/x86/intel-vbtn.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/platform/x86/mlx-platform.c" ], "commitId" : "f3f865f565fa267d8e12decea5903d2fad30e8a9", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "platform/x86: mlx-platform: Fix parent device in i2c-mux-reg device registration\u000a\u000a[ Upstream commit 160da20b254dd4bfc5828f12c208fa831ad4be6c ]\u000a\u000aFix the issue found while running kernel with the option\u000aCONFIG_DEBUG_TEST_DRIVER_REMOVE.\u000aDriver 'mlx-platform' registers 'i2c_mlxcpld' device and then registers\u000afew underlying 'i2c-mux-reg' devices:\u000a\u0009priv->pdev_i2c = platform_device_register_simple(\"i2c_mlxcpld\", nr,\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 NULL, 0);\u000a\u0009...\u000a\u0009for (i = 0; i < ARRAY_SIZE(mlxplat_mux_data); i++) {\u000a\u0009\u0009priv->pdev_mux[i] = platform_device_register_resndata(\u000a\u0009\u0009\u0009\u0009\u0009\u0009&mlxplat_dev->dev,\u000a\u0009\u0009\u0009\u0009\u0009\u0009\"i2c-mux-reg\", i, NULL,\u000a\u0009\u0009\u0009\u0009\u0009\u00090, &mlxplat_mux_data[i],\u000a\u0009\u0009\u0009\u0009\u0009\u0009sizeof(mlxplat_mux_data[i]));\u000a\u000aBut actual parent of \"i2c-mux-reg\" device is priv->pdev_i2c->dev and\u000anot mlxplat_dev->dev.\u000aPatch fixes parent device parameter in a call to\u000aplatform_device_register_resndata() for \"i2c-mux-reg\".\u000a\u000aIt solves the race during initialization flow while 'i2c_mlxcpld.1' is\u000aremoving after probe, while 'i2c-mux-reg.0' is still in probing flow:\u000a'i2c_mlxcpld.1'\u0009flow:\u0009probe -> remove -> probe.\u000a'i2c-mux-reg.0'\u0009flow:\u0009\u0009 probe -> ...\u000a\u000a[ 12:621096] Registering platform device 'i2c_mlxcpld.1'. Parent at platform\u000a[ 12:621117] device: 'i2c_mlxcpld.1': device_add\u000a[ 12:621155] bus: 'platform': add device i2c_mlxcpld.1\u000a[ 12:621384] Registering platform device 'i2c-mux-reg.0'. Parent at mlxplat\u000a[ 12:621395] device: 'i2c-mux-reg.0': device_add\u000a[ 12:621425] bus: 'platform': add device i2c-mux-reg.0\u000a[ 12:621806] Registering platform device 'i2c-mux-reg.1'. Parent at mlxplat\u000a[ 12:621828] device: 'i2c-mux-reg.1': device_add\u000a[ 12:621892] bus: 'platform': add device i2c-mux-reg.1\u000a[ 12:621906] bus: 'platform': add driver i2c_mlxcpld\u000a[ 12:621996] bus: 'platform': driver_probe_device: matched device i2c_mlxcpld.1 with driver i2c_mlxcpld\u000a[ 12:622003] bus: 'platform': really_probe: probing driver i2c_mlxcpld with device i2c_mlxcpld.1\u000a[ 12:622100] i2c_mlxcpld i2c_mlxcpld.1: no default pinctrl state\u000a[ 12:622293] device: 'i2c-1': device_add\u000a[ 12:627280] bus: 'i2c': add device i2c-1\u000a[ 12:627692] device: 'i2c-1': device_add\u000a[ 12.629639] bus: 'platform': add driver i2c-mux-reg\u000a[ 12.629718] bus: 'platform': driver_probe_device: matched device i2c-mux-reg.0 with driver i2c-mux-reg\u000a[ 12.629723] bus: 'platform': really_probe: probing driver i2c-mux-reg with device i2c-mux-reg.0\u000a[ 12.629818] i2c-mux-reg i2c-mux-reg.0: no default pinctrl state\u000a[ 12.629981] platform i2c-mux-reg.0: Driver i2c-mux-reg requests probe deferral\u000a[ 12.629986] platform i2c-mux-reg.0: Added to deferred list\u000a[ 12.629992] bus: 'platform': driver_probe_device: matched device i2c-mux-reg.1 with driver i2c-mux-reg\u000a[ 12.629997] bus: 'platform': really_probe: probing driver i2c-mux-reg with device i2c-mux-reg.1\u000a[ 12.630091] i2c-mux-reg i2c-mux-reg.1: no default pinctrl state\u000a[ 12.630247] platform i2c-mux-reg.1: Driver i2c-mux-reg requests probe deferral\u000a[ 12.630252] platform i2c-mux-reg.1: Added to deferred list\u000a[ 12.640892] devices_kset: Moving i2c-mux-reg.0 to end of list\u000a[ 12.640900] platform i2c-mux-reg.0: Retrying from deferred list\u000a[ 12.640911] bus: 'platform': driver_probe_device: matched device i2c-mux-reg.0 with driver i2c-mux-reg\u000a[ 12.640919] bus: 'platform': really_probe: probing driver i2c-mux-reg with device i2c-mux-reg.0\u000a[ 12.640999] i2c-mux-reg i2c-mux-reg.0: no default pinctrl state\u000a[ 12.641177] platform i2c-mux-reg.0: Driver i2c-mux-reg requests probe deferral\u000a[ 12.641187] platform i2c-mux-reg.0: Added to deferred list\u000a[ 12.641198] devices_kset: Moving i2c-mux-reg.1 to end of list\u000a[ 12.641219] platform i2c-mux-reg.1: Retrying from deferred list\u000a[ 12.641237] bus: 'platform': driver_probe_device: matched device i2c-mux-reg.1 with driver i2c-mux-reg\u000a[ 12.641247] bus: 'platform': really_probe: probing driver i2c-mux-reg with device i2c-mux-reg.1\u000a[ 12.641331] i2c-mux-reg i2c-mux-reg.1: no default pinctrl state\u000a[ 12.641465] platform i2c-mux-reg.1: Driver i2c-mux-reg requests probe deferral\u000a[ 12.641469] platform i2c-mux-reg.1: Added to deferred list\u000a[ 12.646427] device: 'i2c-1': device_add\u000a[ 12.646647] bus: 'i2c': add device i2c-1\u000a[ 12.647104] device: 'i2c-1': device_add\u000a[ 12.669231] devices_kset: Moving i2c-mux-reg.0 to end of list\u000a[ 12.669240] platform i2c-mux-reg.0: Retrying from deferred list\u000a[ 12.669258] bus: 'platform': driver_probe_device: matched device i2c-mux-reg.0 with driver i2c-mux-reg\u000a[ 12.669263] bus: 'platform': really_probe: probing driver i2c-mux-reg with device i2c-mux-reg.0\u000a[ 12.669343] i2c-mux-reg i2c-mux-reg.0: no default pinctrl state\u000a[ 12.669585] device: 'i2c-2': device_add\u000a[ 12.669795] bus: 'i2c': add device i2c-2\u000a[ 12.670201] device: 'i2c-2': device_add\u000a[ 12.671427] i2c i2c-1: Added multiplexed i2c bus 2\u000a[ 12.671514] device: 'i2c-3': device_add\u000a[ 12.671724] bus: 'i2c': add device i2c-3\u000a[ 12.672136] device: 'i2c-3': device_add\u000a[ 12.673378] i2c i2c-1: Added multiplexed i2c bus 3\u000a[ 12.673472] device: 'i2c-4': device_add\u000a[ 12.673676] bus: 'i2c': add device i2c-4\u000a[ 12.674060] device: 'i2c-4': device_add\u000a[ 12.675861] i2c i2c-1: Added multiplexed i2c bus 4\u000a[ 12.675941] device: 'i2c-5': device_add\u000a[ 12.676150] bus: 'i2c': add device i2c-5\u000a[ 12.676550] device: 'i2c-5': device_add\u000a[ 12.678103] i2c i2c-1: Added multiplexed i2c bus 5\u000a[ 12.678193] device: 'i2c-6': device_add\u000a[ 12.678395] bus: 'i2c': add device i2c-6\u000a[ 12.678774] device: 'i2c-6': device_add\u000a[ 12.679969] i2c i2c-1: Added multiplexed i2c bus 6\u000a[ 12.680065] device: 'i2c-7': device_add\u000a[ 12.680275] bus: 'i2c': add device i2c-7\u000a[ 12.680913] device: 'i2c-7': device_add\u000a[ 12.682506] i2c i2c-1: Added multiplexed i2c bus 7\u000a[ 12.682600] device: 'i2c-8': device_add\u000a[ 12.682808] bus: 'i2c': add device i2c-8\u000a[ 12.683189] device: 'i2c-8': device_add\u000a[ 12.683907] device: 'i2c-1': device_unregister\u000a[ 12.683945] device: 'i2c-1': device_unregister\u000a[ 12.684387] device: 'i2c-1': device_create_release\u000a[ 12.684536] bus: 'i2c': remove device i2c-1\u000a[ 12.686019] i2c i2c-8: Failed to create compatibility class link\u000a[ 12.686086] ------------[ cut here ]------------\u000a[ 12.686087] can't create symlink to mux device\u000a[ 12.686224] Workqueue: events deferred_probe_work_func\u000a[ 12.686135] WARNING: CPU: 7 PID: 436 at drivers/i2c/i2c-mux.c:416 i2c_mux_add_adapter+0x729/0x7d0 [i2c_mux]\u000a[ 12.686232] RIP: 0010:i2c_mux_add_adapter+0x729/0x7d0 [i2c_mux]\u000a[ 0x190/0x190 [i2c_mux]\u000a[ 12.686300] ? i2c_mux_alloc+0xac/0x110 [i2c_mux]\u000a[ 12.686306] ? i2c_mux_reg_set+0x200/0x200 [i2c_mux_reg]\u000a[ 12.686313] i2c_mux_reg_probe+0x22c/0x731 [i2c_mux_reg]\u000a[ 12.686322] ? i2c_mux_reg_deselect+0x60/0x60 [i2c_mux_reg]\u000a[ 12.686346] platform_drv_probe+0xa8/0x110\u000a[ 12.686351] really_probe+0x185/0x720\u000a[ 12.686358] driver_probe_device+0xdf/0x1f0\u000a...\u000a[ 12.686522] i2c i2c-1: Added multiplexed i2c bus 8\u000a[ 12.686621] device: 'i2c-9': device_add\u000a[ 12.686626] kobject_add_internal failed for i2c-9 (error: -2 parent: i2c-1)\u000a[ 12.694729] i2c-core: adapter 'i2c-1-mux (chan_id 8)': can't register device (-2)\u000a[ 12.705726] i2c i2c-1: failed to add mux-adapter 8 as bus 9 (error=-2)\u000a[ 12.714494] device: 'i2c-8': device_unregister\u000a[ 12.714537] device: 'i2c-8': device_unregister\u000a\u000aFixes: 6613d18e9038 (\"platform/x86: mlx-platform: Move module from arch/x86\")\u000aSigned-off-by: Vadim Pasternak \u000aSigned-off-by: Andy Shevchenko \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "f3f865f565fa267d8e12decea5903d2fad30e8a9", "msg" : "platform/x86: mlx-platform: Fix parent device in i2c-mux-reg device registration", "paths" : [ { "editType" : "edit", "file" : "drivers/platform/x86/mlx-platform.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/platform/mellanox/mlxreg-hotplug.c" ], "commitId" : "3d76f277b103354de038ab1c5ec2d1d7a9a579d7", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "platform/mellanox: mlxreg-hotplug: Add devm_free_irq call to remove flow\u000a\u000a[ Upstream commit 8c2eb7b6468ad4aa5600aed01aa0715f921a3f8b ]\u000a\u000aAdd devm_free_irq() call to mlxreg-hotplug remove() for clean release\u000aof devices irq resource. Fix debugobjects warning triggered by rmmod\u000aIt prevents of use-after-free memory, related to\u000amlxreg_hotplug_work_handler.\u000a\u000aIssue has been reported as debugobjects warning triggered by\u000a'rmmod mlxtreg-hotplug' flow, while running kernel with\u000aCONFIG_DEBUG_OBJECTS* options.\u000a\u000a[ 2489.623551] ODEBUG: free active (active state 0) object type: work_struct hint: mlxreg_hotplug_work_handler+0x0/0x7f0 [mlxreg_hotplug]\u000a[ 2489.637097] WARNING: CPU: 5 PID: 3924 at lib/debugobjects.c:328 debug_print_object+0xfe/0x180\u000a[ 2489.637165] RIP: 0010:debug_print_object+0xfe/0x180\u000a?\u000a[ 2489.637214] Call Trace:\u000a[ 2489.637225] __debug_check_no_obj_freed+0x25e/0x320\u000a[ 2489.637231] kfree+0x82/0x110\u000a[ 2489.637238] release_nodes+0x33c/0x4e0\u000a[ 2489.637242] ? devres_remove_group+0x1b0/0x1b0\u000a[ 2489.637247] device_release_driver_internal+0x146/0x270\u000a[ 2489.637251] driver_detach+0x73/0xe0\u000a[ 2489.637254] bus_remove_driver+0xa1/0x170\u000a[ 2489.637261] __x64_sys_delete_module+0x29e/0x320\u000a[ 2489.637265] ? __ia32_sys_delete_module+0x320/0x320\u000a[ 2489.637268] ? blkcg_exit_queue+0x20/0x20\u000a[ 2489.637273] ? task_work_run+0x7d/0x100\u000a[ 2489.637278] ? exit_to_usermode_loop+0x5b/0xf0\u000a[ 2489.637281] do_syscall_64+0x73/0x160\u000a[ 2489.637287] entry_SYSCALL_64_after_hwframe+0x44/0xa9\u000a[ 2489.637290] RIP: 0033:0x7f95c3596fd7\u000a\u000aThe difference in release flow with and with no devm_free_irq is listed\u000abelow:\u000a\u000abus: 'platform': remove driver mlxreg-hotplug\u000a mlxreg_hotplug_remove(start)\u000a\u0009\u0009\u0009\u0009\u0009-> devm_free_irq (with new code)\u000a mlxreg_hotplug_remove (end)\u000a release_nodes (start)\u000a mlxreg-hotplug: DEVRES REL devm_hwmon_release (8 bytes)\u000a device: 'hwmon3': device_unregister\u000a PM: Removing info for No Bus:hwmon3\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (88 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (6 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (5 bytes)\u000a mlxreg-hotplug: DEVRES REL devm_irq_release (16 bytes) (no new code)\u000a mlxreg-hotplug: DEVRES REL devm_kzalloc_release (1376 bytes)\u000a ------------[ cut here ]------------ (no new code):\u000a ODEBUG: free active (active state 0) object type: work_struct hint: mlxreg_hotplug_work_handler\u000a\u000a release_nodes(end)\u000adriver: 'mlxreg-hotplug': driver_release\u000a\u000aFixes: 1f976f6978bf (\"platform/x86: Move Mellanox platform hotplug driver to platform/mellanox\")\u000aSigned-off-by: Vadim Pasternak \u000aSigned-off-by: Andy Shevchenko \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "3d76f277b103354de038ab1c5ec2d1d7a9a579d7", "msg" : "platform/mellanox: mlxreg-hotplug: Add devm_free_irq call to remove flow", "paths" : [ { "editType" : "edit", "file" : "drivers/platform/mellanox/mlxreg-hotplug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/i2c/busses/i2c-pca-platform.c" ], "commitId" : "60bc55dea8053f69cf3677adcc7a23f94e4b3c5c", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "i2c: pca-platform: Fix GPIO lookup code\u000a\u000a[ Upstream commit a0cac264a86fbf4d6cb201fbbb73c1d335e3248a ]\u000a\u000aThe devm_gpiod_request_gpiod() call will add \"-gpios\" to\u000aany passed connection ID before looking it up.\u000a\u000aI do not think the reset GPIO on this platform is named\u000a\"reset-gpios-gpios\" but rather \"reset-gpios\" in the device\u000atree, so fix this up so that we get a proper reset GPIO\u000ahandle.\u000a\u000aAlso drop the inclusion of the legacy GPIO header.\u000a\u000aFixes: 0e8ce93bdceb (\"i2c: pca-platform: add devicetree awareness\")\u000aSigned-off-by: Linus Walleij \u000aReviewed-by: Chris Packham \u000aSigned-off-by: Wolfram Sang \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "60bc55dea8053f69cf3677adcc7a23f94e4b3c5c", "msg" : "i2c: pca-platform: Fix GPIO lookup code", "paths" : [ { "editType" : "edit", "file" : "drivers/i2c/busses/i2c-pca-platform.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/include/asm/tlbflush.h" ], "commitId" : "e2beb74acae6e8a036b3b6a2dc28d577e1c07df0", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: tlbflush: Ensure start/end of address range are aligned to stride\u000a\u000a[ Upstream commit 01d57485fcdb9f9101a10a18e32d5f8b023cab86 ]\u000a\u000aSince commit 3d65b6bbc01e (\"arm64: tlbi: Set MAX_TLBI_OPS to\u000aPTRS_PER_PTE\"), we resort to per-ASID invalidation when attempting to\u000aperform more than PTRS_PER_PTE invalidation instructions in a single\u000acall to __flush_tlb_range(). Whilst this is beneficial, the mmu_gather\u000acode does not ensure that the end address of the range is rounded-up\u000ato the stride when freeing intermediate page tables in pXX_free_tlb(),\u000awhich defeats our range checking.\u000a\u000aAlign the bounds passed into __flush_tlb_range().\u000a\u000aCc: Catalin Marinas \u000aCc: Peter Zijlstra \u000aReported-by: Hanjun Guo \u000aTested-by: Hanjun Guo \u000aReviewed-by: Hanjun Guo \u000aSigned-off-by: Will Deacon \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "e2beb74acae6e8a036b3b6a2dc28d577e1c07df0", "msg" : "arm64: tlbflush: Ensure start/end of address range are aligned to stride", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/include/asm/tlbflush.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/cgroup/cpuset.c" ], "commitId" : "8f4b554b089bb1a74191f7becd7d1822586497a8", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cpuset: restore sanity to cpuset_cpus_allowed_fallback()\u000a\u000a[ Upstream commit d477f8c202d1f0d4791ab1263ca7657bbe5cf79e ]\u000a\u000aIn the case that a process is constrained by taskset(1) (i.e.\u000asched_setaffinity(2)) to a subset of available cpus, and all of those are\u000asubsequently offlined, the scheduler will set tsk->cpus_allowed to\u000athe current value of task_cs(tsk)->effective_cpus.\u000a\u000aThis is done via a call to do_set_cpus_allowed() in the context of\u000acpuset_cpus_allowed_fallback() made by the scheduler when this case is\u000adetected. This is the only call made to cpuset_cpus_allowed_fallback()\u000ain the latest mainline kernel.\u000a\u000aHowever, this is not sane behavior.\u000a\u000aI will demonstrate this on a system running the latest upstream kernel\u000awith the following initial configuration:\u000a\u000a\u0009# grep -i cpu /proc/$$/status\u000a\u0009Cpus_allowed:\u0009ffffffff,fffffff\u000a\u0009Cpus_allowed_list:\u00090-63\u000a\u000a(Where cpus 32-63 are provided via smt.)\u000a\u000aIf we limit our current shell process to cpu2 only and then offline it\u000aand reonline it:\u000a\u000a\u0009# taskset -p 4 $$\u000a\u0009pid 2272's current affinity mask: ffffffffffffffff\u000a\u0009pid 2272's new affinity mask: 4\u000a\u000a\u0009# echo off > /sys/devices/system/cpu/cpu2/online\u000a\u0009# dmesg | tail -3\u000a\u0009[ 2195.866089] process 2272 (bash) no longer affine to cpu2\u000a\u0009[ 2195.872700] IRQ 114: no longer affine to CPU2\u000a\u0009[ 2195.879128] smpboot: CPU 2 is now offline\u000a\u000a\u0009# echo on > /sys/devices/system/cpu/cpu2/online\u000a\u0009# dmesg | tail -1\u000a\u0009[ 2617.043572] smpboot: Booting Node 0 Processor 2 APIC 0x4\u000a\u000aWe see that our current process now has an affinity mask containing\u000aevery cpu available on the system _except_ the one we originally\u000aconstrained it to:\u000a\u000a\u0009# grep -i cpu /proc/$$/status\u000a\u0009Cpus_allowed: ffffffff,fffffffb\u000a\u0009Cpus_allowed_list: 0-1,3-63\u000a\u000aThis is not sane behavior, as the scheduler can now not only place the\u000aprocess on previously forbidden cpus, it can't even schedule it on\u000athe cpu it was originally constrained to!\u000a\u000aOther cases result in even more exotic affinity masks. Take for instance\u000aa process with an affinity mask containing only cpus provided by smt at\u000athe moment that smt is toggled, in a configuration such as the following:\u000a\u000a\u0009# taskset -p f000000000 $$\u000a\u0009# grep -i cpu /proc/$$/status\u000a\u0009Cpus_allowed:\u0009000000f0,00000000\u000a\u0009Cpus_allowed_list:\u000936-39\u000a\u000aA double toggle of smt results in the following behavior:\u000a\u000a\u0009# echo off > /sys/devices/system/cpu/smt/control\u000a\u0009# echo on > /sys/devices/system/cpu/smt/control\u000a\u0009# grep -i cpus /proc/$$/status\u000a\u0009Cpus_allowed:\u0009ffffff00,ffffffff\u000a\u0009Cpus_allowed_list:\u00090-31,40-63\u000a\u000aThis is even less sane than the previous case, as the new affinity mask\u000aexcludes all smt-provided cpus with ids less than those that were\u000apreviously in the affinity mask, as well as those that were actually in\u000athe mask.\u000a\u000aWith this patch applied, both of these cases end in the following state:\u000a\u000a\u0009# grep -i cpu /proc/$$/status\u000a\u0009Cpus_allowed:\u0009ffffffff,ffffffff\u000a\u0009Cpus_allowed_list:\u00090-63\u000a\u000aThe original policy is discarded. Though not ideal, it is the simplest way\u000ato restore sanity to this fallback case without reinventing the cpuset\u000awheel that rolls down the kernel just fine in cgroup v2. A user who wishes\u000afor the previous affinity mask to be restored in this fallback case can use\u000athat mechanism instead.\u000a\u000aThis patch modifies scheduler behavior by instead resetting the mask to\u000atask_cs(tsk)->cpus_allowed by default, and cpu_possible mask in legacy\u000amode. I tested the cases above on both modes.\u000a\u000aNote that the scheduler uses this fallback mechanism if and only if\u000a_every_ other valid avenue has been traveled, and it is the last resort\u000abefore calling BUG().\u000a\u000aSuggested-by: Waiman Long \u000aSuggested-by: Phil Auld \u000aSigned-off-by: Joel Savitz \u000aAcked-by: Phil Auld \u000aAcked-by: Waiman Long \u000aAcked-by: Peter Zijlstra (Intel) \u000aSigned-off-by: Tejun Heo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "8f4b554b089bb1a74191f7becd7d1822586497a8", "msg" : "cpuset: restore sanity to cpuset_cpus_allowed_fallback()", "paths" : [ { "editType" : "edit", "file" : "kernel/cgroup/cpuset.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "scripts/decode_stacktrace.sh" ], "commitId" : "80d567f799c18814c2065df840c74d76ded2fc3c", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scripts/decode_stacktrace.sh: prefix addr2line with $CROSS_COMPILE\u000a\u000a[ Upstream commit c04e32e911653442fc834be6e92e072aeebe01a1 ]\u000a\u000aAt least for ARM64 kernels compiled with the crosstoolchain from\u000aDebian/stretch or with the toolchain from kernel.org the line number is\u000anot decoded correctly by 'decode_stacktrace.sh':\u000a\u000a $ echo \"[ 136.513051] f1+0x0/0xc [kcrash]\" | \\\u000a CROSS_COMPILE=/opt/gcc-8.1.0-nolibc/aarch64-linux/bin/aarch64-linux- \\\u000a ./scripts/decode_stacktrace.sh /scratch/linux-arm64/vmlinux \\\u000a /scratch/linux-arm64 \\\u000a /nfs/debian/lib/modules/4.20.0-devel\u000a [ 136.513051] f1 (/linux/drivers/staging/kcrash/kcrash.c:68) kcrash\u000a\u000aIf addr2line from the toolchain is used the decoded line number is correct:\u000a\u000a [ 136.513051] f1 (/linux/drivers/staging/kcrash/kcrash.c:57) kcrash\u000a\u000aLink: http://lkml.kernel.org/r/20190527083425.3763-1-manut@linutronix.de\u000aSigned-off-by: Manuel Traut \u000aAcked-by: Konstantin Khlebnikov \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "80d567f799c18814c2065df840c74d76ded2fc3c", "msg" : "scripts/decode_stacktrace.sh: prefix addr2line with $CROSS_COMPILE", "paths" : [ { "editType" : "edit", "file" : "scripts/decode_stacktrace.sh" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "mm/mlock.c" ], "commitId" : "12006942792bba95db84339ab8cc7a28b525226d", "timestamp" : 1562745147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mm/mlock.c: change count_mm_mlocked_page_nr return type\u000a\u000a[ Upstream commit 0874bb49bb21bf24deda853e8bf61b8325e24bcb ]\u000a\u000aOn a 64-bit machine the value of \"vma->vm_end - vma->vm_start\" may be\u000anegative when using 32 bit ints and the \"count >> PAGE_SHIFT\"'s result\u000awill be wrong. So change the local variable and return value to\u000aunsigned long to fix the problem.\u000a\u000aLink: http://lkml.kernel.org/r/20190513023701.83056-1-swkhack@gmail.com\u000aFixes: 0cf2f6f6dc60 (\"mm: mlock: check against vma for actual mlock() size\")\u000aSigned-off-by: swkhack \u000aAcked-by: Michal Hocko \u000aReviewed-by: Andrew Morton \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:27 +0200", "id" : "12006942792bba95db84339ab8cc7a28b525226d", "msg" : "mm/mlock.c: change count_mm_mlocked_page_nr return type", "paths" : [ { "editType" : "edit", "file" : "mm/mlock.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/trace/ftrace.c" ], "commitId" : "b61581d5c2d3236645bf387bc418fe9310661f8b", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tracing: avoid build warning with HAVE_NOP_MCOUNT\u000a\u000a[ Upstream commit cbdaeaf050b730ea02e9ab4ff844ce54d85dbe1d ]\u000a\u000aSelecting HAVE_NOP_MCOUNT enables -mnop-mcount (if gcc supports it)\u000aand sets CC_USING_NOP_MCOUNT. Reuse __is_defined (which is suitable for\u000atesting CC_USING_* defines) to avoid conditional compilation and fix\u000athe following gcc 9 warning on s390:\u000a\u000akernel/trace/ftrace.c:2514:1: warning: ‘ftrace_code_disable’ defined\u000abut not used [-Wunused-function]\u000a\u000aLink: http://lkml.kernel.org/r/patch.git-1a82d13f33ac.your-ad-here.call-01559732716-ext-6629@work.hours\u000a\u000aFixes: 2f4df0017baed (\"tracing: Add -mcount-nop option support\")\u000aSigned-off-by: Vasily Gorbik \u000aSigned-off-by: Steven Rostedt (VMware) \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "b61581d5c2d3236645bf387bc418fe9310661f8b", "msg" : "tracing: avoid build warning with HAVE_NOP_MCOUNT", "paths" : [ { "editType" : "edit", "file" : "kernel/trace/ftrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/trace/ftrace.c", "kernel/livepatch/core.c" ], "commitId" : "77dd6d8ecc2e3bc3ee3d475671d77dc6d84d978b", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "module: Fix livepatch/ftrace module text permissions race\u000a\u000a[ Upstream commit 9f255b632bf12c4dd7fc31caee89aa991ef75176 ]\u000a\u000aIt's possible for livepatch and ftrace to be toggling a module's text\u000apermissions at the same time, resulting in the following panic:\u000a\u000a BUG: unable to handle page fault for address: ffffffffc005b1d9\u000a #PF: supervisor write access in kernel mode\u000a #PF: error_code(0x0003) - permissions violation\u000a PGD 3ea0c067 P4D 3ea0c067 PUD 3ea0e067 PMD 3cc13067 PTE 3b8a1061\u000a Oops: 0003 [#1] PREEMPT SMP PTI\u000a CPU: 1 PID: 453 Comm: insmod Tainted: G O K 5.2.0-rc1-a188339ca5 #1\u000a Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-20181126_142135-anatol 04/01/2014\u000a RIP: 0010:apply_relocate_add+0xbe/0x14c\u000a Code: fa 0b 74 21 48 83 fa 18 74 38 48 83 fa 0a 75 40 eb 08 48 83 38 00 74 33 eb 53 83 38 00 75 4e 89 08 89 c8 eb 0a 83 38 00 75 43 <89> 08 48 63 c1 48 39 c8 74 2e eb 48 83 38 00 75 32 48 29 c1 89 08\u000a RSP: 0018:ffffb223c00dbb10 EFLAGS: 00010246\u000a RAX: ffffffffc005b1d9 RBX: 0000000000000000 RCX: ffffffff8b200060\u000a RDX: 000000000000000b RSI: 0000004b0000000b RDI: ffff96bdfcd33000\u000a RBP: ffffb223c00dbb38 R08: ffffffffc005d040 R09: ffffffffc005c1f0\u000a R10: ffff96bdfcd33c40 R11: ffff96bdfcd33b80 R12: 0000000000000018\u000a R13: ffffffffc005c1f0 R14: ffffffffc005e708 R15: ffffffff8b2fbc74\u000a FS: 00007f5f447beba8(0000) GS:ffff96bdff900000(0000) knlGS:0000000000000000\u000a CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a CR2: ffffffffc005b1d9 CR3: 000000003cedc002 CR4: 0000000000360ea0\u000a DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\u000a DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\u000a Call Trace:\u000a klp_init_object_loaded+0x10f/0x219\u000a ? preempt_latency_start+0x21/0x57\u000a klp_enable_patch+0x662/0x809\u000a ? virt_to_head_page+0x3a/0x3c\u000a ? kfree+0x8c/0x126\u000a patch_init+0x2ed/0x1000 [livepatch_test02]\u000a ? 0xffffffffc0060000\u000a do_one_initcall+0x9f/0x1c5\u000a ? kmem_cache_alloc_trace+0xc4/0xd4\u000a ? do_init_module+0x27/0x210\u000a do_init_module+0x5f/0x210\u000a load_module+0x1c41/0x2290\u000a ? fsnotify_path+0x3b/0x42\u000a ? strstarts+0x2b/0x2b\u000a ? kernel_read+0x58/0x65\u000a __do_sys_finit_module+0x9f/0xc3\u000a ? __do_sys_finit_module+0x9f/0xc3\u000a __x64_sys_finit_module+0x1a/0x1c\u000a do_syscall_64+0x52/0x61\u000a entry_SYSCALL_64_after_hwframe+0x44/0xa9\u000a\u000aThe above panic occurs when loading two modules at the same time with\u000aftrace enabled, where at least one of the modules is a livepatch module:\u000a\u000aCPU0\u0009\u0009\u0009\u0009\u0009CPU1\u000aklp_enable_patch()\u000a klp_init_object_loaded()\u000a module_disable_ro()\u000a \u0009\u0009\u0009\u0009\u0009ftrace_module_enable()\u000a\u0009\u0009\u0009\u0009\u0009 ftrace_arch_code_modify_post_process()\u000a\u0009\u0009\u0009\u0009 \u0009 set_all_modules_text_ro()\u000a klp_write_object_relocations()\u000a apply_relocate_add()\u000a\u0009 *patches read-only code* - BOOM\u000a\u000aA similar race exists when toggling ftrace while loading a livepatch\u000amodule.\u000a\u000aFix it by ensuring that the livepatch and ftrace code patching\u000aoperations -- and their respective permissions changes -- are protected\u000aby the text_mutex.\u000a\u000aLink: http://lkml.kernel.org/r/ab43d56ab909469ac5d2520c5d944ad6d4abd476.1560474114.git.jpoimboe@redhat.com\u000a\u000aReported-by: Johannes Erdfelt \u000aFixes: 444d13ff10fb (\"modules: add ro_after_init support\")\u000aAcked-by: Jessica Yu \u000aReviewed-by: Petr Mladek \u000aReviewed-by: Miroslav Benes \u000aSigned-off-by: Josh Poimboeuf \u000aSigned-off-by: Steven Rostedt (VMware) \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "77dd6d8ecc2e3bc3ee3d475671d77dc6d84d978b", "msg" : "module: Fix livepatch/ftrace module text permissions race", "paths" : [ { "editType" : "edit", "file" : "kernel/trace/ftrace.c" }, { "editType" : "edit", "file" : "kernel/livepatch/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/trace/ftrace.c" ], "commitId" : "1c7c91a9a8f39f0ba7b2b6958f259748fa2f3c96", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper()\u000a\u000a[ Upstream commit 04e03d9a616c19a47178eaca835358610e63a1dd ]\u000a\u000aThe mapper may be NULL when called from register_ftrace_function_probe()\u000awith probe->data == NULL.\u000a\u000aThis issue can be reproduced as follow (it may be covered by compiler\u000aoptimization sometime):\u000a\u000a/ # cat /sys/kernel/debug/tracing/set_ftrace_filter\u000a#### all functions enabled ####\u000a/ # echo foo_bar:dump > /sys/kernel/debug/tracing/set_ftrace_filter\u000a[ 206.949100] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\u000a[ 206.952402] Mem abort info:\u000a[ 206.952819] ESR = 0x96000006\u000a[ 206.955326] Exception class = DABT (current EL), IL = 32 bits\u000a[ 206.955844] SET = 0, FnV = 0\u000a[ 206.956272] EA = 0, S1PTW = 0\u000a[ 206.956652] Data abort info:\u000a[ 206.957320] ISV = 0, ISS = 0x00000006\u000a[ 206.959271] CM = 0, WnR = 0\u000a[ 206.959938] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000419f3a000\u000a[ 206.960483] [0000000000000000] pgd=0000000411a87003, pud=0000000411a83003, pmd=0000000000000000\u000a[ 206.964953] Internal error: Oops: 96000006 [#1] SMP\u000a[ 206.971122] Dumping ftrace buffer:\u000a[ 206.973677] (ftrace buffer empty)\u000a[ 206.975258] Modules linked in:\u000a[ 206.976631] Process sh (pid: 281, stack limit = 0x(____ptrval____))\u000a[ 206.978449] CPU: 10 PID: 281 Comm: sh Not tainted 5.2.0-rc1+ #17\u000a[ 206.978955] Hardware name: linux,dummy-virt (DT)\u000a[ 206.979883] pstate: 60000005 (nZCv daif -PAN -UAO)\u000a[ 206.980499] pc : free_ftrace_func_mapper+0x2c/0x118\u000a[ 206.980874] lr : ftrace_count_free+0x68/0x80\u000a[ 206.982539] sp : ffff0000182f3ab0\u000a[ 206.983102] x29: ffff0000182f3ab0 x28: ffff8003d0ec1700\u000a[ 206.983632] x27: ffff000013054b40 x26: 0000000000000001\u000a[ 206.984000] x25: ffff00001385f000 x24: 0000000000000000\u000a[ 206.984394] x23: ffff000013453000 x22: ffff000013054000\u000a[ 206.984775] x21: 0000000000000000 x20: ffff00001385fe28\u000a[ 206.986575] x19: ffff000013872c30 x18: 0000000000000000\u000a[ 206.987111] x17: 0000000000000000 x16: 0000000000000000\u000a[ 206.987491] x15: ffffffffffffffb0 x14: 0000000000000000\u000a[ 206.987850] x13: 000000000017430e x12: 0000000000000580\u000a[ 206.988251] x11: 0000000000000000 x10: cccccccccccccccc\u000a[ 206.988740] x9 : 0000000000000000 x8 : ffff000013917550\u000a[ 206.990198] x7 : ffff000012fac2e8 x6 : ffff000012fac000\u000a[ 206.991008] x5 : ffff0000103da588 x4 : 0000000000000001\u000a[ 206.991395] x3 : 0000000000000001 x2 : ffff000013872a28\u000a[ 206.991771] x1 : 0000000000000000 x0 : 0000000000000000\u000a[ 206.992557] Call trace:\u000a[ 206.993101] free_ftrace_func_mapper+0x2c/0x118\u000a[ 206.994827] ftrace_count_free+0x68/0x80\u000a[ 206.995238] release_probe+0xfc/0x1d0\u000a[ 206.995555] register_ftrace_function_probe+0x4a8/0x868\u000a[ 206.995923] ftrace_trace_probe_callback.isra.4+0xb8/0x180\u000a[ 206.996330] ftrace_dump_callback+0x50/0x70\u000a[ 206.996663] ftrace_regex_write.isra.29+0x290/0x3a8\u000a[ 206.997157] ftrace_filter_write+0x44/0x60\u000a[ 206.998971] __vfs_write+0x64/0xf0\u000a[ 206.999285] vfs_write+0x14c/0x2f0\u000a[ 206.999591] ksys_write+0xbc/0x1b0\u000a[ 206.999888] __arm64_sys_write+0x3c/0x58\u000a[ 207.000246] el0_svc_common.constprop.0+0x408/0x5f0\u000a[ 207.000607] el0_svc_handler+0x144/0x1c8\u000a[ 207.000916] el0_svc+0x8/0xc\u000a[ 207.003699] Code: aa0003f8 a9025bf5 aa0103f5 f946ea80 (f9400303)\u000a[ 207.008388] ---[ end trace 7b6d11b5f542bdf1 ]---\u000a[ 207.010126] Kernel panic - not syncing: Fatal exception\u000a[ 207.011322] SMP: stopping secondary CPUs\u000a[ 207.013956] Dumping ftrace buffer:\u000a[ 207.014595] (ftrace buffer empty)\u000a[ 207.015632] Kernel Offset: disabled\u000a[ 207.017187] CPU features: 0x002,20006008\u000a[ 207.017985] Memory Limit: none\u000a[ 207.019825] ---[ end Kernel panic - not syncing: Fatal exception ]---\u000a\u000aLink: http://lkml.kernel.org/r/20190606031754.10798-1-liwei391@huawei.com\u000a\u000aSigned-off-by: Wei Li \u000aSigned-off-by: Steven Rostedt (VMware) \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "1c7c91a9a8f39f0ba7b2b6958f259748fa2f3c96", "msg" : "ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper()", "paths" : [ { "editType" : "edit", "file" : "kernel/trace/ftrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/ptrace.c" ], "commitId" : "49887fc3f2a7e6185777af3a9c96095aeb2bce1b", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME\u000a\u000acommit 6994eefb0053799d2e07cd140df6c2ea106c41ee upstream.\u000a\u000aFix two issues:\u000a\u000aWhen called for PTRACE_TRACEME, ptrace_link() would obtain an RCU\u000areference to the parent's objective credentials, then give that pointer\u000ato get_cred(). However, the object lifetime rules for things like\u000astruct cred do not permit unconditionally turning an RCU reference into\u000aa stable reference.\u000a\u000aPTRACE_TRACEME records the parent's credentials as if the parent was\u000aacting as the subject, but that's not the case. If a malicious\u000aunprivileged child uses PTRACE_TRACEME and the parent is privileged, and\u000aat a later point, the parent process becomes attacker-controlled\u000a(because it drops privileges and calls execve()), the attacker ends up\u000awith control over two processes with a privileged ptrace relationship,\u000awhich can be abused to ptrace a suid binary and obtain root privileges.\u000a\u000aFix both of these by always recording the credentials of the process\u000athat is requesting the creation of the ptrace relationship:\u000acurrent_cred() can't change under us, and current is the proper subject\u000afor access control.\u000a\u000aThis change is theoretically userspace-visible, but I am not aware of\u000aany code that it will actually break.\u000a\u000aFixes: 64b875f7ac8a (\"ptrace: Capture the ptracer's creds not PT_PTRACE_CAP\")\u000aSigned-off-by: Jann Horn \u000aAcked-by: Oleg Nesterov \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "49887fc3f2a7e6185777af3a9c96095aeb2bce1b", "msg" : "ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME", "paths" : [ { "editType" : "edit", "file" : "kernel/ptrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/crypto_user_base.c" ], "commitId" : "5781d162ec7de101d7ea41afaf8cf0b741fecb5e", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: user - prevent operating on larval algorithms\u000a\u000acommit 21d4120ec6f5b5992b01b96ac484701163917b63 upstream.\u000a\u000aMichal Suchanek reported [1] that running the pcrypt_aead01 test from\u000aLTP [2] in a loop and holding Ctrl-C causes a NULL dereference of\u000aalg->cra_users.next in crypto_remove_spawns(), via crypto_del_alg().\u000aThe test repeatedly uses CRYPTO_MSG_NEWALG and CRYPTO_MSG_DELALG.\u000a\u000aThe crash occurs when the instance that CRYPTO_MSG_DELALG is trying to\u000aunregister isn't a real registered algorithm, but rather is a \"test\u000alarval\", which is a special \"algorithm\" added to the algorithms list\u000awhile the real algorithm is still being tested. Larvals don't have\u000ainitialized cra_users, so that causes the crash. Normally pcrypt_aead01\u000adoesn't trigger this because CRYPTO_MSG_NEWALG waits for the algorithm\u000ato be tested; however, CRYPTO_MSG_NEWALG returns early when interrupted.\u000a\u000aEverything else in the \"crypto user configuration\" API has this same bug\u000atoo, i.e. it inappropriately allows operating on larval algorithms\u000a(though it doesn't look like the other cases can cause a crash).\u000a\u000aFix this by making crypto_alg_match() exclude larval algorithms.\u000a\u000a[1] https://lkml.kernel.org/r/20190625071624.27039-1-msuchanek@suse.de\u000a[2] https://github.com/linux-test-project/ltp/blob/20190517/testcases/kernel/crypto/pcrypt_aead01.c\u000a\u000aReported-by: Michal Suchanek \u000aFixes: a38f7907b926 (\"crypto: Add userspace configuration API\")\u000aCc: # v3.2+\u000aCc: Steffen Klassert \u000aSigned-off-by: Eric Biggers \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "5781d162ec7de101d7ea41afaf8cf0b741fecb5e", "msg" : "crypto: user - prevent operating on larval algorithms", "paths" : [ { "editType" : "edit", "file" : "crypto/crypto_user_base.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/cryptd.c" ], "commitId" : "5e961e899aee3488acc61d895dcc4048190736aa", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: cryptd - Fix skcipher instance memory leak\u000a\u000acommit 1a0fad630e0b7cff38e7691b28b0517cfbb0633f upstream.\u000a\u000acryptd_skcipher_free() fails to free the struct skcipher_instance\u000aallocated in cryptd_create_skcipher(), leading to a memory leak. This\u000ais detected by kmemleak on bootup on ARM64 platforms:\u000a\u000a unreferenced object 0xffff80003377b180 (size 1024):\u000a comm \"cryptomgr_probe\", pid 822, jiffies 4294894830 (age 52.760s)\u000a backtrace:\u000a kmem_cache_alloc_trace+0x270/0x2d0\u000a cryptd_create+0x990/0x124c\u000a cryptomgr_probe+0x5c/0x1e8\u000a kthread+0x258/0x318\u000a ret_from_fork+0x10/0x1c\u000a\u000aFixes: 4e0958d19bd8 (\"crypto: cryptd - Add support for skcipher\")\u000aCc: \u000aSigned-off-by: Vincent Whitchurch \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "5e961e899aee3488acc61d895dcc4048190736aa", "msg" : "crypto: cryptd - Fix skcipher instance memory leak", "paths" : [ { "editType" : "edit", "file" : "crypto/cryptd.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/core/seq/oss/seq_oss_ioctl.c", "sound/core/seq/oss/seq_oss_rw.c" ], "commitId" : "ff487e21a8a7121828c01cd005928e1f1407e055", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: seq: fix incorrect order of dest_client/dest_ports arguments\u000a\u000acommit c3ea60c231446663afd6ea1054da6b7f830855ca upstream.\u000a\u000aThere are two occurrances of a call to snd_seq_oss_fill_addr where\u000athe dest_client and dest_port arguments are in the wrong order. Fix\u000athis by swapping them around.\u000a\u000aAddresses-Coverity: (\"Arguments in wrong order\")\u000aSigned-off-by: Colin Ian King \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "ff487e21a8a7121828c01cd005928e1f1407e055", "msg" : "ALSA: seq: fix incorrect order of dest_client/dest_ports arguments", "paths" : [ { "editType" : "edit", "file" : "sound/core/seq/oss/seq_oss_ioctl.c" }, { "editType" : "edit", "file" : "sound/core/seq/oss/seq_oss_rw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/firewire/amdtp-am824.c" ], "commitId" : "139b5516cb45cc0560dec1f61a61ad14d8445e77", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: firewire-lib/fireworks: fix miss detection of received MIDI messages\u000a\u000acommit 7fbd1753b64eafe21cf842348a40a691d0dee440 upstream.\u000a\u000aIn IEC 61883-6, 8 MIDI data streams are multiplexed into single\u000aMIDI conformant data channel. The index of stream is calculated by\u000amodulo 8 of the value of data block counter.\u000a\u000aIn fireworks, the value of data block counter in CIP header has a quirk\u000awith firmware version v5.0.0, v5.7.3 and v5.8.0. This brings ALSA\u000aIEC 61883-1/6 packet streaming engine to miss detection of MIDI\u000amessages.\u000a\u000aThis commit fixes the miss detection to modify the value of data block\u000acounter for the modulo calculation.\u000a\u000aFor maintainers, this bug exists since a commit 18f5ed365d3f (\"ALSA:\u000afireworks/firewire-lib: add support for recent firmware quirk\") in Linux\u000akernel v4.2. There're many changes since the commit. This fix can be\u000abackported to Linux kernel v4.4 or later. I tagged a base commit to the\u000abackport for your convenience.\u000a\u000aBesides, my work for Linux kernel v5.3 brings heavy code refactoring and\u000asome structure members are renamed in 'sound/firewire/amdtp-stream.h'.\u000aThe content of this patch brings conflict when merging -rc tree with\u000athis patch and the latest tree. I request maintainers to solve the\u000aconflict to replace 'tx_first_dbc' with 'ctx_data.tx.first_dbc'.\u000a\u000aFixes: df075feefbd3 (\"ALSA: firewire-lib: complete AM824 data block processing layer\")\u000aCc: # v4.4+\u000aSigned-off-by: Takashi Sakamoto \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "139b5516cb45cc0560dec1f61a61ad14d8445e77", "msg" : "ALSA: firewire-lib/fireworks: fix miss detection of received MIDI messages", "paths" : [ { "editType" : "edit", "file" : "sound/firewire/amdtp-am824.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/usb/line6/pcm.c" ], "commitId" : "308e490d61bcca5a1114372550edc19187051ccb", "timestamp" : 1562745148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: line6: Fix write on zero-sized buffer\u000a\u000acommit 3450121997ce872eb7f1248417225827ea249710 upstream.\u000a\u000aLINE6 drivers allocate the buffers based on the value returned from\u000ausb_maxpacket() calls. The manipulated device may return zero for\u000athis, and this results in the kmalloc() with zero size (and it may\u000asucceed) while the other part of the driver code writes the packet\u000adata with the fixed size -- which eventually overwrites.\u000a\u000aThis patch adds a simple sanity check for the invalid buffer size for\u000aavoiding that problem.\u000a\u000aReported-by: syzbot+219f00fb49874dcaea17@syzkaller.appspotmail.com\u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:28 +0200", "id" : "308e490d61bcca5a1114372550edc19187051ccb", "msg" : "ALSA: line6: Fix write on zero-sized buffer", "paths" : [ { "editType" : "edit", "file" : "sound/usb/line6/pcm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/usb/mixer_quirks.c" ], "commitId" : "97001b394f87e5250bbdd7a488faf8bf6d9d5b1f", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: usb-audio: fix sign unintended sign extension on left shifts\u000a\u000acommit 2acf5a3e6e9371e63c9e4ff54d84d08f630467a0 upstream.\u000a\u000aThere are a couple of left shifts of unsigned 8 bit values that\u000afirst get promoted to signed ints and hence get sign extended\u000aon the shift if the top bit of the 8 bit values are set. Fix\u000athis by casting the 8 bit values to unsigned ints to stop the\u000aunintentional sign extension.\u000a\u000aAddresses-Coverity: (\"Unintended sign extension\")\u000aSigned-off-by: Colin Ian King \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "97001b394f87e5250bbdd7a488faf8bf6d9d5b1f", "msg" : "ALSA: usb-audio: fix sign unintended sign extension on left shifts", "paths" : [ { "editType" : "edit", "file" : "sound/usb/mixer_quirks.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_realtek.c" ], "commitId" : "32a4cd4c8bea773ea3d741e0e1e1abae9ced298d", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/realtek: Add quirks for several Clevo notebook barebones\u000a\u000acommit 503d90b30602a3295978e46d844ccc8167400fe6 upstream.\u000a\u000aThis adds 4 SND_PCI_QUIRK(...) lines for several barebone models of the ODM\u000aClevo. The model names are written in regex syntax to describe/match all clevo\u000amodels that are similar enough and use the same PCI SSID that this fixup works\u000afor them.\u000a\u000aAdditionally the lines regarding SSID 0x96e1 and 0x97e1 didn't fix audio for the\u000aall our Clevo notebooks using these SSIDs (models Clevo P960* and P970*) since\u000aALC1220_FIXP_CLEVO_PB51ED_PINS swapped pins that are not necesarry to be\u000aswapped. This patch initiates ALC1220_FIXUP_CLEVO_P950 instead for these model\u000aand fixes the audio.\u000a\u000aFixes: 80690a276f44 (\"ALSA: hda/realtek - Add quirk for Tuxedo XC 1509\")\u000aSigned-off-by: Richard Sailer \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "32a4cd4c8bea773ea3d741e0e1e1abae9ced298d", "msg" : "ALSA: hda/realtek: Add quirks for several Clevo notebook barebones", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_realtek.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_realtek.c" ], "commitId" : "786db71da5e5af3c202ed41e9a8daccec890c83b", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/realtek - Change front mic location for Lenovo M710q\u000a\u000acommit bef33e19203dde434bcdf21c449e3fb4f06c2618 upstream.\u000a\u000aOn M710q Lenovo ThinkCentre machine, there are two front mics,\u000awe change the location for one of them to avoid conflicts.\u000a\u000aSigned-off-by: Dennis Wassenberg \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "786db71da5e5af3c202ed41e9a8daccec890c83b", "msg" : "ALSA: hda/realtek - Change front mic location for Lenovo M710q", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_realtek.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/dax.c" ], "commitId" : "7b6532ed7a6380b5c8e3d9c3a1fefff12469c5d8", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dax: Fix xarray entry association for mixed mappings\u000a\u000acommit 1571c029a2ff289683ddb0a32253850363bcb8a7 upstream.\u000a\u000aWhen inserting entry into xarray, we store mapping and index in\u000acorresponding struct pages for memory error handling. When it happened\u000athat one process was mapping file at PMD granularity while another\u000aprocess at PTE granularity, we could wrongly deassociate PMD range and\u000athen reassociate PTE range leaving the rest of struct pages in PMD range\u000awithout mapping information which could later cause missed notifications\u000aabout memory errors. Fix the problem by calling the association /\u000adeassociation code if and only if we are really going to update the\u000axarray (deassociating and associating zero or empty entries is just\u000ano-op so there's no reason to complicate the code with trying to avoid\u000athe calls for these cases).\u000a\u000aCc: \u000aFixes: d2c997c0f145 (\"fs, dax: use page->mapping to warn if truncate...\")\u000aSigned-off-by: Jan Kara \u000aSigned-off-by: Dan Williams \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "7b6532ed7a6380b5c8e3d9c3a1fefff12469c5d8", "msg" : "dax: Fix xarray entry association for mixed mappings", "paths" : [ { "editType" : "edit", "file" : "fs/dax.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "lib/mpi/mpi-pow.c" ], "commitId" : "3e421061981c8bb6ddfb9ebf8469146b90ba7c50", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "lib/mpi: Fix karactx leak in mpi_powm\u000a\u000acommit c8ea9fce2baf7b643384f36f29e4194fa40d33a6 upstream.\u000a\u000aSometimes mpi_powm will leak karactx because a memory allocation\u000afailure causes a bail-out that skips the freeing of karactx. This\u000apatch moves the freeing of karactx to the end of the function like\u000aeverything else so that it can't be skipped.\u000a\u000aReported-by: syzbot+f7baccc38dcc1e094e77@syzkaller.appspotmail.com\u000aFixes: cdec9cb5167a (\"crypto: GnuPG based MPI lib - source files...\")\u000aCc: \u000aSigned-off-by: Herbert Xu \u000aReviewed-by: Eric Biggers \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "3e421061981c8bb6ddfb9ebf8469146b90ba7c50", "msg" : "lib/mpi: Fix karactx leak in mpi_powm", "paths" : [ { "editType" : "edit", "file" : "lib/mpi/mpi-pow.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/userfaultfd.c" ], "commitId" : "61ff807f0dd9e1daa3aa75ade32c102dedbcffd9", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "fs/userfaultfd.c: disable irqs for fault_pending and event locks\u000a\u000acommit cbcfa130a911c613a1d9d921af2eea171c414172 upstream.\u000a\u000aWhen IOCB_CMD_POLL is used on a userfaultfd, aio_poll() disables IRQs\u000aand takes kioctx::ctx_lock, then userfaultfd_ctx::fd_wqh.lock.\u000a\u000aThis may have to wait for userfaultfd_ctx::fd_wqh.lock to be released by\u000auserfaultfd_ctx_read(), which in turn can be waiting for\u000auserfaultfd_ctx::fault_pending_wqh.lock or\u000auserfaultfd_ctx::event_wqh.lock.\u000a\u000aBut elsewhere the fault_pending_wqh and event_wqh locks are taken with\u000aIRQs enabled. Since the IRQ handler may take kioctx::ctx_lock, lockdep\u000areports that a deadlock is possible.\u000a\u000aFix it by always disabling IRQs when taking the fault_pending_wqh and\u000aevent_wqh locks.\u000a\u000aCommit ae62c16e105a (\"userfaultfd: disable irqs when taking the\u000awaitqueue lock\") didn't fix this because it only accounted for the\u000afd_wqh lock, not the other locks nested inside it.\u000a\u000aLink: http://lkml.kernel.org/r/20190627075004.21259-1-ebiggers@kernel.org\u000aFixes: bfe4037e722e (\"aio: implement IOCB_CMD_POLL\")\u000aSigned-off-by: Eric Biggers \u000aReported-by: syzbot+fab6de82892b6b9c6191@syzkaller.appspotmail.com\u000aReported-by: syzbot+53c0b767f7ca0dc0c451@syzkaller.appspotmail.com\u000aReported-by: syzbot+a3accb352f9c22041cfa@syzkaller.appspotmail.com\u000aReviewed-by: Andrew Morton \u000aCc: Christoph Hellwig \u000aCc: Andrea Arcangeli \u000aCc: \u0009[4.19+]\u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "61ff807f0dd9e1daa3aa75ade32c102dedbcffd9", "msg" : "fs/userfaultfd.c: disable irqs for fault_pending and event locks", "paths" : [ { "editType" : "edit", "file" : "fs/userfaultfd.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "mm/page_io.c" ], "commitId" : "d82bf47aa320a0df39df27e63e1e319c429b572e", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "swap_readpage(): avoid blk_wake_io_task() if !synchronous\u000a\u000acommit 8751853091998cd31e9e5f1e8206280155af8921 upstream.\u000a\u000aswap_readpage() sets waiter = bio->bi_private even if synchronous = F,\u000athis means that the caller can get the spurious wakeup after return.\u000a\u000aThis can be fatal if blk_wake_io_task() does\u000aset_current_state(TASK_RUNNING) after the caller does\u000aset_special_state(), in the worst case the kernel can crash in\u000ado_task_dead().\u000a\u000aLink: http://lkml.kernel.org/r/20190704160301.GA5956@redhat.com\u000aFixes: 0619317ff8baa2d (\"block: add polled wakeup task helper\")\u000aSigned-off-by: Oleg Nesterov \u000aReported-by: Qian Cai \u000aAcked-by: Hugh Dickins \u000aReviewed-by: Jens Axboe \u000aCc: \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "d82bf47aa320a0df39df27e63e1e319c429b572e", "msg" : "swap_readpage(): avoid blk_wake_io_task() if !synchronous", "paths" : [ { "editType" : "edit", "file" : "mm/page_io.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/trace/trace.c" ], "commitId" : "ce3ce345cfd20671570596a6f5265abacc0c7021", "timestamp" : 1562745149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tracing/snapshot: Resize spare buffer if size changed\u000a\u000acommit 46cc0b44428d0f0e81f11ea98217fc0edfbeab07 upstream.\u000a\u000aCurrent snapshot implementation swaps two ring_buffers even though their\u000asizes are different from each other, that can cause an inconsistency\u000abetween the contents of buffer_size_kb file and the current buffer size.\u000a\u000aFor example:\u000a\u000a # cat buffer_size_kb\u000a 7 (expanded: 1408)\u000a # echo 1 > events/enable\u000a # grep bytes per_cpu/cpu0/stats\u000a bytes: 1441020\u000a # echo 1 > snapshot // current:1408, spare:1408\u000a # echo 123 > buffer_size_kb // current:123, spare:1408\u000a # echo 1 > snapshot // current:1408, spare:123\u000a # grep bytes per_cpu/cpu0/stats\u000a bytes: 1443700\u000a # cat buffer_size_kb\u000a 123 // != current:1408\u000a\u000aAnd also, a similar per-cpu case hits the following WARNING:\u000a\u000aReproducer:\u000a\u000a # echo 1 > per_cpu/cpu0/snapshot\u000a # echo 123 > buffer_size_kb\u000a # echo 1 > per_cpu/cpu0/snapshot\u000a\u000aWARNING:\u000a\u000a WARNING: CPU: 0 PID: 1946 at kernel/trace/trace.c:1607 update_max_tr_single.part.0+0x2b8/0x380\u000a Modules linked in:\u000a CPU: 0 PID: 1946 Comm: bash Not tainted 5.2.0-rc6 #20\u000a Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-2.fc30 04/01/2014\u000a RIP: 0010:update_max_tr_single.part.0+0x2b8/0x380\u000a Code: ff e8 dc da f9 ff 0f 0b e9 88 fe ff ff e8 d0 da f9 ff 44 89 ee bf f5 ff ff ff e8 33 dc f9 ff 41 83 fd f5 74 96 e8 b8 da f9 ff <0f> 0b eb 8d e8 af da f9 ff 0f 0b e9 bf fd ff ff e8 a3 da f9 ff 48\u000a RSP: 0018:ffff888063e4fca0 EFLAGS: 00010093\u000a RAX: ffff888066214380 RBX: ffffffff99850fe0 RCX: ffffffff964298a8\u000a RDX: 0000000000000000 RSI: 00000000fffffff5 RDI: 0000000000000005\u000a RBP: 1ffff1100c7c9f96 R08: ffff888066214380 R09: ffffed100c7c9f9b\u000a R10: ffffed100c7c9f9a R11: 0000000000000003 R12: 0000000000000000\u000a R13: 00000000ffffffea R14: ffff888066214380 R15: ffffffff99851060\u000a FS: 00007f9f8173c700(0000) GS:ffff88806d000000(0000) knlGS:0000000000000000\u000a CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a CR2: 0000000000714dc0 CR3: 0000000066fa6000 CR4: 00000000000006f0\u000a Call Trace:\u000a ? trace_array_printk_buf+0x140/0x140\u000a ? __mutex_lock_slowpath+0x10/0x10\u000a tracing_snapshot_write+0x4c8/0x7f0\u000a ? trace_printk_init_buffers+0x60/0x60\u000a ? selinux_file_permission+0x3b/0x540\u000a ? tracer_preempt_off+0x38/0x506\u000a ? trace_printk_init_buffers+0x60/0x60\u000a __vfs_write+0x81/0x100\u000a vfs_write+0x1e1/0x560\u000a ksys_write+0x126/0x250\u000a ? __ia32_sys_read+0xb0/0xb0\u000a ? do_syscall_64+0x1f/0x390\u000a do_syscall_64+0xc1/0x390\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a\u000aThis patch adds resize_buffer_duplicate_size() to check if there is a\u000adifference between current/spare buffer sizes and resize a spare buffer\u000aif necessary.\u000a\u000aLink: http://lkml.kernel.org/r/20190625012910.13109-1-devel@etsukata.com\u000a\u000aCc: stable@vger.kernel.org\u000aFixes: ad909e21bbe69 (\"tracing: Add internal tracing_snapshot() functions\")\u000aSigned-off-by: Eiichi Tsukata \u000aSigned-off-by: Steven Rostedt (VMware) \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:29 +0200", "id" : "ce3ce345cfd20671570596a6f5265abacc0c7021", "msg" : "tracing/snapshot: Resize spare buffer if size changed", "paths" : [ { "editType" : "edit", "file" : "kernel/trace/trace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/armada-xp-98dx3236.dtsi" ], "commitId" : "09cc58c8671330bb46294611e61a498f9e817f17", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: armada-xp-98dx3236: Switch to armada-38x-uart serial node\u000a\u000acommit 80031361747aec92163464f2ee08870fec33bcb0 upstream.\u000a\u000aSwitch to the \"marvell,armada-38x-uart\" driver variant to empty\u000athe UART buffer before writing to the UART_LCR register.\u000a\u000aSigned-off-by: Joshua Scott \u000aTested-by: Andrew Lunn \u000aAcked-by: Gregory CLEMENT .\u000aCc: stable@vger.kernel.org\u000aFixes: 43e28ba87708 (\"ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236\")\u000aSigned-off-by: Gregory CLEMENT \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "09cc58c8671330bb46294611e61a498f9e817f17", "msg" : "ARM: dts: armada-xp-98dx3236: Switch to armada-38x-uart serial node", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/armada-xp-98dx3236.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/kernel/module.c" ], "commitId" : "18cd20c0fa1bb0a3844b4b2ef6cfb22a85f8e051", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: kaslr: keep modules inside module region when KASAN is enabled\u000a\u000acommit 6f496a555d93db7a11d4860b9220d904822f586a upstream.\u000a\u000aWhen KASLR and KASAN are both enabled, we keep the modules where they\u000aare, and randomize the placement of the kernel so it is within 2 GB\u000aof the module region. The reason for this is that putting modules in\u000athe vmalloc region (like we normally do when KASLR is enabled) is not\u000apossible in this case, given that the entire vmalloc region is already\u000abacked by KASAN zero shadow pages, and so allocating dedicated KASAN\u000ashadow space as required by loaded modules is not possible.\u000a\u000aThe default module allocation window is set to [_etext - 128MB, _etext]\u000ain kaslr.c, which is appropriate for KASLR kernels booted without a\u000aseed or with 'nokaslr' on the command line. However, as it turns out,\u000ait is not quite correct for the KASAN case, since it still intersects\u000athe vmalloc region at the top, where attempts to allocate shadow pages\u000awill collide with the KASAN zero shadow pages, causing a WARN() and all\u000akinds of other trouble. So cap the top end to MODULES_END explicitly\u000awhen running with KASAN.\u000a\u000aCc: # 4.9+\u000aAcked-by: Catalin Marinas \u000aTested-by: Catalin Marinas \u000aSigned-off-by: Ard Biesheuvel \u000aSigned-off-by: Will Deacon \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "18cd20c0fa1bb0a3844b4b2ef6cfb22a85f8e051", "msg" : "arm64: kaslr: keep modules inside module region when KASAN is enabled", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/kernel/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/i915/intel_ringbuffer.c" ], "commitId" : "e7d14cc87cfee8209b9a2ca522ac375233bb7670", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context\u000a\u000acommit c84c9029d782a3a0d2a7f0522ecb907314d43e2c upstream.\u000a\u000aDespite what I think the prm recommends, commit f2253bd9859b\u000a(\"drm/i915/ringbuffer: EMIT_INVALIDATE after switch context\") turned out\u000ato be a huge mistake when enabling Ironlake contexts as the GPU would\u000ahang on either a MI_FLUSH or PIPE_CONTROL immediately following the\u000aMI_SET_CONTEXT of an active mesa context (more vanilla contexts, e.g.\u000asimple rendercopies with igt, do not suffer).\u000a\u000aVille found the following clue,\u000a\u000a \"[DevCTG+]: For the invalidate operation of the pipe control, the\u000a following pointers are affected. The\u000a invalidate operation affects the restore of these packets. If the pipe\u000a control invalidate operation is completed\u000a before the context save, the indirect pointers will not be restored from\u000a memory.\u000a 1. Pipeline State Pointer\u000a 2. Media State Pointer\u000a 3. Constant Buffer Packet\"\u000a\u000awhich suggests by us emitting the INVALIDATE prior to the MI_SET_CONTEXT,\u000awe prevent the context-restore from chasing the dangling pointers within\u000athe image, and explains why this likely prevents the GPU hang.\u000a\u000aSigned-off-by: Chris Wilson \u000aReviewed-by: Ville Syrjälä \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20190419111749.3910-1-chris@chris-wilson.co.uk\u000a(cherry picked from commit 928f8f42310f244501a7c70daac82c196112c190 in drm-intel-next)\u000aCc: stable@vger.kernel.org\u000aBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111014\u000aFixes: f2253bd9859b (\"drm/i915/ringbuffer: EMIT_INVALIDATE after switch context\")\u000aSigned-off-by: Daniel Vetter \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "e7d14cc87cfee8209b9a2ca522ac375233bb7670", "msg" : "drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/i915/intel_ringbuffer.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/amd/powerplay/hwmgr/process_pptables_v1_0.c", "drivers/gpu/drm/amd/powerplay/smumgr/polaris10_smumgr.c", "drivers/gpu/drm/amd/powerplay/inc/hwmgr.h" ], "commitId" : "5150d80f63190b663a0dca59dce11c14ef2f9a2c", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/amd/powerplay: use hardware fan control if no powerplay fan table\u000a\u000acommit f78c581e22d4b33359ac3462e8d0504735df01f4 upstream.\u000a\u000aOtherwise, you may get divided-by-zero error or corrput the SMU fan\u000acontrol feature.\u000a\u000aSigned-off-by: Evan Quan \u000aReviewed-by: Alex Deucher \u000aTested-by: Slava Abramov \u000aAcked-by: Slava Abramov \u000aSigned-off-by: Alex Deucher \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "5150d80f63190b663a0dca59dce11c14ef2f9a2c", "msg" : "drm/amd/powerplay: use hardware fan control if no powerplay fan table", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/amd/powerplay/smumgr/polaris10_smumgr.c" }, { "editType" : "edit", "file" : "drivers/gpu/drm/amd/powerplay/hwmgr/process_pptables_v1_0.c" }, { "editType" : "edit", "file" : "drivers/gpu/drm/amd/powerplay/inc/hwmgr.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c" ], "commitId" : "3f232903af86a92c78680e4a3b5e6bd996579eed", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/amdgpu: Don't skip display settings in hwmgr_resume()\u000a\u000acommit 688f3d1ebedffa310b6591bd1b63fa0770d945fe upstream.\u000a\u000aI'm not entirely sure why this is, but for some reason:\u000a\u000a921935dc6404 (\"drm/amd/powerplay: enforce display related settings only on needed\")\u000a\u000aBreaks runtime PM resume on the Radeon PRO WX 3100 (Lexa) in one the\u000apre-production laptops I have. The issue manifests as the following\u000amessages in dmesg:\u000a\u000a[drm] UVD and UVD ENC initialized successfully.\u000aamdgpu 0000:3b:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring vce1 test failed (-110)\u000a[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110\u000a[drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).\u000a\u000aAnd happens after about 6-10 runtime PM suspend/resume cycles (sometimes\u000asooner, if you're lucky!). Unfortunately I can't seem to pin down\u000aprecisely which part in psm_adjust_power_state_dynamic that is causing\u000athe issue, but not skipping the display setting setup seems to fix it.\u000aHopefully if there is a better fix for this, this patch will spark\u000adiscussion around it.\u000a\u000aFixes: 921935dc6404 (\"drm/amd/powerplay: enforce display related settings only on needed\")\u000aCc: Evan Quan \u000aCc: Alex Deucher \u000aCc: Huang Rui \u000aCc: Rex Zhu \u000aCc: Likun Gao \u000aCc: # v5.1+\u000aSigned-off-by: Lyude Paul \u000aSigned-off-by: Alex Deucher \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "3f232903af86a92c78680e4a3b5e6bd996579eed", "msg" : "drm/amdgpu: Don't skip display settings in hwmgr_resume()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c" ], "commitId" : "f728b21e2468d0742af2b9ced60088fe91bd981d", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/amdgpu/gfx9: use reset default for PA_SC_FIFO_SIZE\u000a\u000acommit 25f09f858835b0e9a06213811031190a17d8ab78 upstream.\u000a\u000aRecommended by the hw team.\u000a\u000aReviewed-and-Tested-by: Huang Rui \u000aSigned-off-by: Alex Deucher \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "f728b21e2468d0742af2b9ced60088fe91bd981d", "msg" : "drm/amdgpu/gfx9: use reset default for PA_SC_FIFO_SIZE", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/virtio/virtgpu_vq.c" ], "commitId" : "9455763a49212f3463dbeadeb7a1059b9a2d1fdd", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/virtio: move drm_connector_update_edid_property() call\u000a\u000acommit 41de4be6f6efa4132b29af51158cd672d93f2543 upstream.\u000a\u000adrm_connector_update_edid_property can sleep, we must not\u000acall it while holding a spinlock. Move the callsite.\u000a\u000aFixes: b4b01b4995fb (\"drm/virtio: add edid support\")\u000aReported-by: Max Filippov \u000aSigned-off-by: Gerd Hoffmann \u000aTested-by: Max Filippov \u000aTested-by: Cornelia Huck \u000aAcked-by: Cornelia Huck \u000aLink: http://patchwork.freedesktop.org/patch/msgid/20190405044602.2334-1-kraxel@redhat.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "9455763a49212f3463dbeadeb7a1059b9a2d1fdd", "msg" : "drm/virtio: move drm_connector_update_edid_property() call", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/virtio/virtgpu_vq.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/etnaviv/etnaviv_gpu.c" ], "commitId" : "7f426730b8b20b6e4f340f938b550cbaff64e75e", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/etnaviv: add missing failure path to destroy suballoc\u000a\u000acommit be132e1375c1fffe48801296279079f8a59a9ed3 upstream.\u000a\u000aWhen something goes wrong in the GPU init after the cmdbuf suballocator\u000ahas been constructed, we fail to destroy it properly. This causes havok\u000alater when the GPU is unbound due to a module unload or similar.\u000a\u000aFixes: e66774dd6f6a (drm/etnaviv: add cmdbuf suballocator)\u000aSigned-off-by: Lucas Stach \u000aTested-by: Russell King \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "7f426730b8b20b6e4f340f938b550cbaff64e75e", "msg" : "drm/etnaviv: add missing failure path to destroy suballoc", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/etnaviv/etnaviv_gpu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/imx/ipuv3-crtc.c" ], "commitId" : "c61d198157fb8755542c1d517431976064c536b8", "timestamp" : 1562745150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/imx: notify drm core before sending event during crtc disable\u000a\u000acommit 78c68e8f5cd24bd32ba4ca1cdfb0c30cf0642685 upstream.\u000a\u000aNotify drm core before sending pending events during crtc disable.\u000aThis fixes the first event after disable having an old stale timestamp\u000aby having drm_crtc_vblank_off update the timestamp to now.\u000a\u000aThis was seen while debugging weston log message:\u000aWarning: computed repaint delay is insane: -8212 msec\u000a\u000aThis occurred due to:\u000a1. driver starts up\u000a2. fbcon comes along and restores fbdev, enabling vblank\u000a3. vblank_disable_fn fires via timer disabling vblank, keeping vblank\u000aseq number and time set at current value\u000a(some time later)\u000a4. weston starts and does a modeset\u000a5. atomic commit disables crtc while it does the modeset\u000a6. ipu_crtc_atomic_disable sends vblank with old seq number and time\u000a\u000aFixes: a474478642d5 (\"drm/imx: fix crtc vblank state regression\")\u000a\u000aSigned-off-by: Robert Beckett \u000aReviewed-by: Daniel Vetter \u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:30 +0200", "id" : "c61d198157fb8755542c1d517431976064c536b8", "msg" : "drm/imx: notify drm core before sending event during crtc disable", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/imx/ipuv3-crtc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/imx/ipuv3-crtc.c" ], "commitId" : "3d2a80000100ec7de166c3a72a3233a902e7d032", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/imx: only send event on crtc disable if kept disabled\u000a\u000acommit 5aeab2bfc9ffa72d3ca73416635cb3785dfc076f upstream.\u000a\u000aThe event will be sent as part of the vblank enable during the modeset\u000aif the crtc is not being kept disabled.\u000a\u000aFixes: 5f2f911578fb (\"drm/imx: atomic phase 3 step 1: Use atomic configuration\")\u000a\u000aSigned-off-by: Robert Beckett \u000aReviewed-by: Daniel Vetter \u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "3d2a80000100ec7de166c3a72a3233a902e7d032", "msg" : "drm/imx: only send event on crtc disable if kept disabled", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/imx/ipuv3-crtc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/trace/ftrace.c", "arch/x86/kernel/ftrace.c" ], "commitId" : "d0a2a5101c7cdd648a929a5e9519e2c87a6cb5fa", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ftrace/x86: Remove possible deadlock between register_kprobe() and ftrace_run_update_code()\u000a\u000acommit d5b844a2cf507fc7642c9ae80a9d585db3065c28 upstream.\u000a\u000aThe commit 9f255b632bf12c4dd7 (\"module: Fix livepatch/ftrace module text\u000apermissions race\") causes a possible deadlock between register_kprobe()\u000aand ftrace_run_update_code() when ftrace is using stop_machine().\u000a\u000aThe existing dependency chain (in reverse order) is:\u000a\u000a-> #1 (text_mutex){+.+.}:\u000a validate_chain.isra.21+0xb32/0xd70\u000a __lock_acquire+0x4b8/0x928\u000a lock_acquire+0x102/0x230\u000a __mutex_lock+0x88/0x908\u000a mutex_lock_nested+0x32/0x40\u000a register_kprobe+0x254/0x658\u000a init_kprobes+0x11a/0x168\u000a do_one_initcall+0x70/0x318\u000a kernel_init_freeable+0x456/0x508\u000a kernel_init+0x22/0x150\u000a ret_from_fork+0x30/0x34\u000a kernel_thread_starter+0x0/0xc\u000a\u000a-> #0 (cpu_hotplug_lock.rw_sem){++++}:\u000a check_prev_add+0x90c/0xde0\u000a validate_chain.isra.21+0xb32/0xd70\u000a __lock_acquire+0x4b8/0x928\u000a lock_acquire+0x102/0x230\u000a cpus_read_lock+0x62/0xd0\u000a stop_machine+0x2e/0x60\u000a arch_ftrace_update_code+0x2e/0x40\u000a ftrace_run_update_code+0x40/0xa0\u000a ftrace_startup+0xb2/0x168\u000a register_ftrace_function+0x64/0x88\u000a klp_patch_object+0x1a2/0x290\u000a klp_enable_patch+0x554/0x980\u000a do_one_initcall+0x70/0x318\u000a do_init_module+0x6e/0x250\u000a load_module+0x1782/0x1990\u000a __s390x_sys_finit_module+0xaa/0xf0\u000a system_call+0xd8/0x2d0\u000a\u000a Possible unsafe locking scenario:\u000a\u000a CPU0 CPU1\u000a ---- ----\u000a lock(text_mutex);\u000a lock(cpu_hotplug_lock.rw_sem);\u000a lock(text_mutex);\u000a lock(cpu_hotplug_lock.rw_sem);\u000a\u000aIt is similar problem that has been solved by the commit 2d1e38f56622b9b\u000a(\"kprobes: Cure hotplug lock ordering issues\"). Many locks are involved.\u000aTo be on the safe side, text_mutex must become a low level lock taken\u000aafter cpu_hotplug_lock.rw_sem.\u000a\u000aThis can't be achieved easily with the current ftrace design.\u000aFor example, arm calls set_all_modules_text_rw() already in\u000aftrace_arch_code_modify_prepare(), see arch/arm/kernel/ftrace.c.\u000aThis functions is called:\u000a\u000a + outside stop_machine() from ftrace_run_update_code()\u000a + without stop_machine() from ftrace_module_enable()\u000a\u000aFortunately, the problematic fix is needed only on x86_64. It is\u000athe only architecture that calls set_all_modules_text_rw()\u000ain ftrace path and supports livepatching at the same time.\u000a\u000aTherefore it is enough to move text_mutex handling from the generic\u000akernel/trace/ftrace.c into arch/x86/kernel/ftrace.c:\u000a\u000a ftrace_arch_code_modify_prepare()\u000a ftrace_arch_code_modify_post_process()\u000a\u000aThis patch basically reverts the ftrace part of the problematic\u000acommit 9f255b632bf12c4dd7 (\"module: Fix livepatch/ftrace module\u000atext permissions race\"). And provides x86_64 specific-fix.\u000a\u000aSome refactoring of the ftrace code will be needed when livepatching\u000ais implemented for arm or nds32. These architectures call\u000aset_all_modules_text_rw() and use stop_machine() at the same time.\u000a\u000aLink: http://lkml.kernel.org/r/20190627081334.12793-1-pmladek@suse.com\u000a\u000aFixes: 9f255b632bf12c4dd7 (\"module: Fix livepatch/ftrace module text permissions race\")\u000aAcked-by: Thomas Gleixner \u000aReported-by: Miroslav Benes \u000aReviewed-by: Miroslav Benes \u000aReviewed-by: Josh Poimboeuf \u000aSigned-off-by: Petr Mladek \u000a[\u000a As reviewed by Miroslav Benes , removed return value of\u000a ftrace_run_update_code() as it is a void function.\u000a]\u000aSigned-off-by: Steven Rostedt (VMware) \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "d0a2a5101c7cdd648a929a5e9519e2c87a6cb5fa", "msg" : "ftrace/x86: Remove possible deadlock between register_kprobe() and ftrace_run_update_code()", "paths" : [ { "editType" : "edit", "file" : "kernel/trace/ftrace.c" }, { "editType" : "edit", "file" : "arch/x86/kernel/ftrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "mm/vmscan.c" ], "commitId" : "d4ad26edd623b66e9d2583c9cda6ab629ddbddee", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mm/vmscan.c: prevent useless kswapd loops\u000a\u000acommit dffcac2cb88e4ec5906235d64a83d802580b119e upstream.\u000a\u000aIn production we have noticed hard lockups on large machines running\u000alarge jobs due to kswaps hoarding lru lock within isolate_lru_pages when\u000asc->reclaim_idx is 0 which is a small zone. The lru was couple hundred\u000aGiBs and the condition (page_zonenum(page) > sc->reclaim_idx) in\u000aisolate_lru_pages() was basically skipping GiBs of pages while holding\u000athe LRU spinlock with interrupt disabled.\u000a\u000aOn further inspection, it seems like there are two issues:\u000a\u000a(1) If kswapd on the return from balance_pgdat() could not sleep (i.e.\u000a node is still unbalanced), the classzone_idx is unintentionally set\u000a to 0 and the whole reclaim cycle of kswapd will try to reclaim only\u000a the lowest and smallest zone while traversing the whole memory.\u000a\u000a(2) Fundamentally isolate_lru_pages() is really bad when the\u000a allocation has woken kswapd for a smaller zone on a very large machine\u000a running very large jobs. It can hoard the LRU spinlock while skipping\u000a over 100s of GiBs of pages.\u000a\u000aThis patch only fixes (1). (2) needs a more fundamental solution. To\u000afix (1), in the kswapd context, if pgdat->kswapd_classzone_idx is\u000ainvalid use the classzone_idx of the previous kswapd loop otherwise use\u000athe one the waker has requested.\u000a\u000aLink: http://lkml.kernel.org/r/20190701201847.251028-1-shakeelb@google.com\u000aFixes: e716f2eb24de (\"mm, vmscan: prevent kswapd sleeping prematurely due to mismatched classzone_idx\")\u000aSigned-off-by: Shakeel Butt \u000aReviewed-by: Yang Shi \u000aAcked-by: Mel Gorman \u000aCc: Johannes Weiner \u000aCc: Michal Hocko \u000aCc: Vlastimil Babka \u000aCc: Hillf Danton \u000aCc: Roman Gushchin \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "d4ad26edd623b66e9d2583c9cda6ab629ddbddee", "msg" : "mm/vmscan.c: prevent useless kswapd loops", "paths" : [ { "editType" : "edit", "file" : "mm/vmscan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/btrfs/volumes.c", "fs/btrfs/volumes.h", "fs/btrfs/dev-replace.c" ], "commitId" : "723e3866fdd3fbba4539f6b17bcc590f3fd8ae11", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "btrfs: Ensure replaced device doesn't have pending chunk allocation\u000a\u000acommit debd1c065d2037919a7da67baf55cc683fee09f0 upstream.\u000a\u000aRecent FITRIM work, namely bbbf7243d62d (\"btrfs: combine device update\u000aoperations during transaction commit\") combined the way certain\u000aoperations are recoded in a transaction. As a result an ASSERT was added\u000ain dev_replace_finish to ensure the new code works correctly.\u000aUnfortunately I got reports that it's possible to trigger the assert,\u000ameaning that during a device replace it's possible to have an unfinished\u000achunk allocation on the source device.\u000a\u000aThis is supposed to be prevented by the fact that a transaction is\u000acommitted before finishing the replace oepration and alter acquiring the\u000achunk mutex. This is not sufficient since by the time the transaction is\u000acommitted and the chunk mutex acquired it's possible to allocate a chunk\u000adepending on the workload being executed on the replaced device. This\u000abug has been present ever since device replace was introduced but there\u000awas never code which checks for it.\u000a\u000aThe correct way to fix is to ensure that there is no pending device\u000amodification operation when the chunk mutex is acquire and if there is\u000arepeat transaction commit. Unfortunately it's not possible to just\u000aexclude the source device from btrfs_fs_devices::dev_alloc_list since\u000athis causes ENOSPC to be hit in transaction commit.\u000a\u000aFixing that in another way would need to add special cases to handle the\u000alast writes and forbid new ones. The looped transaction fix is more\u000aobvious, and can be easily backported. The runtime of dev-replace is\u000along so there's no noticeable delay caused by that.\u000a\u000aReported-by: David Sterba \u000aFixes: 391cd9df81ac (\"Btrfs: fix unprotected alloc list insertion during the finishing procedure of replace\")\u000aCC: stable@vger.kernel.org # 4.4+\u000aSigned-off-by: Nikolay Borisov \u000aReviewed-by: David Sterba \u000aSigned-off-by: David Sterba \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "723e3866fdd3fbba4539f6b17bcc590f3fd8ae11", "msg" : "btrfs: Ensure replaced device doesn't have pending chunk allocation", "paths" : [ { "editType" : "edit", "file" : "fs/btrfs/volumes.h" }, { "editType" : "edit", "file" : "fs/btrfs/volumes.c" }, { "editType" : "edit", "file" : "fs/btrfs/dev-replace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/tty/rocket.c" ], "commitId" : "3e9e67d03995f8eae4d498f25acc2423ae65d482", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tty: rocket: fix incorrect forward declaration of 'rp_init()'\u000a\u000a[ Upstream commit 423ea3255424b954947d167681b71ded1b8fca53 ]\u000a\u000aMake the forward declaration actually match the real function\u000adefinition, something that previous versions of gcc had just ignored.\u000a\u000aThis is another patch to fix new warnings from gcc-9 before I start the\u000amerge window pulls. I don't want to miss legitimate new warnings just\u000abecause my system update brought a new compiler with new warnings.\u000a\u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "3e9e67d03995f8eae4d498f25acc2423ae65d482", "msg" : "tty: rocket: fix incorrect forward declaration of 'rp_init()'", "paths" : [ { "editType" : "edit", "file" : "drivers/tty/rocket.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/s390/include/asm/pgtable.h" ], "commitId" : "0615757300497d10704f276132a25d02817b0700", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "s390/mm: fix pxd_bad with folded page tables\u000a\u000a[ Upstream commit c9f621524e70774688db3cec60d85fa4c7de52e3 ]\u000a\u000aWith git commit d1874a0c2805fcfa9162c972d6b7541e57adb542\u000a\"s390/mm: make the pxd_offset functions more robust\" and a 2-level page\u000atable it can now happen that pgd_bad() gets asked to verify a large\u000asegment table entry. If the entry is marked as dirty pgd_bad() will\u000aincorrectly return true.\u000a\u000aChange the pgd_bad(), p4d_bad(), pud_bad() and pmd_bad() functions to\u000afirst verify the table type, return false if the table level is lower\u000athan what the function is suppossed to check, return true if the table\u000alevel is too high, and otherwise check the relevant region and segment\u000atable bits. pmd_bad() has to check against ~SEGMENT_ENTRY_BITS for\u000anormal page table pointers or ~SEGMENT_ENTRY_BITS_LARGE for large\u000asegment table entries. Same for pud_bad() which has to check against\u000a~_REGION_ENTRY_BITS or ~_REGION_ENTRY_BITS_LARGE.\u000a\u000aFixes: d1874a0c2805 (\"s390/mm: make the pxd_offset functions more robust\")\u000aSigned-off-by: Martin Schwidefsky \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "0615757300497d10704f276132a25d02817b0700", "msg" : "s390/mm: fix pxd_bad with folded page tables", "paths" : [ { "editType" : "edit", "file" : "arch/s390/include/asm/pgtable.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/x86.c" ], "commitId" : "d2bacadcff03cbde1bba0b3d848226dcced69b27", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: x86: degrade WARN to pr_warn_ratelimited\u000a\u000acommit 3f16a5c318392cbb5a0c7a3d19dff8c8ef3c38ee upstream.\u000a\u000aThis warning can be triggered easily by userspace, so it should certainly not\u000acause a panic if panic_on_warn is set.\u000a\u000aReported-by: syzbot+c03f30b4f4c46bdf8575@syzkaller.appspotmail.com\u000aSuggested-by: Alexander Potapenko \u000aAcked-by: Alexander Potapenko \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "d2bacadcff03cbde1bba0b3d848226dcced69b27", "msg" : "KVM: x86: degrade WARN to pr_warn_ratelimited", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/x86.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/lapic.c" ], "commitId" : "03dbbec3388e7986bd62179891467d3e9f52f67b", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: LAPIC: Fix pending interrupt in IRR blocked by software disable LAPIC\u000a\u000acommit bb34e690e9340bc155ebed5a3d75fc63ff69e082 upstream.\u000a\u000aThomas reported that:\u000a\u000a | Background:\u000a |\u000a | In preparation of supporting IPI shorthands I changed the CPU offline\u000a | code to software disable the local APIC instead of just masking it.\u000a | That's done by clearing the APIC_SPIV_APIC_ENABLED bit in the APIC_SPIV\u000a | register.\u000a |\u000a | Failure:\u000a |\u000a | When the CPU comes back online the startup code triggers occasionally\u000a | the warning in apic_pending_intr_clear(). That complains that the IRRs\u000a | are not empty.\u000a |\u000a | The offending vector is the local APIC timer vector who's IRR bit is set\u000a | and stays set.\u000a |\u000a | It took me quite some time to reproduce the issue locally, but now I can\u000a | see what happens.\u000a |\u000a | It requires apicv_enabled=0, i.e. full apic emulation. With apicv_enabled=1\u000a | (and hardware support) it behaves correctly.\u000a |\u000a | Here is the series of events:\u000a |\u000a | Guest CPU\u000a |\u000a | goes down\u000a |\u000a | native_cpu_disable()\u000a |\u000a | \u0009\u0009\u0009apic_soft_disable();\u000a |\u000a | play_dead()\u000a |\u000a | ....\u000a |\u000a | startup()\u000a |\u000a | if (apic_enabled())\u000a | apic_pending_intr_clear()\u0009<- Not taken\u000a |\u000a | enable APIC\u000a |\u000a | apic_pending_intr_clear()\u0009<- Triggers warning because IRR is stale\u000a |\u000a | When this happens then the deadline timer or the regular APIC timer -\u000a | happens with both, has fired shortly before the APIC is disabled, but the\u000a | interrupt was not serviced because the guest CPU was in an interrupt\u000a | disabled region at that point.\u000a |\u000a | The state of the timer vector ISR/IRR bits:\u000a |\u000a | \u0009 \u0009 \u0009 ISR IRR\u000a | before apic_soft_disable() 0\u0009 1\u000a | after apic_soft_disable() 0\u0009 1\u000a |\u000a | On startup\u0009\u0009 \u0009\u0009 0\u0009 1\u000a |\u000a | Now one would assume that the IRR is cleared after the INIT reset, but this\u000a | happens only on CPU0.\u000a |\u000a | Why?\u000a |\u000a | Because our CPU0 hotplug is just for testing to make sure nothing breaks\u000a | and goes through an NMI wakeup vehicle because INIT would send it through\u000a | the boots-trap code which is not really working if that CPU was not\u000a | physically unplugged.\u000a |\u000a | Now looking at a real world APIC the situation in that case is:\u000a |\u000a | \u0009 \u0009 \u0009 \u0009ISR IRR\u000a | before apic_soft_disable() 0\u0009 1\u000a | after apic_soft_disable() 0\u0009 1\u000a |\u000a | On startup\u0009\u0009 \u0009\u0009 0\u0009 0\u000a |\u000a | Why?\u000a |\u000a | Once the dying CPU reenables interrupts the pending interrupt gets\u000a | delivered as a spurious interupt and then the state is clear.\u000a |\u000a | While that CPU0 hotplug test case is surely an esoteric issue, the APIC\u000a | emulation is still wrong, Even if the play_dead() code would not enable\u000a | interrupts then the pending IRR bit would turn into an ISR .. interrupt\u000a | when the APIC is reenabled on startup.\u000a\u000aFrom SDM 10.4.7.2 Local APIC State After It Has Been Software Disabled\u000a* Pending interrupts in the IRR and ISR registers are held and require\u000a masking or handling by the CPU.\u000a\u000aIn Thomas's testing, hardware cpu will not respect soft disable LAPIC\u000awhen IRR has already been set or APICv posted-interrupt is in flight,\u000aso we can skip soft disable APIC checking when clearing IRR and set ISR,\u000acontinue to respect soft disable APIC when attempting to set IRR.\u000a\u000aReported-by: Rong Chen \u000aReported-by: Feng Tang \u000aReported-by: Thomas Gleixner \u000aTested-by: Thomas Gleixner \u000aCc: Paolo Bonzini \u000aCc: Radim Krčmář \u000aCc: Thomas Gleixner \u000aCc: Rong Chen \u000aCc: Feng Tang \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Wanpeng Li \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "03dbbec3388e7986bd62179891467d3e9f52f67b", "msg" : "KVM: LAPIC: Fix pending interrupt in IRR blocked by software disable LAPIC", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/lapic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/nfsd/nfs4state.c" ], "commitId" : "94f536c7556045f1920a78ef9d2c9a6fd398ef94", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nfsd: Fix overflow causing non-working mounts on 1 TB machines\u000a\u000acommit 3b2d4dcf71c4a91b420f835e52ddea8192300a3b upstream.\u000a\u000aSince commit 10a68cdf10 (nfsd: fix performance-limiting session\u000acalculation) (Linux 5.1-rc1 and 4.19.31), shares from NFS servers with\u000a1 TB of memory cannot be mounted anymore. The mount just hangs on the\u000aclient.\u000a\u000aThe gist of commit 10a68cdf10 is the change below.\u000a\u000a -avail = clamp_t(int, avail, slotsize, avail/3);\u000a +avail = clamp_t(int, avail, slotsize, total_avail/3);\u000a\u000aHere are the macros.\u000a\u000a #define min_t(type, x, y) __careful_cmp((type)(x), (type)(y), <)\u000a #define clamp_t(type, val, lo, hi) min_t(type, max_t(type, val, lo), hi)\u000a\u000a`total_avail` is 8,434,659,328 on the 1 TB machine. `clamp_t()` casts\u000athe values to `int`, which for 32-bit integers can only hold values\u000a−2,147,483,648 (−2^31) through 2,147,483,647 (2^31 − 1).\u000a\u000a`avail` (in the function signature) is just 65536, so that no overflow\u000awas happening. Before the commit the assignment would result in 21845,\u000aand `num = 4`.\u000a\u000aWhen using `total_avail`, it is causing the assignment to be\u000a18446744072226137429 (printed as %lu), and `num` is then 4164608182.\u000a\u000aMy next guess is, that `nfsd_drc_mem_used` is then exceeded, and the\u000aserver thinks there is no memory available any more for this client.\u000a\u000aUpdating the arguments of `clamp_t()` and `min_t()` to `unsigned long`\u000afixes the issue.\u000a\u000aNow, `avail = 65536` (before commit 10a68cdf10 `avail = 21845`), but\u000a`num = 4` remains the same.\u000a\u000aFixes: c54f24e338ed (nfsd: fix performance-limiting session calculation)\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Paul Menzel \u000aSigned-off-by: J. Bruce Fields \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "94f536c7556045f1920a78ef9d2c9a6fd398ef94", "msg" : "nfsd: Fix overflow causing non-working mounts on 1 TB machines", "paths" : [ { "editType" : "edit", "file" : "fs/nfsd/nfs4state.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/sunrpc/xprtrdma/svc_rdma_transport.c" ], "commitId" : "3774d334e314b65c97c98274be365e9d80ca1fe2", "timestamp" : 1562745151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "svcrdma: Ignore source port when computing DRC hash\u000a\u000acommit 1e091c3bbf51d34d5d96337a59ce5ab2ac3ba2cc upstream.\u000a\u000aThe DRC appears to be effectively empty after an RPC/RDMA transport\u000areconnect. The problem is that each connection uses a different\u000asource port, which defeats the DRC hash.\u000a\u000aClients always have to disconnect before they send retransmissions\u000ato reset the connection's credit accounting, thus every retransmit\u000aon NFS/RDMA will miss the DRC.\u000a\u000aAn NFS/RDMA client's IP source port is meaningless for RDMA\u000atransports. The transport layer typically sets the source port value\u000aon the connection to a random ephemeral port. The server already\u000aignores it for the \"secure port\" check. See commit 16e4d93f6de7\u000a(\"NFSD: Ignore client's source port on RDMA transports\").\u000a\u000aThe Linux NFS server's DRC resolves XID collisions from the same\u000asource IP address by using the checksum of the first 200 bytes of\u000athe RPC call header.\u000a\u000aSigned-off-by: Chuck Lever \u000aCc: stable@vger.kernel.org # v4.14+\u000aSigned-off-by: J. Bruce Fields \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:31 +0200", "id" : "3774d334e314b65c97c98274be365e9d80ca1fe2", "msg" : "svcrdma: Ignore source port when computing DRC hash", "paths" : [ { "editType" : "edit", "file" : "net/sunrpc/xprtrdma/svc_rdma_transport.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/mips/mm/mmap.c" ], "commitId" : "e395c337f1445a93ae245f0d1240201dfb7ea8cb", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "MIPS: Fix bounds check virt_addr_valid\u000a\u000acommit d6ed083f5cc621e15c15b56c3b585fd524dbcb0f upstream.\u000a\u000aThe bounds check used the uninitialized variable vaddr, it should use\u000athe given parameter kaddr instead. When using the uninitialized value\u000athe compiler assumed it to be 0 and optimized this function to just\u000areturn 0 in all cases.\u000a\u000aThis should make the function check the range of the given address and\u000aonly do the page map check in case it is in the expected range of\u000avirtual addresses.\u000a\u000aFixes: 074a1e1167af (\"MIPS: Bounds check virt_addr_valid\")\u000aCc: stable@vger.kernel.org # v4.12+\u000aCc: Paul Burton \u000aSigned-off-by: Hauke Mehrtens \u000aSigned-off-by: Paul Burton \u000aCc: ralf@linux-mips.org\u000aCc: jhogan@kernel.org\u000aCc: f4bug@amsat.org\u000aCc: linux-mips@vger.kernel.org\u000aCc: ysu@wavecomp.com\u000aCc: jcristau@debian.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "e395c337f1445a93ae245f0d1240201dfb7ea8cb", "msg" : "MIPS: Fix bounds check virt_addr_valid", "paths" : [ { "editType" : "edit", "file" : "arch/mips/mm/mmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/mips/mm/tlbex.c" ], "commitId" : "4b9615523be558c93f3c6a8510a5f536dc40dad9", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "MIPS: Add missing EHB in mtc0 -> mfc0 sequence.\u000a\u000acommit 0b24cae4d535045f4c9e177aa228d4e97bad212c upstream.\u000a\u000aAdd a missing EHB (Execution Hazard Barrier) in mtc0 -> mfc0 sequence.\u000aWithout this execution hazard barrier it's possible for the value read\u000aback from the KScratch register to be the value from before the mtc0.\u000a\u000aReproducible on P5600 & P6600.\u000a\u000aThe hazard is documented in the MIPS Architecture Reference Manual Vol.\u000aIII: MIPS32/microMIPS32 Privileged Resource Architecture (MD00088), rev\u000a6.03 table 8.1 which includes:\u000a\u000a Producer | Consumer | Hazard\u000a ----------|----------|----------------------------\u000a mtc0 | mfc0 | any coprocessor 0 register\u000a\u000aSigned-off-by: Dmitry Korotin \u000a[paul.burton@mips.com:\u000a - Commit message tweaks.\u000a - Add Fixes tags.\u000a - Mark for stable back to v3.15 where P5600 support was introduced.]\u000aSigned-off-by: Paul Burton \u000aFixes: 3d8bfdd03072 (\"MIPS: Use C0_KScratch (if present) to hold PGD pointer.\")\u000aFixes: 829dcc0a956a (\"MIPS: Add MIPS P5600 probe support\")\u000aCc: linux-mips@vger.kernel.org\u000aCc: stable@vger.kernel.org # v3.15+\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "4b9615523be558c93f3c6a8510a5f536dc40dad9", "msg" : "MIPS: Add missing EHB in mtc0 -> mfc0 sequence.", "paths" : [ { "editType" : "edit", "file" : "arch/mips/mm/tlbex.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/mips/Makefile" ], "commitId" : "b7948d98a058c46360d6af0139664e85860c9e2d", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "MIPS: have \"plain\" make calls build dtbs for selected platforms\u000a\u000acommit 637dfa0fad6d91a9a709dc70549a6d20fa77f615 upstream.\u000a\u000ascripts/package/builddeb calls \"make dtbs_install\" after executing\u000aa plain make (i.e. no build targets specified). It will fail if dtbs\u000awere not built beforehand. Match the arm64 architecture where DTBs get\u000abuilt by the \"all\" target.\u000a\u000aSigned-off-by: Cedric Hombourger \u000a[paul.burton@mips.com: s/builddep/builddeb]\u000aSigned-off-by: Paul Burton \u000aCc: linux-mips@vger.kernel.org\u000aCc: stable@vger.kernel.org # v4.1+\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "b7948d98a058c46360d6af0139664e85860c9e2d", "msg" : "MIPS: have \"plain\" make calls build dtbs for selected platforms", "paths" : [ { "editType" : "edit", "file" : "arch/mips/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/dma/qcom/bam_dma.c" ], "commitId" : "c68eb98ae2975cae25271e4f7334766c17686810", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dmaengine: qcom: bam_dma: Fix completed descriptors count\u000a\u000acommit f6034225442c4a87906d36e975fd9e99a8f95487 upstream.\u000a\u000aOne space is left unused in circular FIFO to differentiate\u000a'full' and 'empty' cases. So take that in to account while\u000acounting for the descriptors completed.\u000a\u000aFixes the issue reported here,\u000a\u0009https://lkml.org/lkml/2019/6/18/669\u000a\u000aCc: stable@vger.kernel.org\u000aReported-by: Srinivas Kandagatla \u000aSigned-off-by: Sricharan R \u000aTested-by: Srinivas Kandagatla \u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "c68eb98ae2975cae25271e4f7334766c17686810", "msg" : "dmaengine: qcom: bam_dma: Fix completed descriptors count", "paths" : [ { "editType" : "edit", "file" : "drivers/dma/qcom/bam_dma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/dma/imx-sdma.c" ], "commitId" : "598ffd879b8a951d1f2febc76f39b97697f65eaf", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dmaengine: imx-sdma: remove BD_INTR for channel0\u000a\u000acommit 3f93a4f297961c12bb17aa16cb3a4d1291823cae upstream.\u000a\u000aIt is possible for an irq triggered by channel0 to be received later\u000aafter clks are disabled once firmware loaded during sdma probe. If\u000athat happens then clearing them by writing to SDMA_H_INTR won't work\u000aand the kernel will hang processing infinite interrupts. Actually,\u000adon't need interrupt triggered on channel0 since it's pollling\u000aSDMA_H_STATSTOP to know channel0 done rather than interrupt in\u000acurrent code, just clear BD_INTR to disable channel0 interrupt to\u000aavoid the above case.\u000aThis issue was brought by commit 1d069bfa3c78 (\"dmaengine: imx-sdma:\u000aack channel 0 IRQ in the interrupt handler\") which didn't take care\u000athe above case.\u000a\u000aFixes: 1d069bfa3c78 (\"dmaengine: imx-sdma: ack channel 0 IRQ in the interrupt handler\")\u000aCc: stable@vger.kernel.org #5.0+\u000aSigned-off-by: Robin Gong \u000aReported-by: Sven Van Asbroeck \u000aTested-by: Sven Van Asbroeck \u000aReviewed-by: Michael Olbrich \u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "598ffd879b8a951d1f2febc76f39b97697f65eaf", "msg" : "dmaengine: imx-sdma: remove BD_INTR for channel0", "paths" : [ { "editType" : "edit", "file" : "drivers/dma/imx-sdma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/dma/dma-jz4780.c" ], "commitId" : "abedf70e30e15c9e2ae8d9543fa56643168acd7c", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dmaengine: jz4780: Fix an endian bug in IRQ handler\u000a\u000acommit 4c89cc73d1da42ae48b5c5dfbfd12304d0b86786 upstream.\u000a\u000aThe \"pending\" variable was a u32 but we cast it to an unsigned long\u000apointer when we do the for_each_set_bit() loop. The problem is that on\u000abig endian 64bit systems that results in an out of bounds read.\u000a\u000aFixes: 4e4106f5e942 (\"dmaengine: jz4780: Fix transfers being ACKed too soon\")\u000aSigned-off-by: Dan Carpenter \u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "abedf70e30e15c9e2ae8d9543fa56643168acd7c", "msg" : "dmaengine: jz4780: Fix an endian bug in IRQ handler", "paths" : [ { "editType" : "edit", "file" : "drivers/dma/dma-jz4780.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/Kconfig" ], "commitId" : "c43646a747ed9c21a9fbe7b0cfb49c92b57eaef8", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "fs: VALIDATE_FS_PARSER should default to n\u000a\u000acommit 75f2d86b20bf6aec0392d6dd2ae3ffff26d2ae0e upstream.\u000a\u000aCONFIG_VALIDATE_FS_PARSER is a debugging tool to check that the parser\u000atables are vaguely sane. It was set to default to 'Y' for the moment to\u000acatch errors in upcoming fs conversion development.\u000a\u000aMake sure it is not enabled by default in the final release of v5.1.\u000a\u000aFixes: 31d921c7fb969172 (\"vfs: Add configuration parser helpers\")\u000aSigned-off-by: Geert Uytterhoeven \u000aSigned-off-by: Al Viro \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "c43646a747ed9c21a9fbe7b0cfb49c92b57eaef8", "msg" : "fs: VALIDATE_FS_PARSER should default to n", "paths" : [ { "editType" : "edit", "file" : "fs/Kconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/target/target_core_iblock.c" ], "commitId" : "10a573205ddd74d94bfc1bff4dfc8828ab7c055a", "timestamp" : 1562745152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: target/iblock: Fix overrun in WRITE SAME emulation\u000a\u000acommit 5676234f20fef02f6ca9bd66c63a8860fce62645 upstream.\u000a\u000aWRITE SAME corrupts data on the block device behind iblock if the command\u000ais emulated. The emulation code issues (M - 1) * N times more bios than\u000arequested, where M is the number of 512 blocks per real block size and N is\u000athe NUMBER OF LOGICAL BLOCKS specified in WRITE SAME command. So, for a\u000adevice with 4k blocks, 7 * N more LBAs gets written after the requested\u000arange.\u000a\u000aThe issue happens because the number of 512 byte sectors to be written is\u000adecreased one by one while the real bios are typically from 1 to 8 512 byte\u000asectors per bio.\u000a\u000aFixes: c66ac9db8d4a (\"[SCSI] target: Add LIO target core v4.0.0-rc6\")\u000aCc: \u000aSigned-off-by: Roman Bolshakov \u000aReviewed-by: Bart Van Assche \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-10 09:52:32 +0200", "id" : "10a573205ddd74d94bfc1bff4dfc8828ab7c055a", "msg" : "scsi: target/iblock: Fix overrun in WRITE SAME emulation", "paths" : [ { "editType" : "edit", "file" : "drivers/target/target_core_iblock.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Makefile" ], "commitId" : "4b886fa2b8f167b70af8a21340dfb3e24711e084", "timestamp" : 1562745153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Linux 5.1.17\u000a", "date" : "2019-07-10 09:52:33 +0200", "id" : "4b886fa2b8f167b70af8a21340dfb3e24711e084", "msg" : "Linux 5.1.17", "paths" : [ { "editType" : "edit", "file" : "Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/lrw.c" ], "commitId" : "043b0ea769aac0dd5524ced016cbf83323468db6", "timestamp" : 1563084574000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: lrw - use correct alignmask\u000a\u000acommit 20a0f9761343fba9b25ea46bd3a3e5e533d974f8 upstream.\u000a\u000aCommit c778f96bf347 (\"crypto: lrw - Optimize tweak computation\")\u000aincorrectly reduced the alignmask of LRW instances from\u000a'__alignof__(u64) - 1' to '__alignof__(__be32) - 1'.\u000a\u000aHowever, xor_tweak() and setkey() assume that the data and key,\u000arespectively, are aligned to 'be128', which has u64 alignment.\u000a\u000aFix the alignmask to be at least '__alignof__(be128) - 1'.\u000a\u000aFixes: c778f96bf347 (\"crypto: lrw - Optimize tweak computation\")\u000aCc: # v4.20+\u000aCc: Ondrej Mosnacek \u000aSigned-off-by: Eric Biggers \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:34 +0200", "id" : "043b0ea769aac0dd5524ced016cbf83323468db6", "msg" : "crypto: lrw - use correct alignmask", "paths" : [ { "editType" : "edit", "file" : "crypto/lrw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/talitos.c" ], "commitId" : "9009b798b514e23e8b548d00fd0b24a81db79206", "timestamp" : 1563084574000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: talitos - rename alternative AEAD algos.\u000a\u000acommit a1a42f84011fae6ff08441a91aefeb7febc984fc upstream.\u000a\u000aThe talitos driver has two ways to perform AEAD depending on the\u000aHW capability. Some HW support both. It is needed to give them\u000adifferent names to distingish which one it is for instance when\u000aa test fails.\u000a\u000aSigned-off-by: Christophe Leroy \u000aFixes: 7405c8d7ff97 (\"crypto: talitos - templates for AEAD using HMAC_SNOOP_NO_AFEU\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:34 +0200", "id" : "9009b798b514e23e8b548d00fd0b24a81db79206", "msg" : "crypto: talitos - rename alternative AEAD algos.", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/talitos.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/soc/bcm/brcmstb/biuctrl.c" ], "commitId" : "113e03c5b977608e76feaace62b7b16604607701", "timestamp" : 1563084575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "soc: brcmstb: Fix error path for unsupported CPUs\u000a\u000a[ Upstream commit 490cad5a3ad6ef0bfd3168a5063140b982f3b22a ]\u000a\u000aIn case setup_hifcpubiuctrl_regs() returns an error, because of e.g:\u000aan unsupported CPU type, just catch that error and return instead of\u000ablindly continuing with the initialization. This fixes a NULL pointer\u000ade-reference with the code continuing without having a proper array of\u000aregisters to use.\u000a\u000aFixes: 22f7a9116eba (\"soc: brcmstb: Correct CPU_CREDIT_REG offset for Brahma-B53 CPUs\")\u000aSigned-off-by: Florian Fainelli \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:35 +0200", "id" : "113e03c5b977608e76feaace62b7b16604607701", "msg" : "soc: brcmstb: Fix error path for unsupported CPUs", "paths" : [ { "editType" : "edit", "file" : "drivers/soc/bcm/brcmstb/biuctrl.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/soc/bcm/brcmstb/biuctrl.c" ], "commitId" : "fc1c8cfd63d4b83075b34162e80b5d03124c3980", "timestamp" : 1563084575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "soc: bcm: brcmstb: biuctrl: Register writes require a barrier\u000a\u000a[ Upstream commit 6b23af0783a54efb348f0bd781b7850636023dbb ]\u000a\u000aThe BIUCTRL register writes require that a data barrier be inserted\u000aafter comitting the write to the register for the block to latch in the\u000arecently written values. Reads have no such requirement and are not\u000achanged.\u000a\u000aFixes: 34642650e5bc (\"soc: Move brcmstb to bcm/brcmstb\")\u000aSigned-off-by: Florian Fainelli \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:35 +0200", "id" : "fc1c8cfd63d4b83075b34162e80b5d03124c3980", "msg" : "soc: bcm: brcmstb: biuctrl: Register writes require a barrier", "paths" : [ { "editType" : "edit", "file" : "drivers/soc/bcm/brcmstb/biuctrl.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/mouse/elantech.c" ], "commitId" : "e87dee8db8e2e6e507acf715c117c9dd209b4859", "timestamp" : 1563084575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: elantech - enable middle button support on 2 ThinkPads\u000a\u000a[ Upstream commit aa440de3058a3ef530851f9ef373fbb5f694dbc3 ]\u000a\u000aAdding 2 new touchpad PNPIDs to enable middle button support.\u000a\u000aSigned-off-by: Aaron Ma \u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:35 +0200", "id" : "e87dee8db8e2e6e507acf715c117c9dd209b4859", "msg" : "Input: elantech - enable middle button support on 2 ThinkPads", "paths" : [ { "editType" : "edit", "file" : "drivers/input/mouse/elantech.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "samples/bpf/bpf_load.c" ], "commitId" : "a5755141b26ac3c966ac3551d49655c895eb9cd0", "timestamp" : 1563084575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "samples, bpf: fix to change the buffer size for read()\u000a\u000a[ Upstream commit f7c2d64bac1be2ff32f8e4f500c6e5429c1003e0 ]\u000a\u000aIf the trace for read is larger than 4096, the return\u000avalue sz will be 4096. This results in off-by-one error\u000aon buf:\u000a\u000a static char buf[4096];\u000a ssize_t sz;\u000a\u000a sz = read(trace_fd, buf, sizeof(buf));\u000a if (sz > 0) {\u000a buf[sz] = 0;\u000a puts(buf);\u000a }\u000a\u000aSigned-off-by: Chang-Hsien Tsai \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:35 +0200", "id" : "a5755141b26ac3c966ac3551d49655c895eb9cd0", "msg" : "samples, bpf: fix to change the buffer size for read()", "paths" : [ { "editType" : "edit", "file" : "samples/bpf/bpf_load.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "samples/bpf/task_fd_query_user.c" ], "commitId" : "3ab0e4bc01ef66567c7ddb39321d76428300fc08", "timestamp" : 1563084575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "samples, bpf: suppress compiler warning\u000a\u000a[ Upstream commit a195cefff49f60054998333e81ee95170ce8bf92 ]\u000a\u000aGCC 9 fails to calculate the size of local constant strings and produces a\u000afalse positive:\u000a\u000asamples/bpf/task_fd_query_user.c: In function ‘test_debug_fs_uprobe’:\u000asamples/bpf/task_fd_query_user.c:242:67: warning: ‘%s’ directive output may be truncated writing up to 255 bytes into a region of size 215 [-Wformat-truncation=]\u000a 242 | snprintf(buf, sizeof(buf), \"/sys/kernel/debug/tracing/events/%ss/%s/id\",\u000a | ^~\u000a 243 | event_type, event_alias);\u000a | ~~~~~~~~~~~\u000asamples/bpf/task_fd_query_user.c:242:2: note: ‘snprintf’ output between 45 and 300 bytes into a destination of size 256\u000a 242 | snprintf(buf, sizeof(buf), \"/sys/kernel/debug/tracing/events/%ss/%s/id\",\u000a | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\u000a 243 | event_type, event_alias);\u000a | ~~~~~~~~~~~~~~~~~~~~~~~~\u000a\u000aWorkaround this by lowering the buffer size to a reasonable value.\u000aRelated GCC Bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83431\u000a\u000aSigned-off-by: Matteo Croce \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:35 +0200", "id" : "3ab0e4bc01ef66567c7ddb39321d76428300fc08", "msg" : "samples, bpf: suppress compiler warning", "paths" : [ { "editType" : "edit", "file" : "samples/bpf/task_fd_query_user.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/riscv/net/bpf_jit_comp.c" ], "commitId" : "a1dbf72838b0f889d9c846076235eee527372d8f", "timestamp" : 1563084575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, riscv: clear target register high 32-bits for and/or/xor on ALU32\u000a\u000a[ Upstream commit fe121ee531d1362810bfd30f38a1b88b1d3d376c ]\u000a\u000aWhen using 32-bit subregisters (ALU32), the RISC-V JIT would not clear\u000athe high 32-bits of the target register and therefore generate\u000aincorrect code.\u000a\u000aE.g., in the following code:\u000a\u000a $ cat test.c\u000a unsigned int f(unsigned long long a,\u000a \u0009 unsigned int b)\u000a {\u000a \u0009return (unsigned int)a & b;\u000a }\u000a\u000a $ clang-9 -target bpf -O2 -emit-llvm -S test.c -o - | \\\u000a \u0009llc-9 -mattr=+alu32 -mcpu=v3\u000a \u0009.text\u000a \u0009.file\u0009\"test.c\"\u000a \u0009.globl\u0009f\u000a \u0009.p2align\u00093\u000a \u0009.type\u0009f,@function\u000a f:\u000a \u0009r0 = r1\u000a \u0009w0 &= w2\u000a \u0009exit\u000a .Lfunc_end0:\u000a \u0009.size\u0009f, .Lfunc_end0-f\u000a\u000aThe JIT would not clear the high 32-bits of r0 after the\u000aand-operation, which in this case might give an incorrect return\u000avalue.\u000a\u000aAfter this patch, that is not the case, and the upper 32-bits are\u000acleared.\u000a\u000aReported-by: Jiong Wang \u000aFixes: 2353ecc6f91f (\"bpf, riscv: add BPF JIT for RV64G\")\u000aSigned-off-by: Björn Töpel \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:35 +0200", "id" : "a1dbf72838b0f889d9c846076235eee527372d8f", "msg" : "bpf, riscv: clear target register high 32-bits for and/or/xor on ALU32", "paths" : [ { "editType" : "edit", "file" : "arch/riscv/net/bpf_jit_comp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/skmsg.h" ], "commitId" : "0579691bf74aab3785474070133f3827b6dd352f", "timestamp" : 1563084576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: sockmap, restore sk_write_space when psock gets dropped\u000a\u000a[ Upstream commit 186bcc3dcd106dc52d706117f912054b616666e1 ]\u000a\u000aOnce psock gets unlinked from its sock (sk_psock_drop), user-space can\u000astill trigger a call to sk->sk_write_space by setting TCP_NOTSENT_LOWAT\u000asocket option. This causes a null-ptr-deref because we try to read\u000apsock->saved_write_space from sk_psock_write_space:\u000a\u000a==================================================================\u000aBUG: KASAN: null-ptr-deref in sk_psock_write_space+0x69/0x80\u000aRead of size 8 at addr 00000000000001a0 by task sockmap-echo/131\u000a\u000aCPU: 0 PID: 131 Comm: sockmap-echo Not tainted 5.2.0-rc1-00094-gf49aa1de9836 #81\u000aHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\u000a?-20180724_192412-buildhw-07.phx2.fedoraproject.org-1.fc29 04/01/2014\u000aCall Trace:\u000a ? sk_psock_write_space+0x69/0x80\u000a __kasan_report.cold.2+0x5/0x3f\u000a ? sk_psock_write_space+0x69/0x80\u000a kasan_report+0xe/0x20\u000a sk_psock_write_space+0x69/0x80\u000a tcp_setsockopt+0x69a/0xfc0\u000a ? tcp_shutdown+0x70/0x70\u000a ? fsnotify+0x5b0/0x5f0\u000a ? remove_wait_queue+0x90/0x90\u000a ? __fget_light+0xa5/0xf0\u000a __sys_setsockopt+0xe6/0x180\u000a ? sockfd_lookup_light+0xb0/0xb0\u000a ? vfs_write+0x195/0x210\u000a ? ksys_write+0xc9/0x150\u000a ? __x64_sys_read+0x50/0x50\u000a ? __bpf_trace_x86_fpu+0x10/0x10\u000a __x64_sys_setsockopt+0x61/0x70\u000a do_syscall_64+0xc5/0x520\u000a ? vmacache_find+0xc0/0x110\u000a ? syscall_return_slowpath+0x110/0x110\u000a ? handle_mm_fault+0xb4/0x110\u000a ? entry_SYSCALL_64_after_hwframe+0x3e/0xbe\u000a ? trace_hardirqs_off_caller+0x4b/0x120\u000a ? trace_hardirqs_off_thunk+0x1a/0x3a\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000aRIP: 0033:0x7f2e5e7cdcce\u000aCode: d8 64 89 02 48 c7 c0 ff ff ff ff eb b1 66 2e 0f 1f 84 00 00 00 00 00\u000a0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 01 f0 ff\u000aff 73 01 c3 48 8b 0d 8a 11 0c 00 f7 d8 64 89 01 48\u000aRSP: 002b:00007ffed011b778 EFLAGS: 00000206 ORIG_RAX: 0000000000000036\u000aRAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f2e5e7cdcce\u000aRDX: 0000000000000019 RSI: 0000000000000006 RDI: 0000000000000007\u000aRBP: 00007ffed011b790 R08: 0000000000000004 R09: 00007f2e5e84ee80\u000aR10: 00007ffed011b788 R11: 0000000000000206 R12: 00007ffed011b78c\u000aR13: 00007ffed011b788 R14: 0000000000000007 R15: 0000000000000068\u000a==================================================================\u000a\u000aRestore the saved sk_write_space callback when psock is being dropped to\u000afix the crash.\u000a\u000aSigned-off-by: Jakub Sitnicki \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:36 +0200", "id" : "0579691bf74aab3785474070133f3827b6dd352f", "msg" : "bpf: sockmap, restore sk_write_space when psock gets dropped", "paths" : [ { "editType" : "edit", "file" : "include/linux/skmsg.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/wireless/util.c" ], "commitId" : "234d92fc85367f5655334711bba4546a2cfcb9ed", "timestamp" : 1563084576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mac80211: fix rate reporting inside cfg80211_calculate_bitrate_he()\u000a\u000a[ Upstream commit 25d16d124a5e249e947c0487678b61dcff25cf8b ]\u000a\u000aThe reported rate is not scaled down correctly. After applying this patch,\u000athe function will behave just like the v/ht equivalents.\u000a\u000aSigned-off-by: Shashidhar Lakkavalli \u000aSigned-off-by: John Crispin \u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:36 +0200", "id" : "234d92fc85367f5655334711bba4546a2cfcb9ed", "msg" : "mac80211: fix rate reporting inside cfg80211_calculate_bitrate_he()", "paths" : [ { "editType" : "edit", "file" : "net/wireless/util.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/core/skbuff.c" ], "commitId" : "8badadedccebc8d67f2920c7adc153e344777d47", "timestamp" : 1563084576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: sockmap, fix use after free from sleep in psock backlog workqueue\u000a\u000a[ Upstream commit bd95e678e0f6e18351ecdc147ca819145db9ed7b ]\u000a\u000aBacklog work for psock (sk_psock_backlog) might sleep while waiting\u000afor memory to free up when sending packets. However, while sleeping\u000athe socket may be closed and removed from the map by the user space\u000aside.\u000a\u000aThis breaks an assumption in sk_stream_wait_memory, which expects the\u000await queue to be still there when it wakes up resulting in a\u000ause-after-free shown below. To fix his mark sendmsg as MSG_DONTWAIT\u000ato avoid the sleep altogether. We already set the flag for the\u000asendpage case but we missed the case were sendmsg is used.\u000aSockmap is currently the only user of skb_send_sock_locked() so only\u000athe sockmap paths should be impacted.\u000a\u000a==================================================================\u000aBUG: KASAN: use-after-free in remove_wait_queue+0x31/0x70\u000aWrite of size 8 at addr ffff888069a0c4e8 by task kworker/0:2/110\u000a\u000aCPU: 0 PID: 110 Comm: kworker/0:2 Not tainted 5.0.0-rc2-00335-g28f9d1a3d4fe-dirty #14\u000aHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-2.fc27 04/01/2014\u000aWorkqueue: events sk_psock_backlog\u000aCall Trace:\u000a print_address_description+0x6e/0x2b0\u000a ? remove_wait_queue+0x31/0x70\u000a kasan_report+0xfd/0x177\u000a ? remove_wait_queue+0x31/0x70\u000a ? remove_wait_queue+0x31/0x70\u000a remove_wait_queue+0x31/0x70\u000a sk_stream_wait_memory+0x4dd/0x5f0\u000a ? sk_stream_wait_close+0x1b0/0x1b0\u000a ? wait_woken+0xc0/0xc0\u000a ? tcp_current_mss+0xc5/0x110\u000a tcp_sendmsg_locked+0x634/0x15d0\u000a ? tcp_set_state+0x2e0/0x2e0\u000a ? __kasan_slab_free+0x1d1/0x230\u000a ? kmem_cache_free+0x70/0x140\u000a ? sk_psock_backlog+0x40c/0x4b0\u000a ? process_one_work+0x40b/0x660\u000a ? worker_thread+0x82/0x680\u000a ? kthread+0x1b9/0x1e0\u000a ? ret_from_fork+0x1f/0x30\u000a ? check_preempt_curr+0xaf/0x130\u000a ? iov_iter_kvec+0x5f/0x70\u000a ? kernel_sendmsg_locked+0xa0/0xe0\u000a skb_send_sock_locked+0x273/0x3c0\u000a ? skb_splice_bits+0x180/0x180\u000a ? start_thread+0xe0/0xe0\u000a ? update_min_vruntime.constprop.27+0x88/0xc0\u000a sk_psock_backlog+0xb3/0x4b0\u000a ? strscpy+0xbf/0x1e0\u000a process_one_work+0x40b/0x660\u000a worker_thread+0x82/0x680\u000a ? process_one_work+0x660/0x660\u000a kthread+0x1b9/0x1e0\u000a ? __kthread_create_on_node+0x250/0x250\u000a ret_from_fork+0x1f/0x30\u000a\u000aFixes: 20bf50de3028c (\"skbuff: Function to send an skbuf on a socket\")\u000aReported-by: Jakub Sitnicki \u000aTested-by: Jakub Sitnicki \u000aSigned-off-by: John Fastabend \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:36 +0200", "id" : "8badadedccebc8d67f2920c7adc153e344777d47", "msg" : "bpf: sockmap, fix use after free from sleep in psock backlog workqueue", "paths" : [ { "editType" : "edit", "file" : "net/core/skbuff.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/soundwire/stream.c" ], "commitId" : "867abba5b0c6efc857ed5423c76792f49ca4d434", "timestamp" : 1563084576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "soundwire: stream: fix out of boundary access on port properties\u000a\u000a[ Upstream commit 03ecad90d3798be11b033248bbd4bbff4425a1c7 ]\u000a\u000aAssigning local iterator to array element and using it again for\u000aindexing would cross the array boundary.\u000aFix this by directly referring array element without using the local\u000avariable.\u000a\u000aSigned-off-by: Srinivas Kandagatla \u000aAcked-by: Pierre-Louis Bossart \u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:36 +0200", "id" : "867abba5b0c6efc857ed5423c76792f49ca4d434", "msg" : "soundwire: stream: fix out of boundary access on port properties", "paths" : [ { "editType" : "edit", "file" : "drivers/soundwire/stream.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/iio/cdc/ad7150.c" ], "commitId" : "179848f4d5d39b6b57dc4f95a33d684a69430a2c", "timestamp" : 1563084576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging:iio:ad7150: fix threshold mode config bit\u000a\u000a[ Upstream commit df4d737ee4d7205aaa6275158aeebff87fd14488 ]\u000a\u000aAccording to the AD7150 configuration register description, bit 7 assumes\u000avalue 1 when the threshold mode is fixed and 0 when it is adaptive,\u000ahowever, the operation that identifies this mode was considering the\u000aopposite values.\u000a\u000aThis patch renames the boolean variable to describe it correctly and\u000aproperly replaces it in the places where it is used.\u000a\u000aFixes: 531efd6aa0991 (\"staging:iio:adc:ad7150: chan_spec conv + i2c_smbus commands + drop unused poweroff timeout control.\")\u000aSigned-off-by: Melissa Wen \u000aSigned-off-by: Jonathan Cameron \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:36 +0200", "id" : "179848f4d5d39b6b57dc4f95a33d684a69430a2c", "msg" : "staging:iio:ad7150: fix threshold mode config bit", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/iio/cdc/ad7150.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/mac80211/mesh.c" ], "commitId" : "452989b756c6a380825b03148ef3fe0d03bea2be", "timestamp" : 1563084576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mac80211: mesh: fix RCU warning\u000a\u000a[ Upstream commit 551842446ed695641a00782cd118cbb064a416a1 ]\u000a\u000aifmsh->csa is an RCU-protected pointer. The writer context\u000ain ieee80211_mesh_finish_csa() is already mutually\u000aexclusive with wdev->sdata.mtx, but the RCU checker did\u000anot know this. Use rcu_dereference_protected() to avoid a\u000awarning.\u000a\u000afixes the following warning:\u000a\u000a[ 12.519089] =============================\u000a[ 12.520042] WARNING: suspicious RCU usage\u000a[ 12.520652] 5.1.0-rc7-wt+ #16 Tainted: G W\u000a[ 12.521409] -----------------------------\u000a[ 12.521972] net/mac80211/mesh.c:1223 suspicious rcu_dereference_check() usage!\u000a[ 12.522928] other info that might help us debug this:\u000a[ 12.523984] rcu_scheduler_active = 2, debug_locks = 1\u000a[ 12.524855] 5 locks held by kworker/u8:2/152:\u000a[ 12.525438] #0: 00000000057be08c ((wq_completion)phy0){+.+.}, at: process_one_work+0x1a2/0x620\u000a[ 12.526607] #1: 0000000059c6b07a ((work_completion)(&sdata->csa_finalize_work)){+.+.}, at: process_one_work+0x1a2/0x620\u000a[ 12.528001] #2: 00000000f184ba7d (&wdev->mtx){+.+.}, at: ieee80211_csa_finalize_work+0x2f/0x90\u000a[ 12.529116] #3: 00000000831a1f54 (&local->mtx){+.+.}, at: ieee80211_csa_finalize_work+0x47/0x90\u000a[ 12.530233] #4: 00000000fd06f988 (&local->chanctx_mtx){+.+.}, at: ieee80211_csa_finalize_work+0x51/0x90\u000a\u000aSigned-off-by: Thomas Pedersen \u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:36 +0200", "id" : "452989b756c6a380825b03148ef3fe0d03bea2be", "msg" : "mac80211: mesh: fix RCU warning", "paths" : [ { "editType" : "edit", "file" : "net/mac80211/mesh.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/mac80211/mesh.c" ], "commitId" : "6017f0892221ee66cdf189664ae3ef644d1d7d75", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mac80211: free peer keys before vif down in mesh\u000a\u000a[ Upstream commit 0112fa557c3bb3a002bc85760dc3761d737264d3 ]\u000a\u000afreeing peer keys after vif down is resulting in peer key uninstall\u000ato fail due to interface lookup failure. so fix that.\u000a\u000aSigned-off-by: Pradeep Kumar Chitrapu \u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "6017f0892221ee66cdf189664ae3ef644d1d7d75", "msg" : "mac80211: free peer keys before vif down in mesh", "paths" : [ { "editType" : "edit", "file" : "net/mac80211/mesh.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/dra7-l4.dtsi" ], "commitId" : "af5275fc48d2c8e5cd6a72148068be2e9bafc88f", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: Drop bogus CLKSEL for timer12 on dra7\u000a\u000a[ Upstream commit 34f61de87017aff3c8306280d196dddb1e168a88 ]\u000a\u000aThere is no CLKSEL for timer12 on dra7 unlike for timer1. This\u000acauses issues on booting the device that Tomi noticed if\u000aDEBUG_SLAB is enabled and the clkctrl clock does not properly\u000ahandle non-existing clock. Let's drop the bogus CLKSEL clock,\u000athe clkctrl clock handling gets fixed separately.\u000a\u000aCc: Peter Ujfalusi \u000aCc: Tero Kristo \u000aCc: Tomi Valkeinen \u000aReported-by: Tomi Valkeinen \u000aTested-by: Tomi Valkeinen \u000aTested-by: Peter Ujfalusi \u000aFixes: 4ed0dfe3cf39 (\"ARM: dts: dra7: Move l4 child devices to probe them with ti-sysc\")\u000aSigned-off-by: Tony Lindgren \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "af5275fc48d2c8e5cd6a72148068be2e9bafc88f", "msg" : "ARM: dts: Drop bogus CLKSEL for timer12 on dra7", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/dra7-l4.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/marvell/mwifiex/scan.c" ], "commitId" : "cb48f5e50582bf44f63599b78941b325a17fa1ec", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mwifiex: Fix possible buffer overflows at parsing bss descriptor\u000a\u000a[ Upstream commit 13ec7f10b87f5fc04c4ccbd491c94c7980236a74 ]\u000a\u000amwifiex_update_bss_desc_with_ie() calls memcpy() unconditionally in\u000aa couple places without checking the destination size. Since the\u000asource is given from user-space, this may trigger a heap buffer\u000aoverflow.\u000a\u000aFix it by putting the length check before performing memcpy().\u000a\u000aThis fix addresses CVE-2019-3846.\u000a\u000aReported-by: huangwen \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "cb48f5e50582bf44f63599b78941b325a17fa1ec", "msg" : "mwifiex: Fix possible buffer overflows at parsing bss descriptor", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/scan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/riscv/net/bpf_jit_comp.c" ], "commitId" : "bb1965c6d7afe5613adc882785a1a183085a26c8", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, riscv: clear high 32 bits for ALU32 add/sub/neg/lsh/rsh/arsh\u000a\u000a[ Upstream commit 1e692f09e091bf5c8b38384f297d6dae5dbf0f12 ]\u000a\u000aIn BPF, 32-bit ALU operations should zero-extend their results into\u000athe 64-bit registers.\u000a\u000aThe current BPF JIT on RISC-V emits incorrect instructions that perform\u000asign extension only (e.g., addw, subw) on 32-bit add, sub, lsh, rsh,\u000aarsh, and neg. This behavior diverges from the interpreter and JITs\u000afor other architectures.\u000a\u000aThis patch fixes the bugs by performing zero extension on the destination\u000aregister of 32-bit ALU operations.\u000a\u000aFixes: 2353ecc6f91f (\"bpf, riscv: add BPF JIT for RV64G\")\u000aCc: Xi Wang \u000aSigned-off-by: Luke Nelson \u000aAcked-by: Song Liu \u000aAcked-by: Björn Töpel \u000aReviewed-by: Palmer Dabbelt \u000aSigned-off-by: Alexei Starovoitov \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "bb1965c6d7afe5613adc882785a1a183085a26c8", "msg" : "bpf, riscv: clear high 32 bits for ALU32 add/sub/neg/lsh/rsh/arsh", "paths" : [ { "editType" : "edit", "file" : "arch/riscv/net/bpf_jit_comp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/pcie/internal.h", "drivers/net/wireless/intel/iwlwifi/mvm/fw.c", "drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c", "drivers/net/wireless/intel/iwlwifi/mvm/ops.c", "drivers/net/wireless/intel/iwlwifi/mvm/mvm.h" ], "commitId" : "597bf51869f0d830b8def6a928244e17aef8774e", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: fix load in rfkill flow for unified firmware\u000a\u000a[ Upstream commit b3500b472c880b5abe90ffd5c4a25aa736f906ad ]\u000a\u000aWhen we have a single image (same firmware image for INIT and\u000aOPERATIONAL), we couldn't load the driver and register to the\u000astack if we had hardware RF-Kill asserted.\u000a\u000aFix this. This required a few changes:\u000a\u000a1) Run the firmware as part of the INIT phase even if its\u000a ucode_type is not IWL_UCODE_INIT.\u000a2) Send the commands that are sent to the unified image in\u000a INIT flow even in RF-Kill.\u000a3) Don't ask the transport to stop the hardware upon RF-Kill\u000a interrupt if the RF-Kill is asserted.\u000a4) Allow the RF-Kill interrupt to take us out of L1A so that\u000a the RF-Kill interrupt will be received by the host (to\u000a enable the radio).\u000a\u000aSigned-off-by: Emmanuel Grumbach \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "597bf51869f0d830b8def6a928244e17aef8774e", "msg" : "iwlwifi: fix load in rfkill flow for unified firmware", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/ops.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/mvm.h" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/internal.h" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/fw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/iwl-prph.h", "drivers/net/wireless/intel/iwlwifi/pcie/trans.c" ], "commitId" : "c72a7c2e945ad23eab99817a0cc5bfb344cbcd11", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: clear persistence bit according to device family\u000a\u000a[ Upstream commit 44f61b5c832c4085fcf476484efeaeef96dcfb8b ]\u000a\u000aThe driver attempts to clear persistence bit on any device familiy even\u000athough only 9000 and 22000 families require it. Clear the bit only on\u000athe relevant device families.\u000a\u000aEach HW has different address to the write protection register. Use the\u000aright register for each HW\u000a\u000aSigned-off-by: Shahar S Matityahu \u000aFixes: 8954e1eb2270 (\"iwlwifi: trans: Clear persistence bit when starting the FW\")\u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "c72a7c2e945ad23eab99817a0cc5bfb344cbcd11", "msg" : "iwlwifi: clear persistence bit according to device family", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/trans.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/iwl-prph.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/pcie/trans.c" ], "commitId" : "8c02f59eb13b92a1e01a1a329aff1dac4fc4be3f", "timestamp" : 1563084577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: fix AX201 killer sku loading firmware issue\u000a\u000a[ Upstream commit b17dc0632a17fbfe66b34ee7c24e1cc10cfc503e ]\u000a\u000aWhen try to bring up the AX201 2 killer sku, we\u000arun into:\u000a[81261.392463] iwlwifi 0000:01:00.0: loaded firmware version 46.8c20f243.0 op_mode iwlmvm\u000a[81261.407407] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AX 22000, REV=0x340\u000a[81262.424778] iwlwifi 0000:01:00.0: Collecting data: trigger 16 fired.\u000a[81262.673359] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:\u000a[81262.673365] iwlwifi 0000:01:00.0: Status: 0x00000000, count: -906373681\u000a[81262.673368] iwlwifi 0000:01:00.0: Loaded firmware version: 46.8c20f243.0\u000a[81262.673371] iwlwifi 0000:01:00.0: 0x507C015D | ADVANCED_SYSASSERT\u000a\u000aFix this issue by adding 2 more cfg to avoid modifying the\u000aoriginal cfg configuration.\u000a\u000aSigned-off-by: Matt Chen \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:37 +0200", "id" : "8c02f59eb13b92a1e01a1a329aff1dac4fc4be3f", "msg" : "iwlwifi: fix AX201 killer sku loading firmware issue", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/trans.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/iwl-drv.c" ], "commitId" : "687f9cc72e09858b080a7d65e1c3253e643f6535", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: Fix double-free problems in iwl_req_fw_callback()\u000a\u000a[ Upstream commit a8627176b0de7ba3f4524f641ddff4abf23ae4e4 ]\u000a\u000aIn the error handling code of iwl_req_fw_callback(), iwl_dealloc_ucode()\u000ais called to free data. In iwl_drv_stop(), iwl_dealloc_ucode() is called\u000aagain, which can cause double-free problems.\u000a\u000aTo fix this bug, the call to iwl_dealloc_ucode() in\u000aiwl_req_fw_callback() is deleted.\u000a\u000aThis bug is found by a runtime fuzzing tool named FIZZER written by us.\u000a\u000aSigned-off-by: Jia-Ju Bai \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "687f9cc72e09858b080a7d65e1c3253e643f6535", "msg" : "iwlwifi: Fix double-free problems in iwl_req_fw_callback()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/iwl-drv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/marvell/mwifiex/ie.c" ], "commitId" : "e9111176d9c195ba709245f1bf1d3d1dae5cd22a", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mwifiex: Fix heap overflow in mwifiex_uap_parse_tail_ies()\u000a\u000a[ Upstream commit 69ae4f6aac1578575126319d3f55550e7e440449 ]\u000a\u000aA few places in mwifiex_uap_parse_tail_ies() perform memcpy()\u000aunconditionally, which may lead to either buffer overflow or read over\u000aboundary.\u000a\u000aThis patch addresses the issues by checking the read size and the\u000adestination size at each place more properly. Along with the fixes,\u000athe patch cleans up the code slightly by introducing a temporary\u000avariable for the token size, and unifies the error path with the\u000astandard goto statement.\u000a\u000aReported-by: huangwen \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "e9111176d9c195ba709245f1bf1d3d1dae5cd22a", "msg" : "mwifiex: Fix heap overflow in mwifiex_uap_parse_tail_ies()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/ie.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv6/netfilter/nf_conntrack_reasm.c" ], "commitId" : "53374b5aa7392edcdc67c33a75fce30d4d109916", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "netfilter: ipv6: nf_defrag: fix leakage of unqueued fragments\u000a\u000a[ Upstream commit a0d56cb911ca301de81735f1d73c2aab424654ba ]\u000a\u000aWith commit 997dd9647164 (\"net: IP6 defrag: use rbtrees in\u000anf_conntrack_reasm.c\"), nf_ct_frag6_reasm() is now called from\u000anf_ct_frag6_queue(). With this change, nf_ct_frag6_queue() can fail\u000aafter the skb has been added to the fragment queue and\u000anf_ct_frag6_gather() was adapted to handle this case.\u000a\u000aBut nf_ct_frag6_queue() can still fail before the fragment has been\u000aqueued. nf_ct_frag6_gather() can't handle this case anymore, because it\u000ahas no way to know if nf_ct_frag6_queue() queued the fragment before\u000afailing. If it didn't, the skb is lost as the error code is overwritten\u000awith -EINPROGRESS.\u000a\u000aFix this by setting -EINPROGRESS directly in nf_ct_frag6_queue(), so\u000athat nf_ct_frag6_gather() can propagate the error as is.\u000a\u000aFixes: 997dd9647164 (\"net: IP6 defrag: use rbtrees in nf_conntrack_reasm.c\")\u000aSigned-off-by: Guillaume Nault \u000aSigned-off-by: Pablo Neira Ayuso \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "53374b5aa7392edcdc67c33a75fce30d4d109916", "msg" : "netfilter: ipv6: nf_defrag: fix leakage of unqueued fragments", "paths" : [ { "editType" : "edit", "file" : "net/ipv6/netfilter/nf_conntrack_reasm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/bpf/bpftool/map.c" ], "commitId" : "0493503b1e28a8d096d241903f338303b5c908c2", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tools: bpftool: Fix JSON output when lookup fails\u000a\u000a[ Upstream commit 1884c066579a7a274dd981a4d9639ca63db66a23 ]\u000a\u000aIn commit 9a5ab8bf1d6d (\"tools: bpftool: turn err() and info() macros\u000ainto functions\") one case of error reporting was special cased, so it\u000acould report a lookup error for a specific key when dumping the map\u000aelement. What the code forgot to do is to wrap the key and value keys\u000ainto a JSON object, so an example output of pretty JSON dump of a\u000asockhash map (which does not support looking up its values) is:\u000a\u000a[\u000a \"key\": [\"0x0a\",\"0x41\",\"0x00\",\"0x02\",\"0x1f\",\"0x78\",\"0x00\",\"0x00\"\u000a ],\u000a \"value\": {\u000a \"error\": \"Operation not supported\"\u000a },\u000a \"key\": [\"0x0a\",\"0x41\",\"0x00\",\"0x02\",\"0x1f\",\"0x78\",\"0x00\",\"0x01\"\u000a ],\u000a \"value\": {\u000a \"error\": \"Operation not supported\"\u000a }\u000a]\u000a\u000aNote the key-value pairs inside the toplevel array. They should be\u000awrapped inside a JSON object, otherwise it is an invalid JSON. This\u000acommit fixes this, so the output now is:\u000a\u000a[{\u000a \"key\": [\"0x0a\",\"0x41\",\"0x00\",\"0x02\",\"0x1f\",\"0x78\",\"0x00\",\"0x00\"\u000a ],\u000a \"value\": {\u000a \"error\": \"Operation not supported\"\u000a }\u000a },{\u000a \"key\": [\"0x0a\",\"0x41\",\"0x00\",\"0x02\",\"0x1f\",\"0x78\",\"0x00\",\"0x01\"\u000a ],\u000a \"value\": {\u000a \"error\": \"Operation not supported\"\u000a }\u000a }\u000a]\u000a\u000aFixes: 9a5ab8bf1d6d (\"tools: bpftool: turn err() and info() macros into functions\")\u000aCc: Quentin Monnet \u000aSigned-off-by: Krzesimir Nowak \u000aAcked-by: Andrii Nakryiko \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "0493503b1e28a8d096d241903f338303b5c908c2", "msg" : "tools: bpftool: Fix JSON output when lookup fails", "paths" : [ { "editType" : "edit", "file" : "tools/bpf/bpftool/map.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/soundwire/stream.c" ], "commitId" : "2d48fa440c70bb22153da18c753e66846ed74a61", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "soundwire: stream: fix bad unlock balance\u000a\u000a[ Upstream commit 9315d904c7e8f38886e2820fa6cb8d0fa723ea21 ]\u000a\u000athe msg lock is taken for multi-link cases only but released\u000aunconditionally, leading to an unlock balance warning for single-link usages\u000aThis patch fixes this.\u000a\u000a =====================================\u000a WARNING: bad unlock balance detected!\u000a 5.1.0-16506-gc1c383a6f0a2-dirty #1523 Tainted: G W\u000a -------------------------------------\u000a aplay/2954 is trying to release lock (&bus->msg_lock) at:\u000a do_bank_switch+0x21c/0x480\u000a but there are no more locks to release!\u000a\u000aSigned-off-by: Srinivas Kandagatla \u000aAcked-by: Pierre-Louis Bossart \u000aAcked-by: Sanyog Kale \u000a[vkoul: edited the change log as suggested by Pierre]\u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "2d48fa440c70bb22153da18c753e66846ed74a61", "msg" : "soundwire: stream: fix bad unlock balance", "paths" : [ { "editType" : "edit", "file" : "drivers/soundwire/stream.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/soundwire/intel.c" ], "commitId" : "0ef90e54de1359c5d954e0d4bb8978e5b113f002", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "soundwire: intel: set dai min and max channels correctly\u000a\u000a[ Upstream commit 39194128701bf2af9bbc420ffe6e3cb5d2c16061 ]\u000a\u000aLooks like there is a copy paste error.\u000aThis patch fixes it!\u000a\u000aSigned-off-by: Srinivas Kandagatla \u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "0ef90e54de1359c5d954e0d4bb8978e5b113f002", "msg" : "soundwire: intel: set dai min and max channels correctly", "paths" : [ { "editType" : "edit", "file" : "drivers/soundwire/intel.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv6/netfilter/nf_conntrack_reasm.c" ], "commitId" : "c7e43c33079692372e3d0bfed047bdd43853d72c", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "netfilter: ipv6: nf_defrag: accept duplicate fragments again\u000a\u000a[ Upstream commit 8a3dca632538c550930ce8bafa8c906b130d35cf ]\u000a\u000aWhen fixing the skb leak introduced by the conversion to rbtree, I\u000aforgot about the special case of duplicate fragments. The condition\u000aunder the 'insert_error' label isn't effective anymore as\u000anf_ct_frg6_gather() doesn't override the returned value anymore. So\u000aduplicate fragments now get NF_DROP verdict.\u000a\u000aTo accept duplicate fragments again, handle them specially as soon as\u000ainet_frag_queue_insert() reports them. Return -EINPROGRESS which will\u000atranslate to NF_STOLEN verdict, like any accepted fragment. However,\u000asuch packets don't carry any new information and aren't queued, so we\u000ajust drop them immediately.\u000a\u000aFixes: a0d56cb911ca (\"netfilter: ipv6: nf_defrag: fix leakage of unqueued fragments\")\u000aSigned-off-by: Guillaume Nault \u000aSigned-off-by: Pablo Neira Ayuso \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "c7e43c33079692372e3d0bfed047bdd43853d72c", "msg" : "netfilter: ipv6: nf_defrag: accept duplicate fragments again", "paths" : [ { "editType" : "edit", "file" : "net/ipv6/netfilter/nf_conntrack_reasm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/devicetree/bindings/net/can/microchip,mcp251x.txt" ], "commitId" : "7b9e3c98ecdb4f512422b52f372d3e8f12c79a46", "timestamp" : 1563084578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dt-bindings: can: mcp251x: add mcp25625 support\u000a\u000a[ Upstream commit 0df82dcd55832a99363ab7f9fab954fcacdac3ae ]\u000a\u000aFully compatible with mcp2515, the mcp25625 have integrated transceiver.\u000a\u000aThis patch add the mcp25625 to the device tree bindings documentation.\u000a\u000aSigned-off-by: Sean Nyekjaer \u000aSigned-off-by: Marc Kleine-Budde \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:38 +0200", "id" : "7b9e3c98ecdb4f512422b52f372d3e8f12c79a46", "msg" : "dt-bindings: can: mcp251x: add mcp25625 support", "paths" : [ { "editType" : "edit", "file" : "Documentation/devicetree/bindings/net/can/microchip,mcp251x.txt" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/can/spi/mcp251x.c", "drivers/net/can/spi/Kconfig" ], "commitId" : "caad90046a157a646530cf85d5a6b19f535d6581", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "can: mcp251x: add support for mcp25625\u000a\u000a[ Upstream commit 35b7fa4d07c43ad79b88e6462119e7140eae955c ]\u000a\u000aFully compatible with mcp2515, the mcp25625 have integrated transceiver.\u000a\u000aThis patch adds support for the mcp25625 to the existing mcp251x driver.\u000a\u000aSigned-off-by: Sean Nyekjaer \u000aSigned-off-by: Marc Kleine-Budde \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "caad90046a157a646530cf85d5a6b19f535d6581", "msg" : "can: mcp251x: add support for mcp25625", "paths" : [ { "editType" : "edit", "file" : "drivers/net/can/spi/Kconfig" }, { "editType" : "edit", "file" : "drivers/net/can/spi/mcp251x.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/can/m_can/m_can.c" ], "commitId" : "677eaf97288305ea5f701aaf0b746e56c72171df", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "can: m_can: implement errata \"Needless activation of MRAF irq\"\u000a\u000a[ Upstream commit 3e82f2f34c930a2a0a9e69fdc2de2f2f1388b442 ]\u000a\u000aDuring frame reception while the MCAN is in Error Passive state and the\u000aReceive Error Counter has thevalue MCAN_ECR.REC = 127, it may happen\u000athat MCAN_IR.MRAF is set although there was no Message RAM access\u000afailure. If MCAN_IR.MRAF is enabled, an interrupt to the Host CPU is\u000agenerated.\u000a\u000aWork around:\u000aThe Message RAM Access Failure interrupt routine needs to check whether\u000a\u000a MCAN_ECR.RP = '1' and MCAN_ECR.REC = '127'.\u000a\u000aIn this case, reset MCAN_IR.MRAF. No further action is required.\u000aThis affects versions older than 3.2.0\u000a\u000aErrata explained on Sama5d2 SoC which includes this hardware block:\u000ahttp://ww1.microchip.com/downloads/en/DeviceDoc/SAMA5D2-Family-Silicon-Errata-and-Data-Sheet-Clarification-DS80000803B.pdf\u000achapter 6.2\u000a\u000aReproducibility: If 2 devices with m_can are connected back to back,\u000aconfiguring different bitrate on them will lead to interrupt storm on\u000athe receiving side, with error \"Message RAM access failure occurred\".\u000aAnother way is to have a bad hardware connection. Bad wire connection\u000acan lead to this issue as well.\u000a\u000aThis patch fixes the issue according to provided workaround.\u000a\u000aSigned-off-by: Eugen Hristev \u000aReviewed-by: Ludovic Desroches \u000aSigned-off-by: Marc Kleine-Budde \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "677eaf97288305ea5f701aaf0b746e56c72171df", "msg" : "can: m_can: implement errata \"Needless activation of MRAF irq\"", "paths" : [ { "editType" : "edit", "file" : "drivers/net/can/m_can/m_can.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/can/af_can.c" ], "commitId" : "bdfd30f912dacf98ac55e0fba038767e77ce4618", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "can: af_can: Fix error path of can_init()\u000a\u000a[ Upstream commit c5a3aed1cd3152429348ee1fe5cdcca65fe901ce ]\u000a\u000aThis patch add error path for can_init() to avoid possible crash if some\u000aerror occurs.\u000a\u000aFixes: 0d66548a10cb (\"[CAN]: Add PF_CAN core module\")\u000aSigned-off-by: YueHaibing \u000aAcked-by: Oliver Hartkopp \u000aSigned-off-by: Marc Kleine-Budde \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "bdfd30f912dacf98ac55e0fba038767e77ce4618", "msg" : "can: af_can: Fix error path of can_init()", "paths" : [ { "editType" : "edit", "file" : "net/can/af_can.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/can/flexcan.c" ], "commitId" : "6a38e8c3d5b2d88410d60ae5876c1a0621f04f38", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "can: flexcan: Remove unneeded registration message\u000a\u000a[ Upstream commit eb503004a7e563d543c9cb869907156de7efe720 ]\u000a\u000aCurrently the following message is observed when the flexcan\u000adriver is probed:\u000a\u000aflexcan 2090000.flexcan: device registered (reg_base=(ptrval), irq=23)\u000a\u000aThe reason for printing 'ptrval' is explained at\u000aDocumentation/core-api/printk-formats.rst:\u000a\u000a\"Pointers printed without a specifier extension (i.e unadorned %p) are\u000ahashed to prevent leaking information about the kernel memory layout. This\u000ahas the added benefit of providing a unique identifier. On 64-bit machines\u000athe first 32 bits are zeroed. The kernel will print ``(ptrval)`` until it\u000agathers enough entropy.\"\u000a\u000aInstead of passing %pK, which can print the correct address, simply\u000aremove the entire message as it is not really that useful.\u000a\u000aSigned-off-by: Fabio Estevam \u000aSigned-off-by: Marc Kleine-Budde \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "6a38e8c3d5b2d88410d60ae5876c1a0621f04f38", "msg" : "can: flexcan: Remove unneeded registration message", "paths" : [ { "editType" : "edit", "file" : "drivers/net/can/flexcan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/phy/Makefile", "drivers/net/phy/Kconfig", "drivers/net/phy/ax88796b.c", "drivers/net/phy/asix.c", "drivers/net/ethernet/8390/Kconfig" ], "commitId" : "fe218cfad2fb8677a1becc90ecc98c9376dffa65", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: phy: rename Asix Electronics PHY driver\u000a\u000a[ Upstream commit a9520543b123bbd7275a0ab8d0375a5412683b41 ]\u000a\u000a[Resent to net instead of net-next - may clash with Anders Roxell's patch\u000aseries addressing duplicate module names]\u000a\u000aCommit 31dd83b96641 (\"net-next: phy: new Asix Electronics PHY driver\")\u000aintroduced a new PHY driver drivers/net/phy/asix.c that causes a module\u000aname conflict with a pre-existiting driver (drivers/net/usb/asix.c).\u000a\u000aThe PHY driver is used by the X-Surf 100 ethernet card driver, and loaded\u000aby that driver via its PHY ID. A rename of the driver looks unproblematic.\u000a\u000aRename PHY driver to ax88796b.c in order to resolve name conflict.\u000a\u000aSigned-off-by: Michael Schmitz \u000aTested-by: Michael Schmitz \u000aFixes: 31dd83b96641 (\"net-next: phy: new Asix Electronics PHY driver\")\u000aReviewed-by: Andrew Lunn \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "fe218cfad2fb8677a1becc90ecc98c9376dffa65", "msg" : "net: phy: rename Asix Electronics PHY driver", "paths" : [ { "editType" : "edit", "file" : "drivers/net/phy/Kconfig" }, { "editType" : "edit", "file" : "drivers/net/ethernet/8390/Kconfig" }, { "editType" : "delete", "file" : "drivers/net/phy/asix.c" }, { "editType" : "add", "file" : "drivers/net/phy/ax88796b.c" }, { "editType" : "edit", "file" : "drivers/net/phy/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/ibm/ibmvnic.c" ], "commitId" : "78e1374d96c50d69f8e8acbd06a9067c2f21b2f8", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ibmvnic: Do not close unopened driver during reset\u000a\u000a[ Upstream commit 1f94608b0ce141be5286dde31270590bdf35b86a ]\u000a\u000aCheck driver state before halting it during a reset. If the driver is\u000anot running, do nothing. Otherwise, a request to deactivate a down link\u000acan cause an error and the reset will fail.\u000a\u000aSigned-off-by: Thomas Falcon \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "78e1374d96c50d69f8e8acbd06a9067c2f21b2f8", "msg" : "ibmvnic: Do not close unopened driver during reset", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/ibm/ibmvnic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/ibm/ibmvnic.c" ], "commitId" : "0c21c3ab0e54cf608b641290e69f943fd0f1423d", "timestamp" : 1563084579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ibmvnic: Refresh device multicast list after reset\u000a\u000a[ Upstream commit be32a24372cf162e825332da1a7ccef058d4f20b ]\u000a\u000aIt was observed that multicast packets were no longer received after\u000aa device reset. The fix is to resend the current multicast list to\u000athe backing device after recovery.\u000a\u000aSigned-off-by: Thomas Falcon \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:39 +0200", "id" : "0c21c3ab0e54cf608b641290e69f943fd0f1423d", "msg" : "ibmvnic: Refresh device multicast list after reset", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/ibm/ibmvnic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/ibm/ibmvnic.c" ], "commitId" : "cda7382c1136e76b6edd58f46d5a405bc052024e", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ibmvnic: Fix unchecked return codes of memory allocations\u000a\u000a[ Upstream commit 7c940b1a5291e5069d561f5b8f0e51db6b7a259a ]\u000a\u000aThe return values for these memory allocations are unchecked,\u000awhich may cause an oops if the driver does not handle them after\u000aa failure. Fix by checking the function's return code.\u000a\u000aSigned-off-by: Thomas Falcon \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "cda7382c1136e76b6edd58f46d5a405bc052024e", "msg" : "ibmvnic: Fix unchecked return codes of memory allocations", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/ibm/ibmvnic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/am335x-pcm-953.dtsi", "arch/arm/boot/dts/am335x-wega.dtsi" ], "commitId" : "3379bbd0fce938edcb8a35bfe2cb690b888119a8", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: am335x phytec boards: Fix cd-gpios active level\u000a\u000a[ Upstream commit 8a0098c05a272c9a68f6885e09755755b612459c ]\u000a\u000aActive level of the mmc1 cd gpio needs to be low instead of high.\u000aFix PCM-953 and phyBOARD-WEGA.\u000a\u000aSigned-off-by: Teresa Remmet \u000aSigned-off-by: Tony Lindgren \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "3379bbd0fce938edcb8a35bfe2cb690b888119a8", "msg" : "ARM: dts: am335x phytec boards: Fix cd-gpios active level", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/am335x-wega.dtsi" }, { "editType" : "edit", "file" : "arch/arm/boot/dts/am335x-pcm-953.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/s390/Makefile" ], "commitId" : "eee9998b27e1a634bf207097532d5b7059282200", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "s390/boot: disable address-of-packed-member warning\u000a\u000a[ Upstream commit f9364df30420987e77599c4789ec0065c609a507 ]\u000a\u000aGet rid of gcc9 warnings like this:\u000a\u000aarch/s390/boot/ipl_report.c: In function 'find_bootdata_space':\u000aarch/s390/boot/ipl_report.c:42:26: warning: taking address of packed member of 'struct ipl_rb_components' may result in an unaligned pointer value [-Waddress-of-packed-member]\u000a 42 | for_each_rb_entry(comp, comps)\u000a | ^~~~~\u000a\u000aThis is effectively the s390 variant of commit 20c6c1890455\u000a(\"x86/boot: Disable the address-of-packed-member compiler warning\").\u000a\u000aReviewed-by: Vasily Gorbik \u000aSigned-off-by: Heiko Carstens \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "eee9998b27e1a634bf207097532d5b7059282200", "msg" : "s390/boot: disable address-of-packed-member warning", "paths" : [ { "editType" : "edit", "file" : "arch/s390/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/riscv/configs/defconfig" ], "commitId" : "2f9f960af41c8a119a47a19f094d5063bb6e7667", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "RISC-V: defconfig: enable clocks, serial console\u000a\u000a[ Upstream commit 3b025f2bc98973f181d926192b0ceb6ced0f86d2 ]\u000a\u000aEnable PRCI clock driver and serial console by default, so the default\u000aupstream defconfig is bootable to a serial console.\u000a\u000aSigned-off-by: Kevin Hilman \u000aReviewed-by: Christoph Hellwig \u000aSigned-off-by: Paul Walmsley \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "2f9f960af41c8a119a47a19f094d5063bb6e7667", "msg" : "RISC-V: defconfig: enable clocks, serial console", "paths" : [ { "editType" : "edit", "file" : "arch/riscv/configs/defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c" ], "commitId" : "04c309800d00093f854ca49fa9af5d7bfbddc971", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/vmwgfx: Honor the sg list segment size limitation\u000a\u000a[ Upstream commit bde15555ba61c7f664f40fd3c6fdbdb63f784c9b ]\u000a\u000aWhen building sg tables, honor the device sg list segment size limitation.\u000a\u000aSigned-off-by: Thomas Hellstrom \u000aReviewed-by: Deepak Rawat \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "04c309800d00093f854ca49fa9af5d7bfbddc971", "msg" : "drm/vmwgfx: Honor the sg list segment size limitation", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/vmwgfx/vmwgfx_drv.c" ], "commitId" : "1ef49d30eb2d24b190fa575bf8e6f35ae622694f", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/vmwgfx: fix a warning due to missing dma_parms\u000a\u000a[ Upstream commit 39916897cd815a0ee07ba1f6820cf88a63e459fc ]\u000a\u000aBooting up with DMA_API_DEBUG_SG=y generates a warning due to the driver\u000aforgot to set dma_parms appropriately. Set it just after vmw_dma_masks()\u000ain vmw_driver_load().\u000a\u000aDMA-API: vmwgfx 0000:00:0f.0: mapping sg segment longer than device\u000aclaims to support [len=2097152] [max=65536]\u000aWARNING: CPU: 2 PID: 261 at kernel/dma/debug.c:1232\u000adebug_dma_map_sg+0x360/0x480\u000aHardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop\u000aReference Platform, BIOS 6.00 04/13/2018\u000aRIP: 0010:debug_dma_map_sg+0x360/0x480\u000aCall Trace:\u000a vmw_ttm_map_dma+0x3b1/0x5b0 [vmwgfx]\u000a vmw_bo_map_dma+0x25/0x30 [vmwgfx]\u000a vmw_otables_setup+0x2a8/0x750 [vmwgfx]\u000a vmw_request_device_late+0x78/0xc0 [vmwgfx]\u000a vmw_request_device+0xee/0x4e0 [vmwgfx]\u000a vmw_driver_load.cold+0x757/0xd84 [vmwgfx]\u000a drm_dev_register+0x1ff/0x340 [drm]\u000a drm_get_pci_dev+0x110/0x290 [drm]\u000a vmw_probe+0x15/0x20 [vmwgfx]\u000a local_pci_probe+0x7a/0xc0\u000a pci_device_probe+0x1b9/0x290\u000a really_probe+0x1b5/0x630\u000a driver_probe_device+0xa3/0x1a0\u000a device_driver_attach+0x94/0xa0\u000a __driver_attach+0xdd/0x1c0\u000a bus_for_each_dev+0xfe/0x150\u000a driver_attach+0x2d/0x40\u000a bus_add_driver+0x290/0x350\u000a driver_register+0xdc/0x1d0\u000a __pci_register_driver+0xda/0xf0\u000a vmwgfx_init+0x34/0x1000 [vmwgfx]\u000a do_one_initcall+0xe5/0x40a\u000a do_init_module+0x10f/0x3a0\u000a load_module+0x16a5/0x1a40\u000a __se_sys_finit_module+0x183/0x1c0\u000a __x64_sys_finit_module+0x43/0x50\u000a do_syscall_64+0xc8/0x606\u000a entry_SYSCALL_64_after_hwframe+0x44/0xa9\u000a\u000aFixes: fb1d9738ca05 (\"drm/vmwgfx: Add DRM driver for VMware Virtual GPU\")\u000aCo-developed-by: Thomas Hellstrom \u000aSigned-off-by: Qian Cai \u000aSigned-off-by: Thomas Hellstrom \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "1ef49d30eb2d24b190fa575bf8e6f35ae622694f", "msg" : "drm/vmwgfx: fix a warning due to missing dma_parms", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/vmwgfx/vmwgfx_drv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/riscv/lib/delay.c" ], "commitId" : "82045b8cbcc68e3f8d38e89a0ff48fc99178c2be", "timestamp" : 1563084580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "riscv: Fix udelay in RV32.\u000a\u000a[ Upstream commit d0e1f2110a5eeb6e410b2dd37d98bc5b30da7bc7 ]\u000a\u000aIn RV32, udelay would delay the wrong cycle. When it shifts right\u000a\"UDELAY_SHIFT\" bits, it either delays 0 cycle or 1 cycle. It only works\u000acorrectly in RV64. Because the 'ucycles' always needs to be 64 bits\u000avariable.\u000a\u000aSigned-off-by: Nick Hu \u000aReviewed-by: Palmer Dabbelt \u000a[paul.walmsley@sifive.com: fixed minor spelling error]\u000aSigned-off-by: Paul Walmsley \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:40 +0200", "id" : "82045b8cbcc68e3f8d38e89a0ff48fc99178c2be", "msg" : "riscv: Fix udelay in RV32.", "paths" : [ { "editType" : "edit", "file" : "arch/riscv/lib/delay.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/keyboard/imx_keypad.c" ], "commitId" : "5f546398d344593edfdf83301d7d7a5ddc55eab9", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: imx_keypad - make sure keyboard can always wake up system\u000a\u000a[ Upstream commit ce9a53eb3dbca89e7ad86673d94ab886e9bea704 ]\u000a\u000aThere are several scenarios that keyboard can NOT wake up system\u000afrom suspend, e.g., if a keyboard is depressed between system\u000adevice suspend phase and device noirq suspend phase, the keyboard\u000aISR will be called and both keyboard depress and release interrupts\u000awill be disabled, then keyboard will no longer be able to wake up\u000asystem. Another scenario would be, if a keyboard is kept depressed,\u000aand then system goes into suspend, the expected behavior would be\u000awhen keyboard is released, system will be waked up, but current\u000aimplementation can NOT achieve that, because both depress and release\u000ainterrupts are disabled in ISR, and the event check is still in\u000aprogress.\u000a\u000aTo fix these issues, need to make sure keyboard's depress or release\u000ainterrupt is enabled after noirq device suspend phase, this patch\u000amoves the suspend/resume callback to noirq suspend/resume phase, and\u000aenable the corresponding interrupt according to current keyboard status.\u000a\u000aSigned-off-by: Anson Huang \u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "5f546398d344593edfdf83301d7d7a5ddc55eab9", "msg" : "Input: imx_keypad - make sure keyboard can always wake up system", "paths" : [ { "editType" : "edit", "file" : "drivers/input/keyboard/imx_keypad.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/xdp/xdp_umem.c" ], "commitId" : "a5769fc5d1bb758a024d54c4147a4692fa4ba5ce", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xdp: check device pointer before clearing\u000a\u000a[ Upstream commit 01d76b5317003e019ace561a9b775f51aafdfdc4 ]\u000a\u000aWe should not call 'ndo_bpf()' or 'dev_put()' with NULL argument.\u000a\u000aFixes: c9b47cc1fabc (\"xsk: fix bug when trying to use both copy and zero-copy on one queue id\")\u000aSigned-off-by: Ilya Maximets \u000aAcked-by: Jonathan Lemon \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "a5769fc5d1bb758a024d54c4147a4692fa4ba5ce", "msg" : "xdp: check device pointer before clearing", "paths" : [ { "editType" : "edit", "file" : "net/xdp/xdp_umem.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "virt/kvm/arm/vgic/vgic-its.c" ], "commitId" : "7a3f322213f00930396a8f09261f1438d272e21c", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: arm/arm64: vgic: Fix kvm_device leak in vgic_its_destroy\u000a\u000a[ Upstream commit 4729ec8c1e1145234aeeebad5d96d77f4ccbb00a ]\u000a\u000akvm_device->destroy() seems to be supposed to free its kvm_device\u000astruct, but vgic_its_destroy() is not currently doing this,\u000aresulting in a memory leak, resulting in kmemleak reports such as\u000athe following:\u000a\u000aunreferenced object 0xffff800aeddfe280 (size 128):\u000a comm \"qemu-system-aar\", pid 13799, jiffies 4299827317 (age 1569.844s)\u000a [...]\u000a backtrace:\u000a [<00000000a08b80e2>] kmem_cache_alloc+0x178/0x208\u000a [<00000000dcad2bd3>] kvm_vm_ioctl+0x350/0xbc0\u000a\u000aFix it.\u000a\u000aCc: Andre Przywara \u000aFixes: 1085fdc68c60 (\"KVM: arm64: vgic-its: Introduce new KVM ITS device\")\u000aSigned-off-by: Dave Martin \u000aSigned-off-by: Marc Zyngier \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "7a3f322213f00930396a8f09261f1438d272e21c", "msg" : "KVM: arm/arm64: vgic: Fix kvm_device leak in vgic_its_destroy", "paths" : [ { "editType" : "edit", "file" : "virt/kvm/arm/vgic/vgic-its.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlxsw/reg.h" ], "commitId" : "5b8efec8a9f2c7de08e720dd3f6310af292d8e50", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mlxsw: spectrum: Disallow prio-tagged packets when PVID is removed\u000a\u000a[ Upstream commit 4b14cc313f076c37b646cee06a85f0db59cf216c ]\u000a\u000aWhen PVID is removed from a bridge port, the Linux bridge drops both\u000auntagged and prio-tagged packets. Align mlxsw with this behavior.\u000a\u000aFixes: 148f472da5db (\"mlxsw: reg: Add the Switch Port Acceptable Frame Types register\")\u000aAcked-by: Jiri Pirko \u000aSigned-off-by: Ido Schimmel \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "5b8efec8a9f2c7de08e720dd3f6310af292d8e50", "msg" : "mlxsw: spectrum: Disallow prio-tagged packets when PVID is removed", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlxsw/reg.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/nested.c" ], "commitId" : "e80b4f6271eca3f86ada3c21fdfedb02ec3643d8", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: nVMX: use correct clean fields when copying from eVMCS\u000a\u000a[ Upstream commit f9bc5227652df4900eff12a9b8b38e9a8c7c78ea ]\u000a\u000aUnfortunately, a couple of mistakes were made while implementing\u000aEnlightened VMCS support, in particular, wrong clean fields were\u000aused in copy_enlightened_to_vmcs12():\u000a- exception_bitmap is covered by CONTROL_EXCPN;\u000a- vm_exit_controls/pin_based_vm_exec_control/secondary_vm_exec_control\u000a are covered by CONTROL_GRP1.\u000a\u000aFixes: 945679e301ea0 (\"KVM: nVMX: add enlightened VMCS state\")\u000aSigned-off-by: Vitaly Kuznetsov \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "e80b4f6271eca3f86ada3c21fdfedb02ec3643d8", "msg" : "KVM: nVMX: use correct clean fields when copying from eVMCS", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/nested.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/testing/selftests/bpf/verifier/div_overflow.c" ], "commitId" : "5d5e2b12cdcd6ea9d3b2b2c50c829e5379bda5c7", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: fix div64 overflow tests to properly detect errors\u000a\u000a[ Upstream commit 3e0682695199bad51dd898fe064d1564637ff77a ]\u000a\u000aIf the result of the division is LLONG_MIN, current tests do not detect\u000athe error since the return value is truncated to a 32-bit value and ends\u000aup being 0.\u000a\u000aSigned-off-by: Naveen N. Rao \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "5d5e2b12cdcd6ea9d3b2b2c50c829e5379bda5c7", "msg" : "bpf: fix div64 overflow tests to properly detect errors", "paths" : [ { "editType" : "edit", "file" : "tools/testing/selftests/bpf/verifier/div_overflow.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/mach-davinci/board-da850-evm.c" ], "commitId" : "06004e683ee1138dcf5dae105326460e568a2da4", "timestamp" : 1563084581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: davinci: da850-evm: call regulator_has_full_constraints()\u000a\u000a[ Upstream commit 0c0c9b5753cd04601b17de09da1ed2885a3b42fe ]\u000a\u000aThe BB expander at 0x21 i2c bus 1 fails to probe on da850-evm because\u000athe board doesn't set has_full_constraints to true in the regulator\u000aAPI.\u000a\u000aCall regulator_has_full_constraints() at the end of board registration\u000ajust like we do in da850-lcdk and da830-evm.\u000a\u000aReviewed-by: Linus Walleij \u000aSigned-off-by: Bartosz Golaszewski \u000aSigned-off-by: Sekhar Nori \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:41 +0200", "id" : "06004e683ee1138dcf5dae105326460e568a2da4", "msg" : "ARM: davinci: da850-evm: call regulator_has_full_constraints()", "paths" : [ { "editType" : "edit", "file" : "arch/arm/mach-davinci/board-da850-evm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/mach-davinci/devices-da8xx.c" ], "commitId" : "658031eab6241a3c7ffc72066f65c19ad3f22b49", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: davinci: da8xx: specify dma_coherent_mask for lcdc\u000a\u000a[ Upstream commit 68f2515bb31a664ba3e2bc1eb78dd9f529b10067 ]\u000a\u000aThe lcdc device is missing the dma_coherent_mask definition causing the\u000afollowing warning on da850-evm:\u000a\u000ada8xx_lcdc da8xx_lcdc.0: found Sharp_LK043T1DG01 panel\u000a------------[ cut here ]------------\u000aWARNING: CPU: 0 PID: 1 at kernel/dma/mapping.c:247 dma_alloc_attrs+0xc8/0x110\u000aModules linked in:\u000aCPU: 0 PID: 1 Comm: swapper Not tainted 5.2.0-rc3-00077-g16d72dd4891f #18\u000aHardware name: DaVinci DA850/OMAP-L138/AM18x EVM\u000a[] (unwind_backtrace) from [] (show_stack+0x10/0x14)\u000a[] (show_stack) from [] (__warn+0xec/0x114)\u000a[] (__warn) from [] (warn_slowpath_null+0x3c/0x48)\u000a[] (warn_slowpath_null) from [] (dma_alloc_attrs+0xc8/0x110)\u000a[] (dma_alloc_attrs) from [] (fb_probe+0x228/0x5a8)\u000a[] (fb_probe) from [] (platform_drv_probe+0x48/0x9c)\u000a[] (platform_drv_probe) from [] (really_probe+0x1d8/0x2d4)\u000a[] (really_probe) from [] (driver_probe_device+0x5c/0x168)\u000a[] (driver_probe_device) from [] (device_driver_attach+0x58/0x60)\u000a[] (device_driver_attach) from [] (__driver_attach+0x80/0xbc)\u000a[] (__driver_attach) from [] (bus_for_each_dev+0x64/0xb4)\u000a[] (bus_for_each_dev) from [] (bus_add_driver+0xe4/0x1d8)\u000a[] (bus_add_driver) from [] (driver_register+0x78/0x10c)\u000a[] (driver_register) from [] (do_one_initcall+0x48/0x1bc)\u000a[] (do_one_initcall) from [] (kernel_init_freeable+0x10c/0x1d8)\u000a[] (kernel_init_freeable) from [] (kernel_init+0x8/0xf4)\u000a[] (kernel_init) from [] (ret_from_fork+0x14/0x34)\u000aException stack(0xc6837fb0 to 0xc6837ff8)\u000a7fa0: 00000000 00000000 00000000 00000000\u000a7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000\u000a7fe0: 00000000 00000000 00000000 00000000 00000013 00000000\u000a---[ end trace 8a8073511be81dd2 ]---\u000a\u000aAdd a 32-bit mask to the platform device's definition.\u000a\u000aSigned-off-by: Bartosz Golaszewski \u000a\u000aSigned-off-by: Sekhar Nori \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "658031eab6241a3c7ffc72066f65c19ad3f22b49", "msg" : "ARM: davinci: da8xx: specify dma_coherent_mask for lcdc", "paths" : [ { "editType" : "edit", "file" : "arch/arm/mach-davinci/devices-da8xx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/ipu-v3/ipu-image-convert.c" ], "commitId" : "955be60e0c2f3f4aae7b6e8819a5a8b234fbfa00", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpu: ipu-v3: image-convert: Fix input bytesperline width/height align\u000a\u000a[ Upstream commit ff391ecd65a1b8324c49046c3db98d9c8ab29af9 ]\u000a\u000aThe output width and height alignment values were being used in the\u000ainput bytesperline calculation. Fix by separating local vars w_align\u000aand h_align into w_align_in, h_align_in, w_align_out, and h_align_out.\u000a\u000aFixes: d966e23d61a2c (\"gpu: ipu-v3: image-convert: fix bytesperline\u000aadjustment\")\u000a\u000aSigned-off-by: Steve Longerbeam \u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "955be60e0c2f3f4aae7b6e8819a5a8b234fbfa00", "msg" : "gpu: ipu-v3: image-convert: Fix input bytesperline width/height align", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/ipu-v3/ipu-image-convert.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/ipu-v3/ipu-image-convert.c" ], "commitId" : "858251f8dd6eb387470256a1d2ea7f78f82d2a9f", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpu: ipu-v3: image-convert: Fix input bytesperline for packed formats\u000a\u000a[ Upstream commit bca4d70cf1b8f6478a711c448a3a1e47b794b162 ]\u000a\u000aThe input bytesperline calculation for packed pixel formats was\u000aincorrect. The min/max clamping values must be multiplied by the\u000apacked bits-per-pixel. This was causing corrupted converted images\u000awhen the input format was RGB4 (probably also other input packed\u000aformats).\u000a\u000aFixes: d966e23d61a2c (\"gpu: ipu-v3: image-convert: fix bytesperline\u000aadjustment\")\u000a\u000aReported-by: Harsha Manjula Mallikarjun \u000aSuggested-by: Harsha Manjula Mallikarjun \u000aSigned-off-by: Steve Longerbeam \u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "858251f8dd6eb387470256a1d2ea7f78f82d2a9f", "msg" : "gpu: ipu-v3: image-convert: Fix input bytesperline for packed formats", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/ipu-v3/ipu-image-convert.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/ipu-v3/ipu-image-convert.c" ], "commitId" : "b7ed6a9b4c56fa602ba941ca188aa7274105147e", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpu: ipu-v3: image-convert: Fix image downsize coefficients\u000a\u000a[ Upstream commit 912bbf7e9ca422099935dd69d3ff0fd62db24882 ]\u000a\u000aThe output of the IC downsizer unit in both dimensions must be <= 1024\u000abefore being passed to the IC resizer unit. This was causing corrupted\u000aimages when:\u000a\u000ainput_dim > 1024, and\u000ainput_dim / 2 < output_dim < input_dim\u000a\u000aSome broken examples were 1920x1080 -> 1024x768 and 1920x1080 ->\u000a1280x1080.\u000a\u000aFixes: 70b9b6b3bcb21 (\"gpu: ipu-v3: image-convert: calculate per-tile\u000aresize coefficients\")\u000a\u000aSigned-off-by: Steve Longerbeam \u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "b7ed6a9b4c56fa602ba941ca188aa7274105147e", "msg" : "gpu: ipu-v3: image-convert: Fix image downsize coefficients", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/ipu-v3/ipu-image-convert.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/mac80211/ieee80211_i.h" ], "commitId" : "b88d16425319b2f2d51b12bd5cca739b5ac3a37d", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mac80211: only warn once on chanctx_conf being NULL\u000a\u000a[ Upstream commit 563572340173865a9a356e6bb02579e6998a876d ]\u000a\u000aIn multiple SSID cases, it takes time to prepare every AP interface\u000ato be ready in initializing phase. If a sta already knows everything it\u000aneeds to join one of the APs and sends authentication to the AP which\u000ais not fully prepared at this point of time, AP's channel context\u000acould be NULL. As a result, warning message occurs.\u000a\u000aEven worse, if the AP is under attack via tools such as MDK3 and massive\u000aauthentication requests are received in a very short time, console will\u000abe hung due to kernel warning messages.\u000a\u000aWARN_ON_ONCE() could be a better way for indicating warning messages\u000awithout duplicate messages to flood the console.\u000a\u000aJohannes: We still need to address the underlying problem, but we\u000a don't really have a good handle on it yet. Suppress the\u000a worst side-effects for now.\u000a\u000aSigned-off-by: Zhi Chen \u000aSigned-off-by: Yibo Zhao \u000a[johannes: add note, change subject]\u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "b88d16425319b2f2d51b12bd5cca739b5ac3a37d", "msg" : "mac80211: only warn once on chanctx_conf being NULL", "paths" : [ { "editType" : "edit", "file" : "net/mac80211/ieee80211_i.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/mac80211/ieee80211_i.h", "net/mac80211/util.c" ], "commitId" : "d2aab1140bd37e5bbfbc03152243701ff832d2ba", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mac80211: do not start any work during reconfigure flow\u000a\u000a[ Upstream commit f8891461a277ec0afc493fd30cd975a38048a038 ]\u000a\u000aIt is not a good idea to try to perform any work (e.g. send an auth\u000aframe) during reconfigure flow.\u000a\u000aPrevent this from happening, and at the end of the reconfigure flow\u000arequeue all the works.\u000a\u000aSigned-off-by: Naftali Goldstein \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "d2aab1140bd37e5bbfbc03152243701ff832d2ba", "msg" : "mac80211: do not start any work during reconfigure flow", "paths" : [ { "editType" : "edit", "file" : "net/mac80211/ieee80211_i.h" }, { "editType" : "edit", "file" : "net/mac80211/util.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/wireless/util.c" ], "commitId" : "afe6a610dd5d82e93add11aaee1fb071d5b57a78", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cfg80211: util: fix bit count off by one\u000a\u000a[ Upstream commit 1a473d6092d5d182914bea854ce0b21e6d12519d ]\u000a\u000aThe bits of Rx MCS Map in VHT capability were enumerated\u000awith index transform - index i -> (i + 1) bit => nss i. BUG!\u000awhile it should be - index i -> (i + 1) bit => (i + 1) nss.\u000a\u000aThe bug was exposed in commit a53b2a0b1245 (\"iwlwifi: mvm: implement VHT\u000aextended NSS support in rs.c\"), where iwlwifi started using the\u000afunction.\u000a\u000aSigned-off-by: Mordechay Goodstein \u000aFixes: b0aa75f0b1b2 (\"ieee80211: add new VHT capability fields/parsing\")\u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "afe6a610dd5d82e93add11aaee1fb071d5b57a78", "msg" : "cfg80211: util: fix bit count off by one", "paths" : [ { "editType" : "edit", "file" : "net/wireless/util.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/wireless/pmsr.c" ], "commitId" : "6d0b6b471e5c3379ea964a893d934a7bd17a697a", "timestamp" : 1563084582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cfg80211: report measurement start TSF correctly\u000a\u000a[ Upstream commit b65842025335711e2a0259feb4dbadb0c9ffb6d9 ]\u000a\u000aInstead of reporting the AP's TSF, host time was reported. Fix it.\u000a\u000aSigned-off-by: Avraham Stern \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:42 +0200", "id" : "6d0b6b471e5c3379ea964a893d934a7bd17a697a", "msg" : "cfg80211: report measurement start TSF correctly", "paths" : [ { "editType" : "edit", "file" : "net/wireless/pmsr.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/bpf/devmap.c" ], "commitId" : "92e9431c8beffad497ee8601f9befd7caa56620f", "timestamp" : 1563084583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, devmap: Fix premature entry free on destroying map\u000a\u000a[ Upstream commit d4dd153d551634683fccf8881f606fa9f3dfa1ef ]\u000a\u000adev_map_free() waits for flush_needed bitmap to be empty in order to\u000aensure all flush operations have completed before freeing its entries.\u000aHowever the corresponding clear_bit() was called before using the\u000aentries, so the entries could be used after free.\u000a\u000aAll access to the entries needs to be done before clearing the bit.\u000aIt seems commit a5e2da6e9787 (\"bpf: netdev is never null in\u000a__dev_map_flush\") accidentally changed the clear_bit() and memory access\u000aorder.\u000a\u000aNote that the problem happens only in __dev_map_flush(), not in\u000adev_map_flush_old(). dev_map_flush_old() is called only after nulling\u000aout the corresponding netdev_map entry, so dev_map_free() never frees\u000athe entry thus no such race happens there.\u000a\u000aFixes: a5e2da6e9787 (\"bpf: netdev is never null in __dev_map_flush\")\u000aSigned-off-by: Toshiaki Makita \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:43 +0200", "id" : "92e9431c8beffad497ee8601f9befd7caa56620f", "msg" : "bpf, devmap: Fix premature entry free on destroying map", "paths" : [ { "editType" : "edit", "file" : "kernel/bpf/devmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/bpf/devmap.c" ], "commitId" : "ee2ec83afa8b3c0cfe6e8589cfed08f57d468b11", "timestamp" : 1563084583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, devmap: Add missing bulk queue free\u000a\u000a[ Upstream commit edabf4d9dd905acd60048ea1579943801e3a4876 ]\u000a\u000adev_map_free() forgot to free bulk queue when freeing its entries.\u000a\u000aFixes: 5d053f9da431 (\"bpf: devmap prepare xdp frames for bulking\")\u000aSigned-off-by: Toshiaki Makita \u000aAcked-by: Jesper Dangaard Brouer \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:43 +0200", "id" : "ee2ec83afa8b3c0cfe6e8589cfed08f57d468b11", "msg" : "bpf, devmap: Add missing bulk queue free", "paths" : [ { "editType" : "edit", "file" : "kernel/bpf/devmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/bpf/devmap.c" ], "commitId" : "172a3024ef7eee59b295a14dca67406a79645cb9", "timestamp" : 1563084583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, devmap: Add missing RCU read lock on flush\u000a\u000a[ Upstream commit 86723c8640633bee4b4588d3c7784ee7a0032f65 ]\u000a\u000a.ndo_xdp_xmit() assumes it is called under RCU. For example virtio_net\u000auses RCU to detect it has setup the resources for tx. The assumption\u000aaccidentally broke when introducing bulk queue in devmap.\u000a\u000aFixes: 5d053f9da431 (\"bpf: devmap prepare xdp frames for bulking\")\u000aReported-by: David Ahern \u000aSigned-off-by: Toshiaki Makita \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:43 +0200", "id" : "172a3024ef7eee59b295a14dca67406a79645cb9", "msg" : "bpf, devmap: Add missing RCU read lock on flush", "paths" : [ { "editType" : "edit", "file" : "kernel/bpf/devmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/net/bpf_jit_comp.c" ], "commitId" : "86e69af63f6ebcd50959ef6d5a9be947102d3bb0", "timestamp" : 1563084583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, x64: fix stack layout of JITed bpf code\u000a\u000a[ Upstream commit fe8d9571dc50232b569242fac7ea6332a654f186 ]\u000a\u000aSince commit 177366bf7ceb the %rbp stopped pointing to %rbp of the\u000aprevious stack frame. That broke frame pointer based stack unwinding.\u000aThis commit is a partial revert of it.\u000aNote that the location of tail_call_cnt is fixed, since the verifier\u000aenforces MAX_BPF_STACK stack size for programs with tail calls.\u000a\u000aFixes: 177366bf7ceb (\"bpf: change x86 JITed program stack layout\")\u000aSigned-off-by: Alexei Starovoitov \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:43 +0200", "id" : "86e69af63f6ebcd50959ef6d5a9be947102d3bb0", "msg" : "bpf, x64: fix stack layout of JITed bpf code", "paths" : [ { "editType" : "edit", "file" : "arch/x86/net/bpf_jit_comp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/usb/qmi_wwan.c" ], "commitId" : "4bd6849a7cd76bfd1f59cece6b798232c31f41eb", "timestamp" : 1563084583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "qmi_wwan: add support for QMAP padding in the RX path\u000a\u000a[ Upstream commit 61356088ace1866a847a727d4d40da7bf00b67fc ]\u000a\u000aThe QMAP code in the qmi_wwan driver is based on the CodeAurora GobiNet\u000adriver which does not process QMAP padding in the RX path correctly.\u000aAdd support for QMAP padding to qmimux_rx_fixup() according to the\u000adescription of the rmnet driver.\u000a\u000aFixes: c6adf77953bc (\"net: usb: qmi_wwan: add qmap mux protocol support\")\u000aCc: Daniele Palmas \u000aSigned-off-by: Reinhard Speyerer \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:43 +0200", "id" : "4bd6849a7cd76bfd1f59cece6b798232c31f41eb", "msg" : "qmi_wwan: add support for QMAP padding in the RX path", "paths" : [ { "editType" : "edit", "file" : "drivers/net/usb/qmi_wwan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/usb/qmi_wwan.c" ], "commitId" : "382719d4a0c815d2313a3d707088f6f02e3e161b", "timestamp" : 1563084583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "qmi_wwan: avoid RCU stalls on device disconnect when in QMAP mode\u000a\u000a[ Upstream commit a8fdde1cb830e560208af42b6c10750137f53eb3 ]\u000a\u000aSwitch qmimux_unregister_device() and qmi_wwan_disconnect() to\u000ause unregister_netdevice_queue() and unregister_netdevice_many()\u000ainstead of unregister_netdevice(). This avoids RCU stalls which\u000ahave been observed on device disconnect in certain setups otherwise.\u000a\u000aFixes: c6adf77953bc (\"net: usb: qmi_wwan: add qmap mux protocol support\")\u000aCc: Daniele Palmas \u000aSigned-off-by: Reinhard Speyerer \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:43 +0200", "id" : "382719d4a0c815d2313a3d707088f6f02e3e161b", "msg" : "qmi_wwan: avoid RCU stalls on device disconnect when in QMAP mode", "paths" : [ { "editType" : "edit", "file" : "drivers/net/usb/qmi_wwan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/ABI/testing/sysfs-class-net-qmi", "drivers/net/usb/qmi_wwan.c" ], "commitId" : "4e1b6174a87806df5fddc54305ed55d15e72b137", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "qmi_wwan: extend permitted QMAP mux_id value range\u000a\u000a[ Upstream commit 36815b416fa48766ac5a98e4b2dc3ebc5887222e ]\u000a\u000aPermit mux_id values up to 254 to be used in qmimux_register_device()\u000afor compatibility with ip(8) and the rmnet driver.\u000a\u000aFixes: c6adf77953bc (\"net: usb: qmi_wwan: add qmap mux protocol support\")\u000aCc: Daniele Palmas \u000aSigned-off-by: Reinhard Speyerer \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "4e1b6174a87806df5fddc54305ed55d15e72b137", "msg" : "qmi_wwan: extend permitted QMAP mux_id value range", "paths" : [ { "editType" : "edit", "file" : "Documentation/ABI/testing/sysfs-class-net-qmi" }, { "editType" : "edit", "file" : "drivers/net/usb/qmi_wwan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/mmc/core/mmc.c" ], "commitId" : "511b73e67016bbdb8ab6d879f2ddf62655a3d74e", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mmc: core: complete HS400 before checking status\u000a\u000a[ Upstream commit b0e370b95a3b231d0fb5d1958cce85ef57196fe6 ]\u000a\u000aWe don't have a reproducible error case, yet our BSP team suggested that\u000athe mmc_switch_status() command in mmc_select_hs400() should come after\u000athe callback into the driver completing HS400 setup. It makes sense to\u000ame because we want the status of a fully setup HS400, so it will\u000aincrease the reliability of the mmc_switch_status() command.\u000a\u000aReported-by: Yoshihiro Shimoda \u000aSigned-off-by: Wolfram Sang \u000aFixes: ba6c7ac3a2f4 (\"mmc: core: more fine-grained hooks for HS400 tuning\")\u000aSigned-off-by: Ulf Hansson \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "511b73e67016bbdb8ab6d879f2ddf62655a3d74e", "msg" : "mmc: core: complete HS400 before checking status", "paths" : [ { "editType" : "edit", "file" : "drivers/mmc/core/mmc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/hw/hfi1/rc.c", "drivers/infiniband/hw/hfi1/hfi.h" ], "commitId" : "339d51e3723bb049728d4d9d7c61dd836e7a3263", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "IB/hfi1: Create inline to get extended headers\u000a\u000a[ Upstream commit 9755f72496664eec70bc804104118b5797b6bf63 ]\u000a\u000aThis paves the way for another patch that reacts to a\u000aflush sdma completion for RC.\u000a\u000aFixes: 81cd3891f021 (\"IB/hfi1: Add support for 16B Management Packets\")\u000aReviewed-by: Dennis Dalessandro \u000aSigned-off-by: Mike Marciniszyn \u000aSigned-off-by: Dennis Dalessandro \u000aSigned-off-by: Doug Ledford \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "339d51e3723bb049728d4d9d7c61dd836e7a3263", "msg" : "IB/hfi1: Create inline to get extended headers", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/hfi.h" }, { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/rc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/hw/hfi1/rc.c", "drivers/infiniband/hw/hfi1/verbs.c", "drivers/infiniband/hw/hfi1/verbs.h" ], "commitId" : "01514e2d6ea9c79f40697b570a0a4648a2d008eb", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "IB/hfi1: Use aborts to trigger RC throttling\u000a\u000a[ Upstream commit 4bb02e9572af1383038d83ad196d7166c515f2ee ]\u000a\u000aSDMA and pio flushes will cause a lot of packets to be transmitted\u000aafter a link has gone down, using a lot of CPU to retransmit\u000apackets.\u000a\u000aFix for RC QPs by recognizing the flush status and:\u000a- Forcing a timer start\u000a- Putting the QP into a \"send one\" mode\u000a\u000aFixes: 7724105686e7 (\"IB/hfi1: add driver files\")\u000aReviewed-by: Kaike Wan \u000aSigned-off-by: Mike Marciniszyn \u000aSigned-off-by: Dennis Dalessandro \u000aSigned-off-by: Doug Ledford \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "01514e2d6ea9c79f40697b570a0a4648a2d008eb", "msg" : "IB/hfi1: Use aborts to trigger RC throttling", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/rc.c" }, { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/verbs.h" }, { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/verbs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/hw/hfi1/sdma.c" ], "commitId" : "c7a79b35dd816c47745c021953cdc92c78c1d6b8", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "IB/hfi1: Wakeup QPs orphaned on wait list after flush\u000a\u000a[ Upstream commit f972775b1cc0441ae22c9f8d06dd16b118463632 ]\u000a\u000aOnce an SDMA engine is taken down due to a link failure, any waiting QPs\u000athat do not have outstanding descriptors in the ring will stay\u000aon the dmawait list as long as the port is down.\u000a\u000aSince there is no timer running, they will stay there for a long time.\u000a\u000aThe fix is to wake up all iowaits linked to dmawait. The send engine\u000awill build and post packets that get flushed back.\u000a\u000aFixes: 7724105686e7 (\"IB/hfi1: add driver files\")\u000aReviewed-by: Kaike Wan \u000aSigned-off-by: Mike Marciniszyn \u000aSigned-off-by: Dennis Dalessandro \u000aSigned-off-by: Doug Ledford \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "c7a79b35dd816c47745c021953cdc92c78c1d6b8", "msg" : "IB/hfi1: Wakeup QPs orphaned on wait list after flush", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/sdma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/hw/hfi1/pio.c" ], "commitId" : "d19a1a9c4083e2b9015e7a1a151e9661ba5c47d5", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "IB/hfi1: Handle wakeup of orphaned QPs for pio\u000a\u000a[ Upstream commit 099a884ba4c00145cef283d36e050726311c2e95 ]\u000a\u000aOnce a send context is taken down due to a link failure, any QPs waiting\u000afor pio credits will stay on the waitlist indefinitely.\u000a\u000aFix by wakeing up all QPs linked to piowait list.\u000a\u000aFixes: 7724105686e7 (\"IB/hfi1: add driver files\")\u000aReviewed-by: Dennis Dalessandro \u000aSigned-off-by: Mike Marciniszyn \u000aSigned-off-by: Dennis Dalessandro \u000aSigned-off-by: Doug Ledford \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "d19a1a9c4083e2b9015e7a1a151e9661ba5c47d5", "msg" : "IB/hfi1: Handle wakeup of orphaned QPs for pio", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/pio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/hw/hfi1/rc.c", "drivers/infiniband/hw/hfi1/pio.c", "drivers/infiniband/hw/hfi1/verbs.c", "drivers/infiniband/hw/hfi1/ud.c" ], "commitId" : "e62ebc063f5ee8cfed2a799c43db954a9964677d", "timestamp" : 1563084584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "IB/hfi1: Handle port down properly in pio\u000a\u000a[ Upstream commit 942a899335707fc9cfc97cb382a60734b2ff4e03 ]\u000a\u000aThe call to sc_buffer_alloc currently returns NULL (no buffer) or\u000aa buffer descriptor.\u000a\u000aThere is a third case when the port is down. Currently that\u000areturns NULL and this prevents the caller from properly handling the\u000asc_buffer_alloc() failure. A verbs code link test after the call is\u000aracy so the indication needs to come from the state check inside the allocation\u000aroutine to be valid.\u000a\u000aFix by encoding the ECOMM failure like SDMA. IS_ERR_OR_NULL() tests\u000aare added at all call sites. For verbs send, this needs to treat any\u000aerror by returning a completion without any MMIO copy.\u000a\u000aFixes: 7724105686e7 (\"IB/hfi1: add driver files\")\u000aReviewed-by: Dennis Dalessandro \u000aSigned-off-by: Mike Marciniszyn \u000aSigned-off-by: Dennis Dalessandro \u000aSigned-off-by: Doug Ledford \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:44 +0200", "id" : "e62ebc063f5ee8cfed2a799c43db954a9964677d", "msg" : "IB/hfi1: Handle port down properly in pio", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/rc.c" }, { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/verbs.c" }, { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/pio.c" }, { "editType" : "edit", "file" : "drivers/infiniband/hw/hfi1/ud.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/md.c" ], "commitId" : "32cb50319091a5033c5021c297df62d786315857", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "md: fix for divide error in status_resync\u000a\u000a[ Upstream commit 9642fa73d073527b0cbc337cc17a47d545d82cd2 ]\u000a\u000aStopping external metadata arrays during resync/recovery causes\u000aretries, loop of interrupting and starting reconstruction, until it\u000ahit at good moment to stop completely. While these retries\u000acurr_mark_cnt can be small- especially on HDD drives, so subtraction\u000aresult can be smaller than 0. However it is casted to uint without\u000achecking. As a result of it the status bar in /proc/mdstat while stopping\u000ais strange (it jumps between 0% and 99%).\u000a\u000aThe real problem occurs here after commit 72deb455b5ec (\"block: remove\u000aCONFIG_LBDAF\"). Sector_div() macro has been changed, now the\u000adivisor is casted to uint32. For db = -8 the divisior(db/32-1) becomes 0.\u000a\u000aCheck if db value can be really counted and replace these macro by\u000adiv64_u64() inline.\u000a\u000aSigned-off-by: Mariusz Tkaczyk \u000aSigned-off-by: Song Liu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "32cb50319091a5033c5021c297df62d786315857", "msg" : "md: fix for divide error in status_resync", "paths" : [ { "editType" : "edit", "file" : "drivers/md/md.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/broadcom/bnx2x/bnx2x_ethtool.c", "drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.h" ], "commitId" : "d929834822c78b3a88105ec52a796f08f3a8976e", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bnx2x: Check if transceiver implements DDM before access\u000a\u000a[ Upstream commit cf18cecca911c0db96b868072665347efe6df46f ]\u000a\u000aSome transceivers may comply with SFF-8472 even though they do not\u000aimplement the Digital Diagnostic Monitoring (DDM) interface described in\u000athe spec. The existence of such area is specified by the 6th bit of byte\u000a92, set to 1 if implemented.\u000a\u000aCurrently, without checking this bit, bnx2x fails trying to read sfp\u000amodule's EEPROM with the follow message:\u000a\u000aethtool -m enP5p1s0f1\u000aCannot get Module EEPROM data: Input/output error\u000a\u000aBecause it fails to read the additional 256 bytes in which it is assumed\u000ato exist the DDM data.\u000a\u000aThis issue was noticed using a Mellanox Passive DAC PN 01FT738. The EEPROM\u000adata was confirmed by Mellanox as correct and similar to other Passive\u000aDACs from other manufacturers.\u000a\u000aSigned-off-by: Mauro S. M. Rodrigues \u000aAcked-by: Sudarsana Reddy Kalluru \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "d929834822c78b3a88105ec52a796f08f3a8976e", "msg" : "bnx2x: Check if transceiver implements DDM before access", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_ethtool.c" }, { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/drm_ioc32.c", "drivers/gpu/drm/drm_bufs.c" ], "commitId" : "b4ef52d26aec77217f27d7a399816b2a135b63f6", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm: return -EFAULT if copy_to_user() fails\u000a\u000a[ Upstream commit 74b67efa8d7b4f90137f0ab9a80dd319da050350 ]\u000a\u000aThe copy_from_user() function returns the number of bytes remaining\u000ato be copied but we want to return a negative error code. Otherwise\u000athe callers treat it as a successful copy.\u000a\u000aSigned-off-by: Dan Carpenter \u000aSigned-off-by: Sean Paul \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20190618131843.GA29463@mwanda\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "b4ef52d26aec77217f27d7a399816b2a135b63f6", "msg" : "drm: return -EFAULT if copy_to_user() fails", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/drm_ioc32.c" }, { "editType" : "edit", "file" : "drivers/gpu/drm/drm_bufs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/net/ip6_tunnel.h" ], "commitId" : "9465dc24d1c5205ae980988e44afd1d4736aaeba", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ip6_tunnel: allow not to count pkts on tstats by passing dev as NULL\u000a\u000a[ Upstream commit 6f6a8622057c92408930c31698394fae1557b188 ]\u000a\u000aA similar fix to Patch \"ip_tunnel: allow not to count pkts on tstats by\u000asetting skb's dev to NULL\" is also needed by ip6_tunnel.\u000a\u000aSigned-off-by: Xin Long \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "9465dc24d1c5205ae980988e44afd1d4736aaeba", "msg" : "ip6_tunnel: allow not to count pkts on tstats by passing dev as NULL", "paths" : [ { "editType" : "edit", "file" : "include/net/ip6_tunnel.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/cavium/liquidio/lio_core.c" ], "commitId" : "40386f7d5f4328cc5bde597e857e265661ae23d6", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: lio_core: fix potential sign-extension overflow on large shift\u000a\u000a[ Upstream commit 9476274093a0e79b905f4cd6cf6d149f65e02c17 ]\u000a\u000aLeft shifting the signed int value 1 by 31 bits has undefined behaviour\u000aand the shift amount oq_no can be as much as 63. Fix this by using\u000aBIT_ULL(oq_no) instead.\u000a\u000aAddresses-Coverity: (\"Bad shift operation\")\u000aFixes: f21fb3ed364b (\"Add support of Cavium Liquidio ethernet adapters\")\u000aSigned-off-by: Colin Ian King \u000aReviewed-by: Dan Carpenter \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "40386f7d5f4328cc5bde597e857e265661ae23d6", "msg" : "net: lio_core: fix potential sign-extension overflow on large shift", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/cavium/liquidio/lio_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/qedi/qedi_main.c" ], "commitId" : "b936c0e244e840fa42fadabe18cfe212b9c72d95", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: qedi: Check targetname while finding boot target information\u000a\u000a[ Upstream commit 1ac3549ed58cdfdaf43bbf31ac260e2381cc0dae ]\u000a\u000aThe kernel panic was observed during iSCSI discovery via offload with below\u000acall trace,\u000a\u000a[ 2115.646901] BUG: unable to handle kernel NULL pointer dereference at (null)\u000a[ 2115.646909] IP: [] strncmp+0xc/0x60\u000a[ 2115.646927] PGD 0\u000a[ 2115.646932] Oops: 0000 [#1] SMP\u000a[ 2115.647107] CPU: 24 PID: 264 Comm: kworker/24:1 Kdump: loaded Tainted: G\u000a OE ------------ 3.10.0-957.el7.x86_64 #1\u000a[ 2115.647133] Workqueue: slowpath-13:00. qed_slowpath_task [qed]\u000a[ 2115.647135] task: ffff8d66af80b0c0 ti: ffff8d66afb80000 task.ti: ffff8d66afb80000\u000a[ 2115.647136] RIP: 0010:[] [] strncmp+0xc/0x60\u000a[ 2115.647141] RSP: 0018:ffff8d66afb83c68 EFLAGS: 00010206\u000a[ 2115.647143] RAX: 0000000000000001 RBX: 0000000000000007 RCX: 000000000000000a\u000a[ 2115.647144] RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffff8d632b3ba040\u000a[ 2115.647145] RBP: ffff8d66afb83c68 R08: 0000000000000000 R09: 000000000000ffff\u000a[ 2115.647147] R10: 0000000000000007 R11: 0000000000000800 R12: ffff8d66a30007a0\u000a[ 2115.647148] R13: ffff8d66747a3c10 R14: ffff8d632b3ba000 R15: ffff8d66747a32f8\u000a[ 2115.647149] FS: 0000000000000000(0000) GS:ffff8d66aff00000(0000) knlGS:0000000000000000\u000a[ 2115.647151] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 2115.647152] CR2: 0000000000000000 CR3: 0000000509610000 CR4: 00000000007607e0\u000a[ 2115.647153] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\u000a[ 2115.647154] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\u000a[ 2115.647155] PKRU: 00000000\u000a[ 2115.647157] Call Trace:\u000a[ 2115.647165] [] qedi_get_protocol_tlv_data+0x2c5/0x510 [qedi]\u000a[ 2115.647184] [] ? qed_mfw_process_tlv_req+0x245/0xbe0 [qed]\u000a[ 2115.647195] [] qed_mfw_fill_tlv_data+0x4b/0xb0 [qed]\u000a[ 2115.647206] [] qed_mfw_process_tlv_req+0x261/0xbe0 [qed]\u000a[ 2115.647215] [] ? dequeue_task_fair+0x41e/0x660\u000a[ 2115.647221] [] ? __switch_to+0xce/0x580\u000a[ 2115.647230] [] qed_slowpath_task+0xa3/0x160 [qed]\u000a[ 2115.647278] RIP [] strncmp+0xc/0x60\u000a\u000aFix kernel panic by validating the session targetname before providing TLV\u000adata and confirming the presence of boot targets.\u000a\u000aSigned-off-by: Nilesh Javali \u000aReviewed-by: Lee Duncan \u000aReviewed-by: Chris Leech \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "b936c0e244e840fa42fadabe18cfe212b9c72d95", "msg" : "scsi: qedi: Check targetname while finding boot target information", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/qedi/qedi_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/mm/mem.c", "arch/powerpc/include/asm/page.h", "arch/powerpc/platforms/powermac/Kconfig" ], "commitId" : "bfd2bc5cc2d07cafe683cbb074a94bf9b4275c4f", "timestamp" : 1563084585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc: enable a 30-bit ZONE_DMA for 32-bit pmac\u000a\u000a[ Upstream commit 9739ab7eda459f0669ec9807e0d9be5020bab88c ]\u000a\u000aWith the strict dma mask checking introduced with the switch to\u000athe generic DMA direct code common wifi chips on 32-bit powerbooks\u000astopped working. Add a 30-bit ZONE_DMA to the 32-bit pmac builds\u000ato allow them to reliably allocate dma coherent memory.\u000a\u000aFixes: 65a21b71f948 (\"powerpc/dma: remove dma_nommu_dma_supported\")\u000aReported-by: Aaro Koskinen \u000aSigned-off-by: Christoph Hellwig \u000aTested-by: Larry Finger \u000aAcked-by: Larry Finger \u000aTested-by: Aaro Koskinen \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:45 +0200", "id" : "bfd2bc5cc2d07cafe683cbb074a94bf9b4275c4f", "msg" : "powerpc: enable a 30-bit ZONE_DMA for 32-bit pmac", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/include/asm/page.h" }, { "editType" : "edit", "file" : "arch/powerpc/platforms/powermac/Kconfig" }, { "editType" : "edit", "file" : "arch/powerpc/mm/mem.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/quota/dquot.c" ], "commitId" : "e0e24af6f44aff4e07417364b0969f36bd2485fe", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "quota: fix a problem about transfer quota\u000a\u000a[ Upstream commit c6d9c35d16f1bafd3fec64b865e569e48cbcb514 ]\u000a\u000aRun below script as root, dquot_add_space will return -EDQUOT since\u000a__dquot_transfer call dquot_add_space with flags=0, and dquot_add_space\u000athink it's a preallocation. Fix it by set flags as DQUOT_SPACE_WARN.\u000a\u000amkfs.ext4 -O quota,project /dev/vdb\u000amount -o prjquota /dev/vdb /mnt\u000asetquota -P 23 1 1 0 0 /dev/vdb\u000add if=/dev/zero of=/mnt/test-file bs=4K count=1\u000achattr -p 23 test-file\u000a\u000aFixes: 7b9ca4c61bc2 (\"quota: Reduce contention on dq_data_lock\")\u000aSigned-off-by: yangerkun \u000aSigned-off-by: Jan Kara \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "e0e24af6f44aff4e07417364b0969f36bd2485fe", "msg" : "quota: fix a problem about transfer quota", "paths" : [ { "editType" : "edit", "file" : "fs/quota/dquot.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/dsa/mv88e6xxx/global1_vtu.c" ], "commitId" : "3f14533a672b21b12aa3109f3f6d15c2fe90f4ff", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: dsa: mv88e6xxx: fix shift of FID bits in mv88e6185_g1_vtu_loadpurge()\u000a\u000a[ Upstream commit 48620e341659f6e4b978ec229f6944dabe6df709 ]\u000a\u000aThe comment is correct, but the code ends up moving the bits four\u000aplaces too far, into the VTUOp field.\u000a\u000aFixes: 11ea809f1a74 (net: dsa: mv88e6xxx: support 256 databases)\u000aSigned-off-by: Rasmus Villemoes \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "3f14533a672b21b12aa3109f3f6d15c2fe90f4ff", "msg" : "net: dsa: mv88e6xxx: fix shift of FID bits in mv88e6185_g1_vtu_loadpurge()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/dsa/mv88e6xxx/global1_vtu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "virt/kvm/arm/arch_timer.c" ], "commitId" : "7e5cb4da600918a2a2fecfa48771770853c3c0c3", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: arm/arm64: Fix emulated ptimer irq injection\u000a\u000a[ Upstream commit e4e5a865e9a9e8e47ac1959b629e9f3ae3b062f2 ]\u000a\u000aThe emulated ptimer needs to track the level changes, otherwise the\u000athe interrupt will never get deasserted, resulting in the guest getting\u000astuck in an interrupt storm if it enables ptimer interrupts. This was\u000afound with kvm-unit-tests; the ptimer tests hung as soon as interrupts\u000awere enabled. Typical Linux guests don't have a problem as they prefer\u000ausing the virtual timer.\u000a\u000aFixes: bee038a674875 (\"KVM: arm/arm64: Rework the timer code to use a timer_map\")\u000aSigned-off-by: Andrew Jones \u000a[Simplified the patch to res we only care about emulated timers here]\u000aSigned-off-by: Marc Zyngier \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "7e5cb4da600918a2a2fecfa48771770853c3c0c3", "msg" : "KVM: arm/arm64: Fix emulated ptimer irq injection", "paths" : [ { "editType" : "edit", "file" : "virt/kvm/arm/arch_timer.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/nfs/nfs4proc.c" ], "commitId" : "26fd9ac2120b4d05c5c4c9f6c8981c056cc6d1cd", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "NFS4: Only set creation opendata if O_CREAT\u000a\u000a[ Upstream commit 909105199a682cb09c500acd443d34b182846c9c ]\u000a\u000aWe can end up in nfs4_opendata_alloc during task exit, in which case\u000acurrent->fs has already been cleaned up. This leads to a crash in\u000acurrent_umask().\u000a\u000aFix this by only setting creation opendata if we are actually doing an open\u000awith O_CREAT. We can drop the check for NULL nfs4_open_createattrs, since\u000aO_CREAT will never be set for the recovery path.\u000a\u000aSuggested-by: Trond Myklebust \u000aSigned-off-by: Benjamin Coddington \u000aSigned-off-by: Anna Schumaker \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "26fd9ac2120b4d05c5c4c9f6c8981c056cc6d1cd", "msg" : "NFS4: Only set creation opendata if O_CREAT", "paths" : [ { "editType" : "edit", "file" : "fs/nfs/nfs4proc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/crypto/policy.c" ], "commitId" : "d326a510c017c37204212736ae0364e6b2e34404", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "fscrypt: don't set policy for a dead directory\u000a\u000acommit 5858bdad4d0d0fc18bf29f34c3ac836e0b59441f upstream.\u000a\u000aThe directory may have been removed when entering\u000afscrypt_ioctl_set_policy(). If so, the empty_dir() check will return\u000aerror for ext4 file system.\u000a\u000aext4_rmdir() sets i_size = 0, then ext4_empty_dir() reports an error\u000abecause 'inode->i_size < EXT4_DIR_REC_LEN(1) + EXT4_DIR_REC_LEN(2)'. If\u000athe fs is mounted with errors=panic, it will trigger a panic issue.\u000a\u000aAdd the check IS_DEADDIR() to fix this problem.\u000a\u000aFixes: 9bd8212f981e (\"ext4 crypto: add encryption policy and password salt support\")\u000aCc: # v4.1+\u000aSigned-off-by: Hongjie Fang \u000aSigned-off-by: Eric Biggers \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "d326a510c017c37204212736ae0364e6b2e34404", "msg" : "fscrypt: don't set policy for a dead directory", "paths" : [ { "editType" : "edit", "file" : "fs/crypto/policy.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/udf/inode.c" ], "commitId" : "f0ec469682c9d36012195f299bb3e942611b2450", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "udf: Fix incorrect final NOT_ALLOCATED (hole) extent length\u000a\u000acommit fa33cdbf3eceb0206a4f844fe91aeebcf6ff2b7a upstream.\u000a\u000aIn some cases, using the 'truncate' command to extend a UDF file results\u000ain a mismatch between the length of the file's extents (specifically, due\u000ato incorrect length of the final NOT_ALLOCATED extent) and the information\u000a(file) length. The discrepancy can prevent other operating systems\u000a(i.e., Windows 10) from opening the file.\u000a\u000aTwo particular errors have been observed when extending a file:\u000a\u000a1. The final extent is larger than it should be, having been rounded up\u000a to a multiple of the block size.\u000a\u000aB. The final extent is not shorter than it should be, due to not having\u000a been updated when the file's information length was increased.\u000a\u000a[JK: simplified udf_do_extend_final_block(), fixed up some types]\u000a\u000aFixes: 2c948b3f86e5 (\"udf: Avoid IO in udf_clear_inode\")\u000aCC: stable@vger.kernel.org\u000aSigned-off-by: Steven J. Magnani \u000aLink: https://lore.kernel.org/r/1561948775-5878-1-git-send-email-steve@digidescorp.com\u000aSigned-off-by: Jan Kara \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "f0ec469682c9d36012195f299bb3e942611b2450", "msg" : "udf: Fix incorrect final NOT_ALLOCATED (hole) extent length", "paths" : [ { "editType" : "edit", "file" : "fs/udf/inode.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/dvb-frontends/stv0297.c" ], "commitId" : "888b0232bd49f6dc0e27aaa9edca88bca3082d7f", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: stv0297: fix frequency range limit\u000a\u000acommit b09a2ab2baeb36bf7ef7780405ad172281741c7c upstream.\u000a\u000aThere was a typo at the lower frequency limit for a DVB-C\u000acard, causing the driver to fail while tuning channels at the\u000aVHF range.\u000a\u000ahttps://bugzilla.kernel.org/show_bug.cgi?id=202083\u000a\u000aFixes: f1b1eabff0eb (\"media: dvb: represent min/max/step/tolerance freqs in Hz\")\u000aReported-by: Ari Kohtamäki \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sean Young \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "888b0232bd49f6dc0e27aaa9edca88bca3082d7f", "msg" : "media: stv0297: fix frequency range limit", "paths" : [ { "editType" : "edit", "file" : "drivers/media/dvb-frontends/stv0297.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/uapi/linux/usb/audio.h", "sound/usb/mixer.c" ], "commitId" : "dd025262fe105e00d9194b4b9fcf4a7717c8b4f1", "timestamp" : 1563084586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: usb-audio: Fix parse of UAC2 Extension Units\u000a\u000acommit ca95c7bf3d29716916baccdc77c3c2284b703069 upstream.\u000a\u000aExtension Unit (XU) is used to have a compatible layout with\u000aProcessing Unit (PU) on UAC1, and the usb-audio driver code assumed it\u000afor parsing the descriptors. Meanwhile, on UAC2, XU became slightly\u000aincompatible with PU; namely, XU has a one-byte bmControls bitmap\u000awhile PU has two bytes bmControls bitmap. This incompatibility\u000aresults in the read of a wrong address for the last iExtension field,\u000awhich ended up with an incorrect string for the mixer element name, as\u000arecently reported for Focusrite Scarlett 18i20 device.\u000a\u000aThis patch corrects this misalignment by introducing a couple of new\u000amacros and calling them depending on the descriptor type.\u000a\u000aFixes: 23caaf19b11e (\"ALSA: usb-mixer: Add support for Audio Class v2.0\")\u000aReported-by: Stefan Sauer \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:46 +0200", "id" : "dd025262fe105e00d9194b4b9fcf4a7717c8b4f1", "msg" : "ALSA: usb-audio: Fix parse of UAC2 Extension Units", "paths" : [ { "editType" : "edit", "file" : "sound/usb/mixer.c" }, { "editType" : "edit", "file" : "include/uapi/linux/usb/audio.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_realtek.c" ], "commitId" : "b487df8a8b6f761d0327273f766f275e4153eeb6", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/realtek - Headphone Mic can't record after S3\u000a\u000acommit d07a9a4f66e944fcc900812cbc2f6817bde6a43d upstream.\u000a\u000aDell headset mode platform with ALC236.\u000aIt doesn't recording after system resume from S3.\u000aS3 mode was deep. s2idle was not has this issue.\u000aS3 deep will cut of codec power. So, the register will back to default\u000aafter resume back.\u000aThis patch will solve this issue.\u000a\u000aSigned-off-by: Kailang Yang \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "b487df8a8b6f761d0327273f766f275e4153eeb6", "msg" : "ALSA: hda/realtek - Headphone Mic can't record after S3", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_realtek.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/char/tpm/tpm2-cmd.c", "drivers/char/tpm/tpm1-cmd.c" ], "commitId" : "446daaf5d94a392c99e8a7fa48afb0dc472e701f", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tpm: Actually fail on TPM errors during \"get random\"\u000a\u000acommit 782779b60faa2fc7ff609ac8ef938260fd792c0f upstream.\u000a\u000aA \"get random\" may fail with a TPM error, but those codes were returned\u000aas-is to the caller, which assumed the result was the number of bytes\u000athat had been written to the target buffer, which could lead to a kernel\u000aheap memory exposure and over-read.\u000a\u000aThis fixes tpm1_get_random() to mask positive TPM errors into -EIO, as\u000abefore.\u000a\u000a[ 18.092103] tpm tpm0: A TPM error (379) occurred attempting get random\u000a[ 18.092106] usercopy: Kernel memory exposure attempt detected from SLUB object 'kmalloc-64' (offset 0, size 379)!\u000a\u000aLink: https://bugzilla.redhat.com/show_bug.cgi?id=1650989\u000aReported-by: Phil Baker \u000aReported-by: Craig Robson \u000aFixes: 7aee9c52d7ac (\"tpm: tpm1: rewrite tpm1_get_random() using tpm_buf structure\")\u000aCc: Laura Abbott \u000aCc: Tomas Winkler \u000aCc: Jarkko Sakkinen \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Kees Cook \u000aReviewed-by: Tomas Winkler \u000aTested-by: Bartosz Szczepanek \u000aReviewed-by: Jarkko Sakkinen \u000aSigned-off-by: Jarkko Sakkinen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "446daaf5d94a392c99e8a7fa48afb0dc472e701f", "msg" : "tpm: Actually fail on TPM errors during \"get random\"", "paths" : [ { "editType" : "edit", "file" : "drivers/char/tpm/tpm2-cmd.c" }, { "editType" : "edit", "file" : "drivers/char/tpm/tpm1-cmd.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/char/tpm/tpm-chip.c" ], "commitId" : "a28f6c295dbed6795617fc8e2466c53f2d3b0181", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations\u000a\u000acommit db4d8cb9c9f2af71c4d087817160d866ed572cc9 upstream.\u000a\u000aTPM 2.0 Shutdown involve sending TPM2_Shutdown to TPM chip and disabling\u000afuture TPM operations. TPM 1.2 behavior was different, future TPM\u000aoperations weren't disabled, causing rare issues. This patch ensures\u000athat future TPM operations are disabled.\u000a\u000aFixes: d1bd4a792d39 (\"tpm: Issue a TPM2_Shutdown for TPM2 devices.\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Vadim Sukhomlinov \u000a[dianders: resolved merge conflicts with mainline]\u000aSigned-off-by: Douglas Anderson \u000aReviewed-by: Jarkko Sakkinen \u000aSigned-off-by: Jarkko Sakkinen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "a28f6c295dbed6795617fc8e2466c53f2d3b0181", "msg" : "tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations", "paths" : [ { "editType" : "edit", "file" : "drivers/char/tpm/tpm-chip.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/bfq-iosched.c" ], "commitId" : "9b48536db7ea3365ba78bb35d8f96e9d7cd4e232", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "block, bfq: NULL out the bic when it's no longer valid\u000a\u000acommit dbc3117d4ca9e17819ac73501e914b8422686750 upstream.\u000a\u000aIn reboot tests on several devices we were seeing a \"use after free\"\u000awhen slub_debug or KASAN was enabled. The kernel complained about:\u000a\u000a Unable to handle kernel paging request at virtual address 6b6b6c2b\u000a\u000a...which is a classic sign of use after free under slub_debug. The\u000astack crawl in kgdb looked like:\u000a\u000a 0 test_bit (addr=, nr=)\u000a 1 bfq_bfqq_busy (bfqq=)\u000a 2 bfq_select_queue (bfqd=)\u000a 3 __bfq_dispatch_request (hctx=)\u000a 4 bfq_dispatch_request (hctx=)\u000a 5 0xc056ef00 in blk_mq_do_dispatch_sched (hctx=0xed249440)\u000a 6 0xc056f728 in blk_mq_sched_dispatch_requests (hctx=0xed249440)\u000a 7 0xc0568d24 in __blk_mq_run_hw_queue (hctx=0xed249440)\u000a 8 0xc0568d94 in blk_mq_run_work_fn (work=)\u000a 9 0xc024c5c4 in process_one_work (worker=0xec6d4640, work=0xed249480)\u000a 10 0xc024cff4 in worker_thread (__worker=0xec6d4640)\u000a\u000aDigging in kgdb, it could be found that, though bfqq looked fine,\u000abfqq->bic had been freed.\u000a\u000aThrough further digging, I postulated that perhaps it is illegal to\u000aaccess a \"bic\" (AKA an \"icq\") after bfq_exit_icq() had been called\u000abecause the \"bic\" can be freed at some point in time after this call\u000ais made. I confirmed that there certainly were cases where the exact\u000acrashing code path would access the \"bic\" after bfq_exit_icq() had\u000abeen called. Sspecifically I set the \"bfqq->bic\" to (void *)0x7 and\u000asaw that the bic was 0x7 at the time of the crash.\u000a\u000aTo understand a bit more about why this crash was fairly uncommon (I\u000asaw it only once in a few hundred reboots), you can see that much of\u000athe time bfq_exit_icq_fbqq() fully frees the bfqq and thus it can't\u000aaccess the ->bic anymore. The only case it doesn't is if\u000abfq_put_queue() sees a reference still held.\u000a\u000aHowever, even in the case when bfqq isn't freed, the crash is still\u000arare. Why? I tracked what happened to the \"bic\" after the exit\u000aroutine. It doesn't get freed right away. Rather,\u000aput_io_context_active() eventually called put_io_context() which\u000aqueued up freeing on a workqueue. The freeing then actually happened\u000alater than that through call_rcu(). Despite all these delays, some\u000aextra debugging showed that all the hoops could be jumped through in\u000atime and the memory could be freed causing the original crash. Phew!\u000a\u000aTo make a long story short, assuming it truly is illegal to access an\u000aicq after the \"exit_icq\" callback is finished, this patch is needed.\u000a\u000aCc: stable@vger.kernel.org\u000aReviewed-by: Paolo Valente \u000aSigned-off-by: Douglas Anderson \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "9b48536db7ea3365ba78bb35d8f96e9d7cd4e232", "msg" : "block, bfq: NULL out the bic when it's no longer valid", "paths" : [ { "editType" : "edit", "file" : "block/bfq-iosched.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/intel-pt.c" ], "commitId" : "91f87bc375d2e8b41d65073a4f05654d93096aae", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf intel-pt: Fix itrace defaults for perf script\u000a\u000acommit 26f19c2eb7e54015564ff133b91983a74e84541b upstream.\u000a\u000aCommit 4eb068157121 (\"perf script: Make itrace script default to all\u000acalls\") does not work because 'use_browser' is being used to determine\u000awhether to default to periodic sampling (i.e. better for perf report).\u000aThe result is that nothing but CBR events display for perf script when\u000ano --itrace option is specified.\u000a\u000aFix by using 'default_no_sample' and 'inject' instead.\u000a\u000aExample:\u000a\u000a Before:\u000a\u000a $ perf record -e intel_pt/cyc/u ls\u000a $ perf script > cmp1.txt\u000a $ perf script --itrace=cepwx > cmp2.txt\u000a $ diff -sq cmp1.txt cmp2.txt\u000a Files cmp1.txt and cmp2.txt differ\u000a\u000a After:\u000a\u000a $ perf script > cmp1.txt\u000a $ perf script --itrace=cepwx > cmp2.txt\u000a $ diff -sq cmp1.txt cmp2.txt\u000a Files cmp1.txt and cmp2.txt are identical\u000a\u000aSigned-off-by: Adrian Hunter \u000aTested-by: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: stable@vger.kernel.org # v4.20+\u000aFixes: 90e457f7be08 (\"perf tools: Add Intel PT support\")\u000aLink: http://lkml.kernel.org/r/20190520113728.14389-2-adrian.hunter@intel.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "91f87bc375d2e8b41d65073a4f05654d93096aae", "msg" : "perf intel-pt: Fix itrace defaults for perf script", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/intel-pt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/auxtrace.c" ], "commitId" : "0a205fd56ea118668f2b7a653537a33070e5e2f2", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf auxtrace: Fix itrace defaults for perf script\u000a\u000acommit 355200e0f6a9ce14771625014aa469f5ecbd8977 upstream.\u000a\u000aCommit 4eb068157121 (\"perf script: Make itrace script default to all\u000acalls\") does not work for the case when '--itrace' only is used, because\u000adefault_no_sample is not being passed.\u000a\u000aExample:\u000a\u000a Before:\u000a\u000a $ perf record -e intel_pt/cyc/u ls\u000a $ perf script --itrace > cmp1.txt\u000a $ perf script --itrace=cepwx > cmp2.txt\u000a $ diff -sq cmp1.txt cmp2.txt\u000a Files cmp1.txt and cmp2.txt differ\u000a\u000a After:\u000a\u000a $ perf script --itrace > cmp1.txt\u000a $ perf script --itrace=cepwx > cmp2.txt\u000a $ diff -sq cmp1.txt cmp2.txt\u000a Files cmp1.txt and cmp2.txt are identical\u000a\u000aSigned-off-by: Adrian Hunter \u000aTested-by: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: stable@vger.kernel.org\u000aFixes: 4eb068157121 (\"perf script: Make itrace script default to all calls\")\u000aLink: http://lkml.kernel.org/r/20190520113728.14389-3-adrian.hunter@intel.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "0a205fd56ea118668f2b7a653537a33070e5e2f2", "msg" : "perf auxtrace: Fix itrace defaults for perf script", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/auxtrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/Documentation/intel-pt.txt" ], "commitId" : "c30f3eda42279ed382ef71ca503faf1d93373eba", "timestamp" : 1563084587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf intel-pt: Fix itrace defaults for perf script intel-pt documentation\u000a\u000acommit a2d8a1585e35444789c1c8cf7e2e51fb15589880 upstream.\u000a\u000aFix intel-pt documentation to reflect the change of itrace defaults for\u000aperf script.\u000a\u000aSigned-off-by: Adrian Hunter \u000aCc: Jiri Olsa \u000aCc: stable@vger.kernel.org\u000aFixes: 4eb068157121 (\"perf script: Make itrace script default to all calls\")\u000aLink: http://lkml.kernel.org/r/20190520113728.14389-4-adrian.hunter@intel.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:47 +0200", "id" : "c30f3eda42279ed382ef71ca503faf1d93373eba", "msg" : "perf intel-pt: Fix itrace defaults for perf script intel-pt documentation", "paths" : [ { "editType" : "edit", "file" : "tools/perf/Documentation/intel-pt.txt" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/pmu.c" ], "commitId" : "286c71f17595737a76339476a45ee7ae44c0cb65", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf pmu: Fix uncore PMU alias list for ARM64\u000a\u000acommit 599ee18f0740d7661b8711249096db94c09bc508 upstream.\u000a\u000aIn commit 292c34c10249 (\"perf pmu: Fix core PMU alias list for X86\u000aplatform\"), we fixed the issue of CPU events being aliased to uncore\u000aevents.\u000a\u000aFix this same issue for ARM64, since the said commit left the (broken)\u000abehaviour untouched for ARM64.\u000a\u000aSigned-off-by: John Garry \u000aCc: Alexander Shishkin \u000aCc: Ben Hutchings \u000aCc: Hendrik Brueckner \u000aCc: Jiri Olsa \u000aCc: Kan Liang \u000aCc: Mark Rutland \u000aCc: Mathieu Poirier \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aCc: Shaokun Zhang \u000aCc: Thomas Richter \u000aCc: Will Deacon \u000aCc: linux-arm-kernel@lists.infradead.org\u000aCc: linuxarm@huawei.com\u000aCc: stable@vger.kernel.org\u000aFixes: 292c34c10249 (\"perf pmu: Fix core PMU alias list for X86 platform\")\u000aLink: http://lkml.kernel.org/r/1560521283-73314-2-git-send-email-john.garry@huawei.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "286c71f17595737a76339476a45ee7ae44c0cb65", "msg" : "perf pmu: Fix uncore PMU alias list for ARM64", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/pmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/thread-stack.c" ], "commitId" : "13449616e0343e8ee1ecf62263eeb0f00429724b", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf thread-stack: Fix thread stack return from kernel for kernel-only case\u000a\u000acommit 97860b483c5597663a174ff7405be957b4838391 upstream.\u000a\u000aCommit f08046cb3082 (\"perf thread-stack: Represent jmps to the start of a\u000adifferent symbol\") had the side-effect of introducing more stack entries\u000abefore return from kernel space.\u000a\u000aWhen user space is also traced, those entries are popped before entry to\u000auser space, but when user space is not traced, they get stuck at the\u000abottom of the stack, making the stack grow progressively larger.\u000a\u000aFix by detecting a return-from-kernel branch type, and popping kernel\u000aaddresses from the stack then.\u000a\u000aNote, the problem and fix affect the exported Call Graph / Tree but not\u000athe callindent option used by \"perf script --call-trace\".\u000a\u000aExample:\u000a\u000a perf-with-kcore record example -e intel_pt//k -- ls\u000a perf-with-kcore script example --itrace=bep -s ~/libexec/perf-core/scripts/python/export-to-sqlite.py example.db branches calls\u000a ~/libexec/perf-core/scripts/python/exported-sql-viewer.py example.db\u000a\u000a Menu option: Reports -> Context-Sensitive Call Graph\u000a\u000a Before: (showing Call Path column only)\u000a\u000a Call Path\u000a ▶ perf\u000a ▼ ls\u000a ▼ 12111:12111\u000a ▶ setup_new_exec\u000a ▶ __task_pid_nr_ns\u000a ▶ perf_event_pid_type\u000a ▶ perf_event_comm_output\u000a ▶ perf_iterate_ctx\u000a ▶ perf_iterate_sb\u000a ▶ perf_event_comm\u000a ▶ __set_task_comm\u000a ▶ load_elf_binary\u000a ▶ search_binary_handler\u000a ▶ __do_execve_file.isra.41\u000a ▶ __x64_sys_execve\u000a ▶ do_syscall_64\u000a ▼ entry_SYSCALL_64_after_hwframe\u000a ▼ swapgs_restore_regs_and_return_to_usermode\u000a ▼ native_iret\u000a ▶ error_entry\u000a ▶ do_page_fault\u000a ▼ error_exit\u000a ▼ retint_user\u000a ▶ prepare_exit_to_usermode\u000a ▼ native_iret\u000a ▶ error_entry\u000a ▶ do_page_fault\u000a ▼ error_exit\u000a ▼ retint_user\u000a ▶ prepare_exit_to_usermode\u000a ▼ native_iret\u000a ▶ error_entry\u000a ▶ do_page_fault\u000a ▼ error_exit\u000a ▼ retint_user\u000a ▶ prepare_exit_to_usermode\u000a ▶ native_iret\u000a\u000a After: (showing Call Path column only)\u000a\u000a Call Path\u000a ▶ perf\u000a ▼ ls\u000a ▼ 12111:12111\u000a ▶ setup_new_exec\u000a ▶ __task_pid_nr_ns\u000a ▶ perf_event_pid_type\u000a ▶ perf_event_comm_output\u000a ▶ perf_iterate_ctx\u000a ▶ perf_iterate_sb\u000a ▶ perf_event_comm\u000a ▶ __set_task_comm\u000a ▶ load_elf_binary\u000a ▶ search_binary_handler\u000a ▶ __do_execve_file.isra.41\u000a ▶ __x64_sys_execve\u000a ▶ do_syscall_64\u000a ▶ entry_SYSCALL_64_after_hwframe\u000a ▶ page_fault\u000a ▼ entry_SYSCALL_64\u000a ▼ do_syscall_64\u000a ▶ __x64_sys_brk\u000a ▶ __x64_sys_access\u000a ▶ __x64_sys_openat\u000a ▶ __x64_sys_newfstat\u000a ▶ __x64_sys_mmap\u000a ▶ __x64_sys_close\u000a ▶ __x64_sys_read\u000a ▶ __x64_sys_mprotect\u000a ▶ __x64_sys_arch_prctl\u000a ▶ __x64_sys_munmap\u000a ▶ exit_to_usermode_loop\u000a ▶ __x64_sys_set_tid_address\u000a ▶ __x64_sys_set_robust_list\u000a ▶ __x64_sys_rt_sigaction\u000a ▶ __x64_sys_rt_sigprocmask\u000a ▶ __x64_sys_prlimit64\u000a ▶ __x64_sys_statfs\u000a ▶ __x64_sys_ioctl\u000a ▶ __x64_sys_getdents64\u000a ▶ __x64_sys_write\u000a ▶ __x64_sys_exit_group\u000a\u000aCommitter notes:\u000a\u000aThe first arg to the perf-with-kcore needs to be the same for the\u000a'record' and 'script' lines, otherwise we'll record the perf.data file\u000aand kcore_dir/ files in one directory ('example') to then try to use it\u000afrom the 'bep' directory, fix the instructions above it so that both use\u000a'example'.\u000a\u000aSigned-off-by: Adrian Hunter \u000aTested-by: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: stable@vger.kernel.org\u000aFixes: f08046cb3082 (\"perf thread-stack: Represent jmps to the start of a different symbol\")\u000aLink: http://lkml.kernel.org/r/20190619064429.14940-2-adrian.hunter@intel.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "13449616e0343e8ee1ecf62263eeb0f00429724b", "msg" : "perf thread-stack: Fix thread stack return from kernel for kernel-only case", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/thread-stack.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/header.c" ], "commitId" : "5f2bad57c482b509702ce2b6646e647520db538e", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf header: Assign proper ff->ph in perf_event__synthesize_features()\u000a\u000acommit c952b35f4b15dd1b83e952718dec3307256383ef upstream.\u000a\u000abpf/btf write_* functions need ff->ph->env.\u000a\u000aWith this missing, pipe-mode (perf record -o -) would crash like:\u000a\u000aProgram terminated with signal SIGSEGV, Segmentation fault.\u000a\u000aThis patch assign proper ph value to ff.\u000a\u000aCommitter testing:\u000a\u000a (gdb) run record -o -\u000a Starting program: /root/bin/perf record -o -\u000a PERFILE2\u000a \u000a Thread 1 \"perf\" received signal SIGSEGV, Segmentation fault.\u000a __do_write_buf (size=4, buf=0x160, ff=0x7fffffff8f80) at util/header.c:126\u000a 126\u0009\u0009memcpy(ff->buf + ff->offset, buf, size);\u000a (gdb) bt\u000a #0 __do_write_buf (size=4, buf=0x160, ff=0x7fffffff8f80) at util/header.c:126\u000a #1 do_write (ff=ff@entry=0x7fffffff8f80, buf=buf@entry=0x160, size=4) at util/header.c:137\u000a #2 0x00000000004eddba in write_bpf_prog_info (ff=0x7fffffff8f80, evlist=) at util/header.c:912\u000a #3 0x00000000004f69d7 in perf_event__synthesize_features (tool=tool@entry=0x97cc00 , session=session@entry=0x7fffe9c6d010,\u000a evlist=0x7fffe9cae010, process=process@entry=0x4435d0 ) at util/header.c:3695\u000a #4 0x0000000000443c79 in record__synthesize (tail=tail@entry=false, rec=0x97cc00 ) at builtin-record.c:1214\u000a #5 0x0000000000444ec9 in __cmd_record (rec=0x97cc00 , argv=, argc=0) at builtin-record.c:1435\u000a #6 cmd_record (argc=0, argv=) at builtin-record.c:2450\u000a #7 0x00000000004ae3e9 in run_builtin (p=p@entry=0x98e058 , argc=argc@entry=3, argv=0x7fffffffd670) at perf.c:304\u000a #8 0x000000000042eded in handle_internal_command (argv=, argc=) at perf.c:356\u000a #9 run_argv (argcp=, argv=) at perf.c:400\u000a #10 main (argc=3, argv=) at perf.c:522\u000a (gdb)\u000a\u000aAfter the patch the SEGSEGV is gone.\u000a\u000aReported-by: David Carrillo Cisneros \u000aSigned-off-by: Song Liu \u000aTested-by: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: Namhyung Kim \u000aCc: kernel-team@fb.com\u000aCc: stable@vger.kernel.org # v5.1+\u000aFixes: 606f972b1361 (\"perf bpf: Save bpf_prog_info information as headers to perf.data\")\u000aLink: http://lkml.kernel.org/r/20190620010453.4118689-1-songliubraving@fb.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "5f2bad57c482b509702ce2b6646e647520db538e", "msg" : "perf header: Assign proper ff->ph in perf_event__synthesize_features()", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/header.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/ptrace.c" ], "commitId" : "d4ef7981cad64623c8bede832f2b7bbb4cc3d611", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()\u000a\u000acommit 31a2fbb390fee4231281b939e1979e810f945415 upstream.\u000a\u000aThe index to access the threads ptrace_bps is controlled by userspace via\u000asyscall: sys_ptrace(), hence leading to a potential exploitation of the\u000aSpectre variant 1 vulnerability.\u000a\u000aThe index can be controlled from:\u000a ptrace -> arch_ptrace -> ptrace_get_debugreg.\u000a\u000aFix this by sanitizing the user supplied index before using it access\u000athread->ptrace_bps.\u000a\u000aSigned-off-by: Dianzhang Chen \u000aSigned-off-by: Thomas Gleixner \u000aCc: bp@alien8.de\u000aCc: hpa@zytor.com\u000aCc: stable@vger.kernel.org\u000aLink: https://lkml.kernel.org/r/1561476617-3759-1-git-send-email-dianzhangchen0@gmail.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "d4ef7981cad64623c8bede832f2b7bbb4cc3d611", "msg" : "x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/ptrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/tls.c" ], "commitId" : "f26cffdb59f7953b22b16a891c3c1f2371bb1149", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/tls: Fix possible spectre-v1 in do_get_thread_area()\u000a\u000acommit 993773d11d45c90cb1c6481c2638c3d9f092ea5b upstream.\u000a\u000aThe index to access the threads tls array is controlled by userspace\u000avia syscall: sys_ptrace(), hence leading to a potential exploitation\u000aof the Spectre variant 1 vulnerability.\u000a\u000aThe index can be controlled from:\u000a ptrace -> arch_ptrace -> do_get_thread_area.\u000a\u000aFix this by sanitizing the user supplied index before using it to access\u000athe p->thread.tls_array.\u000a\u000aSigned-off-by: Dianzhang Chen \u000aSigned-off-by: Thomas Gleixner \u000aCc: bp@alien8.de\u000aCc: hpa@zytor.com\u000aCc: stable@vger.kernel.org\u000aLink: https://lkml.kernel.org/r/1561524630-3642-1-git-send-email-dianzhangchen0@gmail.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "f26cffdb59f7953b22b16a891c3c1f2371bb1149", "msg" : "x86/tls: Fix possible spectre-v1 in do_get_thread_area()", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/tls.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/admin-guide/hw-vuln/spectre.rst", "Documentation/userspace-api/spec_ctrl.rst", "Documentation/admin-guide/hw-vuln/index.rst" ], "commitId" : "bbf4f4234e0acb88157841f426c6128f762ae3a7", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Documentation: Add section about CPU vulnerabilities for Spectre\u000a\u000acommit 6e88559470f581741bcd0f2794f9054814ac9740 upstream.\u000a\u000aAdd documentation for Spectre vulnerability and the mitigation mechanisms:\u000a\u000a- Explain the problem and risks\u000a- Document the mitigation mechanisms\u000a- Document the command line controls\u000a- Document the sysfs files\u000a\u000aCo-developed-by: Andi Kleen \u000aSigned-off-by: Andi Kleen \u000aCo-developed-by: Tim Chen \u000aSigned-off-by: Tim Chen \u000aReviewed-by: Randy Dunlap \u000aReviewed-by: Thomas Gleixner \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jonathan Corbet \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "bbf4f4234e0acb88157841f426c6128f762ae3a7", "msg" : "Documentation: Add section about CPU vulnerabilities for Spectre", "paths" : [ { "editType" : "add", "file" : "Documentation/admin-guide/hw-vuln/spectre.rst" }, { "editType" : "edit", "file" : "Documentation/admin-guide/hw-vuln/index.rst" }, { "editType" : "edit", "file" : "Documentation/userspace-api/spec_ctrl.rst" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/admin-guide/kernel-parameters.txt" ], "commitId" : "bca7f52f10d0fe6534c568d163419de9d031a71f", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Documentation/admin: Remove the vsyscall=native documentation\u000a\u000acommit d974ffcfb7447db5f29a4b662a3eaf99a4e1109e upstream.\u000a\u000aThe vsyscall=native feature is gone -- remove the docs.\u000a\u000aFixes: 076ca272a14c (\"x86/vsyscall/64: Drop \"native\" vsyscalls\")\u000aSigned-off-by: Andy Lutomirski \u000aSigned-off-by: Thomas Gleixner \u000aAcked-by: Kees Cook \u000aCc: Florian Weimer \u000aCc: Jann Horn \u000aCc: stable@vger.kernel.org\u000aCc: Borislav Petkov \u000aCc: Kernel Hardening \u000aCc: Peter Zijlstra \u000aLink: https://lkml.kernel.org/r/d77c7105eb4c57c1a95a95b6a5b8ba194a18e764.1561610354.git.luto@kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "bca7f52f10d0fe6534c568d163419de9d031a71f", "msg" : "Documentation/admin: Remove the vsyscall=native documentation", "paths" : [ { "editType" : "edit", "file" : "Documentation/admin-guide/kernel-parameters.txt" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/marvell/mwifiex/scan.c" ], "commitId" : "5a93f9120a1ab3fb2db98ea4a2fb0609e789d12f", "timestamp" : 1563084588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mwifiex: Abort at too short BSS descriptor element\u000a\u000acommit 685c9b7750bfacd6fc1db50d86579980593b7869 upstream.\u000a\u000aCurrently mwifiex_update_bss_desc_with_ie() implicitly assumes that\u000athe source descriptor entries contain the enough size for each type\u000aand performs copying without checking the source size. This may lead\u000ato read over boundary.\u000a\u000aFix this by putting the source size check in appropriate places.\u000a\u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:48 +0200", "id" : "5a93f9120a1ab3fb2db98ea4a2fb0609e789d12f", "msg" : "mwifiex: Abort at too short BSS descriptor element", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/scan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/marvell/mwifiex/wmm.c", "drivers/net/wireless/marvell/mwifiex/fw.h", "drivers/net/wireless/marvell/mwifiex/scan.c", "drivers/net/wireless/marvell/mwifiex/sta_ioctl.c" ], "commitId" : "b441bf73158b3adea913fbd5d6002cdb556ee0d3", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mwifiex: Don't abort on small, spec-compliant vendor IEs\u000a\u000acommit 63d7ef36103d26f20325a921ecc96a3288560146 upstream.\u000a\u000aPer the 802.11 specification, vendor IEs are (at minimum) only required\u000ato contain an OUI. A type field is also included in ieee80211.h (struct\u000aieee80211_vendor_ie) but doesn't appear in the specification. The\u000aremaining fields (subtype, version) are a convention used in WMM\u000aheaders.\u000a\u000aThus, we should not reject vendor-specific IEs that have only the\u000aminimum length (3 bytes) -- we should skip over them (since we only want\u000ato match longer IEs, that match either WMM or WPA formats). We can\u000areject elements that don't have the minimum-required 3 byte OUI.\u000a\u000aWhile we're at it, move the non-standard subtype and version fields into\u000athe WMM structs, to avoid this confusion in the future about generic\u000a\"vendor header\" attributes.\u000a\u000aFixes: 685c9b7750bf (\"mwifiex: Abort at too short BSS descriptor element\")\u000aCc: Takashi Iwai \u000aSigned-off-by: Brian Norris \u000aReviewed-by: Takashi Iwai \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "b441bf73158b3adea913fbd5d6002cdb556ee0d3", "msg" : "mwifiex: Don't abort on small, spec-compliant vendor IEs", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/wmm.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/fw.h" }, { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/sta_ioctl.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/marvell/mwifiex/scan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/serial/ftdi_sio.c", "drivers/usb/serial/ftdi_sio_ids.h" ], "commitId" : "b9baf84e016e7107919a4ab6a9df2c290d1d1786", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "USB: serial: ftdi_sio: add ID for isodebug v1\u000a\u000acommit f8377eff548170e8ea8022c067a1fbdf9e1c46a8 upstream.\u000a\u000aThis adds the vid:pid of the isodebug v1 isolated JTAG/SWD+UART. Only the\u000asecond channel is available for use as a serial port.\u000a\u000aSigned-off-by: Andreas Fritiofson \u000aCc: stable \u000aSigned-off-by: Johan Hovold \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "b9baf84e016e7107919a4ab6a9df2c290d1d1786", "msg" : "USB: serial: ftdi_sio: add ID for isodebug v1", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/serial/ftdi_sio.c" }, { "editType" : "edit", "file" : "drivers/usb/serial/ftdi_sio_ids.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/serial/option.c" ], "commitId" : "c02af52b6c1c55bd930f7988059cfbfc2d790be6", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "USB: serial: option: add support for GosunCn ME3630 RNDIS mode\u000a\u000acommit aed2a26283528fb69c38e414f649411aa48fb391 upstream.\u000a\u000aAdded USB IDs for GosunCn ME3630 cellular module in RNDIS mode.\u000a\u000aT: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=03 Dev#= 18 Spd=480 MxCh= 0\u000aD: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1\u000aP: Vendor=19d2 ProdID=0601 Rev=03.18\u000aS: Manufacturer=Android\u000aS: Product=Android\u000aS: SerialNumber=b950269c\u000aC: #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=500mA\u000aI: If#=0x0 Alt= 0 #EPs= 1 Cls=e0(wlcon) Sub=01 Prot=03 Driver=rndis_host\u000aI: If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host\u000aI: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option\u000aI: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option\u000aI: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option\u000a\u000aSigned-off-by: Jörgen Storvist \u000aCc: stable \u000aSigned-off-by: Johan Hovold \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "c02af52b6c1c55bd930f7988059cfbfc2d790be6", "msg" : "USB: serial: option: add support for GosunCn ME3630 RNDIS mode", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/serial/option.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/tty/serial/8250/8250_port.c" ], "commitId" : "32a88e920591efb9beff6a1916ca05dc98b9bb2e", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Revert \"serial: 8250: Don't service RX FIFO if interrupts are disabled\"\u000a\u000acommit 3f2640ed7be838c3f05c0d2b0f7c7508e7431e48 upstream.\u000a\u000aThis reverts commit 2e9fe539108320820016f78ca7704a7342788380.\u000a\u000aReading LSR unconditionally but processing the error flags only if\u000aUART_IIR_RDI bit was set before in IIR may lead to a loss of transmission\u000aerror information on UARTs where the transmission error flags are cleared\u000aby a read of LSR. Information are lost in case an error is detected right\u000abefore the read of LSR while processing e.g. an UART_IIR_THRI interrupt.\u000a\u000aSigned-off-by: Oliver Barta \u000aReviewed-by: Andy Shevchenko \u000aFixes: 2e9fe5391083 (\"serial: 8250: Don't service RX FIFO if interrupts are disabled\")\u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "32a88e920591efb9beff6a1916ca05dc98b9bb2e", "msg" : "Revert \"serial: 8250: Don't service RX FIFO if interrupts are disabled\"", "paths" : [ { "editType" : "edit", "file" : "drivers/tty/serial/8250/8250_port.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intersil/p54/p54usb.c" ], "commitId" : "cae928691200cbe65da1b31d92472f50abe48a14", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "p54usb: Fix race between disconnect and firmware loading\u000a\u000acommit 6e41e2257f1094acc37618bf6c856115374c6922 upstream.\u000a\u000aThe syzbot fuzzer found a bug in the p54 USB wireless driver. The\u000aissue involves a race between disconnect and the firmware-loader\u000acallback routine, and it has several aspects.\u000a\u000aOne big problem is that when the firmware can't be loaded, the\u000acallback routine tries to unbind the driver from the USB _device_ (by\u000acalling device_release_driver) instead of from the USB _interface_ to\u000awhich it is actually bound (by calling usb_driver_release_interface).\u000a\u000aThe race involves access to the private data structure. The driver's\u000adisconnect handler waits for a completion that is signalled by the\u000afirmware-loader callback routine. As soon as the completion is\u000asignalled, you have to assume that the private data structure may have\u000abeen deallocated by the disconnect handler -- even if the firmware was\u000aloaded without errors. However, the callback routine does access the\u000aprivate data several times after that point.\u000a\u000aAnother problem is that, in order to ensure that the USB device\u000astructure hasn't been freed when the callback routine runs, the driver\u000atakes a reference to it. This isn't good enough any more, because now\u000athat the callback routine calls usb_driver_release_interface, it has\u000ato ensure that the interface structure hasn't been freed.\u000a\u000aFinally, the driver takes an unnecessary reference to the USB device\u000astructure in the probe function and drops the reference in the\u000adisconnect handler. This extra reference doesn't accomplish anything,\u000abecause the USB core already guarantees that a device structure won't\u000abe deallocated while a driver is still bound to any of its interfaces.\u000a\u000aTo fix these problems, this patch makes the following changes:\u000a\u000a\u0009Call usb_driver_release_interface() rather than\u000a\u0009device_release_driver().\u000a\u000a\u0009Don't signal the completion until after the important\u000a\u0009information has been copied out of the private data structure,\u000a\u0009and don't refer to the private data at all thereafter.\u000a\u000a\u0009Lock udev (the interface's parent) before unbinding the driver\u000a\u0009instead of locking udev->parent.\u000a\u000a\u0009During the firmware loading process, take a reference to the\u000a\u0009USB interface instead of the USB device.\u000a\u000a\u0009Don't take an unnecessary reference to the device during probe\u000a\u0009(and then don't drop it during disconnect).\u000a\u000aSigned-off-by: Alan Stern \u000aReported-and-tested-by: syzbot+200d4bb11b23d929335f@syzkaller.appspotmail.com\u000aCC: \u000aAcked-by: Christian Lamparter \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "cae928691200cbe65da1b31d92472f50abe48a14", "msg" : "p54usb: Fix race between disconnect and firmware loading", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intersil/p54/p54usb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/gadget/function/f_fs.c" ], "commitId" : "5b5a979c8fb2d5d85789c577478762d6d5c99fe9", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "usb: gadget: f_fs: data_len used before properly set\u000a\u000acommit 4833a94eb383f5b22775077ff92ddaae90440921 upstream.\u000a\u000aThe following line of code in function ffs_epfile_io is trying to set\u000aflag io_data->use_sg in case buffer required is larger than one page.\u000a\u000a io_data->use_sg = gadget->sg_supported && data_len > PAGE_SIZE;\u000a\u000aHowever at this point of time the variable data_len has not been set\u000ato the proper buffer size yet. The consequence is that io_data->use_sg\u000ais always set regardless what buffer size really is, because the condition\u000a(data_len > PAGE_SIZE) is effectively an unsigned comparison between\u000a-EINVAL and PAGE_SIZE which would always result in TRUE.\u000a\u000aFixes: 772a7a724f69 (\"usb: gadget: f_fs: Allow scatter-gather buffers\")\u000aSigned-off-by: Fei Yang \u000aCc: stable \u000aSigned-off-by: Felipe Balbi \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "5b5a979c8fb2d5d85789c577478762d6d5c99fe9", "msg" : "usb: gadget: f_fs: data_len used before properly set", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/gadget/function/f_fs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/gadget/function/u_ether.c" ], "commitId" : "43b417e412f10d7a9dee7b519904d4c619072320", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "usb: gadget: ether: Fix race between gether_disconnect and rx_submit\u000a\u000acommit d29fcf7078bc8be2b6366cbd4418265b53c94fac upstream.\u000a\u000aOn spin lock release in rx_submit, gether_disconnect get a chance to\u000arun, it makes port_usb NULL, rx_submit access NULL port USB, hence null\u000apointer crash.\u000a\u000aFixed by releasing the lock in rx_submit after port_usb is used.\u000a\u000aFixes: 2b3d942c4878 (\"usb ethernet gadget: split out network core\")\u000aCc: \u000aSigned-off-by: Kiruthika Varadarajan \u000aSigned-off-by: Felipe Balbi \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "43b417e412f10d7a9dee7b519904d4c619072320", "msg" : "usb: gadget: ether: Fix race between gether_disconnect and rx_submit", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/gadget/function/u_ether.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/dwc2/core.c" ], "commitId" : "4351a218d30030f229911f23edec3efff9b6719a", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "usb: dwc2: use a longer AHB idle timeout in dwc2_core_reset()\u000a\u000acommit dfc4fdebc5d62ac4e2fe5428e59b273675515fb2 upstream.\u000a\u000aUse a 10000us AHB idle timeout in dwc2_core_reset() and make it\u000aconsistent with the other \"wait for AHB master IDLE state\" ocurrences.\u000a\u000aThis fixes a problem for me where dwc2 would not want to initialize when\u000aupdating to 4.19 on a MIPS Lantiq VRX200 SoC. dwc2 worked fine with\u000a4.14.\u000aTesting on my board shows that it takes 180us until AHB master IDLE\u000astate is signalled. The very old vendor driver for this SoC (ifxhcd)\u000aused a 1 second timeout.\u000aUse the same timeout that is used everywhere when polling for\u000aGRSTCTL_AHBIDLE instead of using a timeout that \"works for one board\"\u000a(180us in my case) to have consistent behavior across the dwc2 driver.\u000a\u000aCc: linux-stable # 4.19+\u000aAcked-by: Minas Harutyunyan \u000aSigned-off-by: Martin Blumenstingl \u000aSigned-off-by: Felipe Balbi \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "4351a218d30030f229911f23edec3efff9b6719a", "msg" : "usb: dwc2: use a longer AHB idle timeout in dwc2_core_reset()", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/dwc2/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/renesas_usbhs/fifo.c" ], "commitId" : "bc696de1d8fda6f16b9bcb05bb3d20e986edf52f", "timestamp" : 1563084589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "usb: renesas_usbhs: add a workaround for a race condition of workqueue\u000a\u000acommit b2357839c56ab7d06bcd4e866ebc2d0e2b7997f3 upstream.\u000a\u000aThe old commit 6e4b74e4690d (\"usb: renesas: fix scheduling in atomic\u000acontext bug\") fixed an atomic issue by using workqueue for the shdmac\u000admaengine driver. However, this has a potential race condition issue\u000abetween the work pending and usbhsg_ep_free_request() in gadget mode.\u000aWhen usbhsg_ep_free_request() is called while pending the queue,\u000asince the work_struct will be freed and then the work handler is\u000acalled, kernel panic happens on process_one_work().\u000a\u000aTo fix the issue, if we could call cancel_work_sync() at somewhere\u000abefore the free request, it could be easy. However,\u000athe usbhsg_ep_free_request() is called on atomic (e.g. f_ncm driver\u000acalls free request via gether_disconnect()).\u000a\u000aFor now, almost all users are having \"USB-DMAC\" and the DMAengine\u000adriver can be used on atomic. So, this patch adds a workaround for\u000aa race condition to call the DMAengine APIs without the workqueue.\u000a\u000aThis means we still have TODO on shdmac environment (SH7724), but\u000asince it doesn't have SMP, the race condition might not happen.\u000a\u000aFixes: ab330cf3888d (\"usb: renesas_usbhs: add support for USB-DMAC\")\u000aCc: # v4.1+\u000aSigned-off-by: Yoshihiro Shimoda \u000aSigned-off-by: Felipe Balbi \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:49 +0200", "id" : "bc696de1d8fda6f16b9bcb05bb3d20e986edf52f", "msg" : "usb: renesas_usbhs: add a workaround for a race condition of workqueue", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/renesas_usbhs/fifo.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/typec/tps6598x.c" ], "commitId" : "8a2f9af6e5231433cd6da76af82c570a1c0f691a", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drivers/usb/typec/tps6598x.c: fix portinfo width\u000a\u000acommit 05da75fc651138e51ff74ace97174349910463f5 upstream.\u000a\u000aPortinfo bit field is 3 bits wide, not 2 bits. This led to\u000aa wrong driver configuration for some tps6598x configurations.\u000a\u000aFixes: 0a4c005bd171 (\"usb: typec: driver for TI TPS6598x USB Power Delivery controllers\")\u000aSigned-off-by: Nikolaus Voss \u000aAcked-by: Heikki Krogerus \u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "8a2f9af6e5231433cd6da76af82c570a1c0f691a", "msg" : "drivers/usb/typec/tps6598x.c: fix portinfo width", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/typec/tps6598x.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/typec/tps6598x.c" ], "commitId" : "52a7655707a8d50acfee28fdafb9c54930e985f5", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drivers/usb/typec/tps6598x.c: fix 4CC cmd write\u000a\u000acommit 2681795b5e7a5bf336537661010072f4c22cea31 upstream.\u000a\u000aWriting 4CC commands with tps6598x_write_4cc() already has\u000aa pointer arg, don't reference it when using as arg to\u000atps6598x_block_write(). Correcting this enforces the constness\u000aof the pointer to propagate to tps6598x_block_write(), so add\u000athe const qualifier there to avoid the warning.\u000a\u000aFixes: 0a4c005bd171 (\"usb: typec: driver for TI TPS6598x USB Power Delivery controllers\")\u000aSigned-off-by: Nikolaus Voss \u000aAcked-by: Heikki Krogerus \u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "52a7655707a8d50acfee28fdafb9c54930e985f5", "msg" : "drivers/usb/typec/tps6598x.c: fix 4CC cmd write", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/typec/tps6598x.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intersil/p54/txrx.c" ], "commitId" : "99fdac8553c937b401c6e763a6caa08988d82de6", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "p54: fix crash during initialization\u000a\u000acommit 1645ab931998b39aed5761f095956f0b10a6362f upstream.\u000a\u000aThis patch fixes a crash that got introduced when the\u000amentioned patch replaced the direct list_head access\u000awith skb_peek_tail(). When the device is starting up,\u000athere are no entries in the queue, so previously to\u000a\"Use skb_peek_tail() instead...\" the target_skb would\u000aend up as the tail and head pointer which then could\u000abe used by __skb_queue_after to fill the empty queue.\u000a\u000aWith skb_peek_tail() in its place will instead just\u000areturn NULL which then causes a crash in the\u000a__skb_queue_after().\u000a\u000a| BUG: unable to handle kernel NULL pointer dereference at 000000\u000a| #PF error: [normal kernel read fault]\u000a| PGD 0 P4D 0\u000a| Oops: 0000 [#1] SMP PTI\u000a| CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: GO 5.1.0-rc7-wt+ #218\u000a| Hardware name: MSI MS-7816/Z87-G43 (MS-7816), BIOS V1.11 05/09/2015\u000a| Workqueue: events request_firmware_work_func\u000a| RIP: 0010:p54_tx_pending+0x10f/0x1b0 [p54common]\u000a| Code: 78 06 80 78 28 00 74 6d <48> 8b 07 49 89 7c 24 08 49 89 04 24 4\u000a| RSP: 0018:ffffa81c81927d90 EFLAGS: 00010086\u000a| RAX: ffff9bbaaf131048 RBX: 0000000000020670 RCX: 0000000000020264\u000a| RDX: ffff9bbaa976d660 RSI: 0000000000000202 RDI: 0000000000000000\u000a| RBP: ffff9bbaa976d620 R08: 00000000000006c0 R09: ffff9bbaa976d660\u000a| R10: 0000000000000000 R11: ffffe8480dbc5900 R12: ffff9bbb45e87700\u000a| R13: ffff9bbaa976d648 R14: ffff9bbaa976d674 R15: ffff9bbaaf131048\u000a| FS: 0000000000000000(0000) GS:ffff9bbb5ec00000(0000) knlGS:00000\u000a| CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a| CR2: 0000000000000000 CR3: 00000003695fc003 CR4: 00000000001606f0\u000a| Call Trace:\u000a| p54_download_eeprom+0xbe/0x120 [p54common]\u000a| p54_read_eeprom+0x7f/0xc0 [p54common]\u000a| p54u_load_firmware_cb+0xe0/0x160 [p54usb]\u000a| request_firmware_work_func+0x42/0x80\u000a| process_one_work+0x1f5/0x3f0\u000a| worker_thread+0x28/0x3c0\u000a\u000aCc: stable@vger.kernel.org\u000aFixes: e3554197fc8f (\"p54: Use skb_peek_tail() instead of direct head pointer accesses.\")\u000aSigned-off-by: Christian Lamparter \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "99fdac8553c937b401c6e763a6caa08988d82de6", "msg" : "p54: fix crash during initialization", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intersil/p54/txrx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/comedi/drivers/dt282x.c" ], "commitId" : "e634a09b6de5323bb1993993f8a4a6ac2ab05966", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: comedi: dt282x: fix a null pointer deref on interrupt\u000a\u000acommit b8336be66dec06bef518030a0df9847122053ec5 upstream.\u000a\u000aThe interrupt handler `dt282x_interrupt()` causes a null pointer\u000adereference for those supported boards that have no analog output\u000asupport. For these boards, `dev->write_subdev` will be `NULL` and\u000atherefore the `s_ao` subdevice pointer variable will be `NULL`. In that\u000acase, the following call near the end of the interrupt handler results\u000ain a null pointer dereference:\u000a\u000a\u0009comedi_handle_events(dev, s_ao);\u000a\u000aFix it by only calling the above function if `s_ao` is valid.\u000a\u000a(There are other uses of `s_ao` by the interrupt handler that may or may\u000anot be reached depending on values of hardware registers. Trust that\u000athey are reliable for now.)\u000a\u000aNote:\u000acommit 4f6f009b204f (\"staging: comedi: dt282x: use comedi_handle_events()\")\u000apropagates an earlier error from\u000acommit f21c74fa4cfe (\"staging: comedi: dt282x: use cfc_handle_events()\").\u000a\u000aFixes: 4f6f009b204f (\"staging: comedi: dt282x: use comedi_handle_events()\")\u000aCc: # v3.19+\u000aSigned-off-by: Ian Abbott \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "e634a09b6de5323bb1993993f8a4a6ac2ab05966", "msg" : "staging: comedi: dt282x: fix a null pointer deref on interrupt", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/comedi/drivers/dt282x.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/wilc1000/wilc_netdev.c" ], "commitId" : "2720d5677d801749ce1907ac42c1cf461576a8f9", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: wilc1000: fix error path cleanup in wilc_wlan_initialize()\u000a\u000acommit 6419f818ababebc1116fb2d0e220bd4fe835d0e3 upstream.\u000a\u000aFor the error path in wilc_wlan_initialize(), the resources are not\u000acleanup in the correct order. Reverted the previous changes and use the\u000acorrect order to free during error condition.\u000a\u000aFixes: b46d68825c2d (\"staging: wilc1000: remove COMPLEMENT_BOOT\")\u000aCc: \u000aSigned-off-by: Ajay Singh \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "2720d5677d801749ce1907ac42c1cf461576a8f9", "msg" : "staging: wilc1000: fix error path cleanup in wilc_wlan_initialize()", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/wilc1000/wilc_netdev.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/comedi/drivers/amplc_pci230.c" ], "commitId" : "811c7e8f1ef5312520457ccd48c2bd0422b3220c", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: comedi: amplc_pci230: fix null pointer deref on interrupt\u000a\u000acommit 7379e6baeddf580d01feca650ec1ad508b6ea8ee upstream.\u000a\u000aThe interrupt handler `pci230_interrupt()` causes a null pointer\u000adereference for a PCI260 card. There is no analog output subdevice for\u000aa PCI260. The `dev->write_subdev` subdevice pointer and therefore the\u000a`s_ao` subdevice pointer variable will be `NULL` for a PCI260. The\u000afollowing call near the end of the interrupt handler results in the null\u000apointer dereference for a PCI260:\u000a\u000a\u0009comedi_handle_events(dev, s_ao);\u000a\u000aFix it by only calling the above function if `s_ao` is valid.\u000a\u000aNote that the other uses of `s_ao` in the calls\u000a`pci230_handle_ao_nofifo(dev, s_ao);` and `pci230_handle_ao_fifo(dev,\u000as_ao);` will never be reached for a PCI260, so they are safe.\u000a\u000aFixes: 39064f23284c (\"staging: comedi: amplc_pci230: use comedi_handle_events()\")\u000aCc: # v3.19+\u000aSigned-off-by: Ian Abbott \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "811c7e8f1ef5312520457ccd48c2bd0422b3220c", "msg" : "staging: comedi: amplc_pci230: fix null pointer deref on interrupt", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/comedi/drivers/amplc_pci230.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/mt7621-pci/pci-mt7621.c" ], "commitId" : "7e5487c385591c7094b006e4bb300440eb899c7b", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: mt7621-pci: fix PCIE_FTS_NUM_LO macro\u000a\u000acommit 0ae0cf509d28d8539b88b5f7f24558f5bfe57cdf upstream.\u000a\u000aAdd missing parenthesis to PCIE_FTS_NUM_LO macro to do the\u000asame it was being done in original code.\u000a\u000aFixes: a4b2eb912bb1 (\"staging: mt7621-pci: rewrite RC FTS configuration\")\u000aSigned-off-by: Sergio Paracuellos \u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "7e5487c385591c7094b006e4bb300440eb899c7b", "msg" : "staging: mt7621-pci: fix PCIE_FTS_NUM_LO macro", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/mt7621-pci/pci-mt7621.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/hid-ids.h", "drivers/hid/hid-quirks.c" ], "commitId" : "efb27acc284420bd099df151d99b437c0fa83816", "timestamp" : 1563084590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: Add another Primax PIXART OEM mouse quirk\u000a\u000acommit 4c12954965fdf33d8ae3883c1931fc29ca023cfb upstream.\u000a\u000aThe PixArt OEM mice are known for disconnecting every minute in\u000arunlevel 1 or 3 if they are not always polled. So add quirk\u000aALWAYS_POLL for this Alienware branded Primax mouse as well.\u000a\u000aDaniel Schepler (@dschepler) reported and tested the quirk.\u000aReference: https://github.com/sriemer/fix-linux-mouse/issues/15\u000a\u000aSigned-off-by: Sebastian Parschauer \u000aCC: stable@vger.kernel.org\u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:50 +0200", "id" : "efb27acc284420bd099df151d99b437c0fa83816", "msg" : "HID: Add another Primax PIXART OEM mouse quirk", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/hid-quirks.c" }, { "editType" : "edit", "file" : "drivers/hid/hid-ids.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/misc/lkdtm/Makefile" ], "commitId" : "cd05fb747726f7e2292ca3b6e654b3938ecc59b5", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "lkdtm: support llvm-objcopy\u000a\u000acommit e9e08a07385e08f1a7f85c5d1e345c21c9564963 upstream.\u000a\u000aWith CONFIG_LKDTM=y and make OBJCOPY=llvm-objcopy, llvm-objcopy errors:\u000allvm-objcopy: error: --set-section-flags=.text conflicts with\u000a--rename-section=.text=.rodata\u000a\u000aRather than support setting flags then renaming sections vs renaming\u000athen setting flags, it's simpler to just change both at the same time\u000avia --rename-section. Adding the load flag is required for GNU objcopy\u000ato mark .rodata Type as PROGBITS after the rename.\u000a\u000aThis can be verified with:\u000a$ readelf -S drivers/misc/lkdtm/rodata_objcopy.o\u000a...\u000aSection Headers:\u000a [Nr] Name Type Address Offset\u000a Size EntSize Flags Link Info Align\u000a...\u000a [ 1] .rodata PROGBITS 0000000000000000 00000040\u000a 0000000000000004 0000000000000000 A 0 0 4\u000a...\u000a\u000aWhich shows that .text is now renamed .rodata, the alloc flag A is set,\u000athe type is PROGBITS, and the section is not flagged as writeable W.\u000a\u000aCc: stable@vger.kernel.org\u000aLink: https://sourceware.org/bugzilla/show_bug.cgi?id=24554\u000aLink: https://github.com/ClangBuiltLinux/linux/issues/448\u000aReported-by: Nathan Chancellor \u000aSuggested-by: Alan Modra \u000aSuggested-by: Jordan Rupprect \u000aSuggested-by: Kees Cook \u000aAcked-by: Kees Cook \u000aReviewed-by: Nathan Chancellor \u000aSigned-off-by: Nick Desaulniers \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "cd05fb747726f7e2292ca3b6e654b3938ecc59b5", "msg" : "lkdtm: support llvm-objcopy", "paths" : [ { "editType" : "edit", "file" : "drivers/misc/lkdtm/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/android/binder.c" ], "commitId" : "93a260f17e29beadb7b4f4c6f95c305f0e73bcae", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "binder: fix memory leak in error path\u000a\u000acommit 1909a671dbc3606685b1daf8b22a16f65ea7edda upstream.\u000a\u000asyzkallar found a 32-byte memory leak in a rarely executed error\u000acase. The transaction complete work item was not freed if put_user()\u000afailed when writing the BR_TRANSACTION_COMPLETE to the user command\u000abuffer. Fixed by freeing it before put_user() is called.\u000a\u000aReported-by: syzbot+182ce46596c3f2e1eb24@syzkaller.appspotmail.com\u000aSigned-off-by: Todd Kjos \u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "93a260f17e29beadb7b4f4c6f95c305f0e73bcae", "msg" : "binder: fix memory leak in error path", "paths" : [ { "editType" : "edit", "file" : "drivers/android/binder.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/android/binder.c", "drivers/android/binder_alloc.h", "drivers/android/binder_alloc.c" ], "commitId" : "9edfd065a0b85f94ca5f7ea993fe50ad558511a7", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "binder: return errors from buffer copy functions\u000a\u000acommit bb4a2e48d5100ed3ff614df158a636bca3c6bf9f upstream.\u000a\u000aThe buffer copy functions assumed the caller would ensure\u000acorrect alignment and that the memory to be copied was\u000acompletely within the binder buffer. There have been\u000aa few cases discovered by syzkallar where a malformed\u000atransaction created by a user could violated the\u000aassumptions and resulted in a BUG_ON.\u000a\u000aThe fix is to remove the BUG_ON and always return the\u000aerror to be handled appropriately by the caller.\u000a\u000aAcked-by: Martijn Coenen \u000aReported-by: syzbot+3ae18325f96190606754@syzkaller.appspotmail.com\u000aFixes: bde4a19fc04f (\"binder: use userspace pointer as base of buffer space\")\u000aSuggested-by: Dan Carpenter \u000aSigned-off-by: Todd Kjos \u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "9edfd065a0b85f94ca5f7ea993fe50ad558511a7", "msg" : "binder: return errors from buffer copy functions", "paths" : [ { "editType" : "edit", "file" : "drivers/android/binder.c" }, { "editType" : "edit", "file" : "drivers/android/binder_alloc.h" }, { "editType" : "edit", "file" : "drivers/android/binder_alloc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/iio/adc/stm32-adc-core.c" ], "commitId" : "c1f5ded28df861cb0f61120720a1598abaa94198", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iio: adc: stm32-adc: add missing vdda-supply\u000a\u000acommit 7685010fca2ba0284f31fd1380df3cffc96d847e upstream.\u000a\u000aAdd missing vdda-supply, analog power supply, to STM32 ADC. When vdda is\u000aan independent supply, it needs to be properly turned on or off to supply\u000athe ADC.\u000a\u000aSigned-off-by: Fabrice Gasnier \u000aFixes: 1add69880240 (\"iio: adc: Add support for STM32 ADC core\").\u000aCc: \u000aSigned-off-by: Jonathan Cameron \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "c1f5ded28df861cb0f61120720a1598abaa94198", "msg" : "iio: adc: stm32-adc: add missing vdda-supply", "paths" : [ { "editType" : "edit", "file" : "drivers/iio/adc/stm32-adc-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/carl9170/usb.c" ], "commitId" : "9e0150f694944ce0a60a2a23d8cab8925baeb0a8", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "carl9170: fix misuse of device driver API\u000a\u000acommit feb09b2933275a70917a869989ea2823e7356be8 upstream.\u000a\u000aThis patch follows Alan Stern's recent patch:\u000a\"p54: Fix race between disconnect and firmware loading\"\u000a\u000athat overhauled carl9170 buggy firmware loading and driver\u000aunbinding procedures.\u000a\u000aSince the carl9170 code was adapted from p54 it uses the\u000asame functions and is likely to have the same problem, but\u000ait's just that the syzbot hasn't reproduce them (yet).\u000a\u000aa summary from the changes (copied from the p54 patch):\u000a * Call usb_driver_release_interface() rather than\u000a device_release_driver().\u000a\u000a * Lock udev (the interface's parent) before unbinding the\u000a driver instead of locking udev->parent.\u000a\u000a * During the firmware loading process, take a reference\u000a to the USB interface instead of the USB device.\u000a\u000a * Don't take an unnecessary reference to the device during\u000a probe (and then don't drop it during disconnect).\u000a\u000aand\u000a\u000a * Make sure to prevent use-after-free bugs by explicitly\u000a setting the driver context to NULL after signaling the\u000a completion.\u000a\u000aCc: \u000aCc: Alan Stern \u000aSigned-off-by: Christian Lamparter \u000aAcked-by: Alan Stern \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "9e0150f694944ce0a60a2a23d8cab8925baeb0a8", "msg" : "carl9170: fix misuse of device driver API", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/carl9170/usb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/misc/vmw_vmci/vmci_handle_array.c", "drivers/misc/vmw_vmci/vmci_context.c", "include/linux/vmw_vmci_defs.h", "drivers/misc/vmw_vmci/vmci_handle_array.h" ], "commitId" : "95688f33cb29efe90bb31b61e5d604e60ed35498", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "VMCI: Fix integer overflow in VMCI handle arrays\u000a\u000acommit 1c2eb5b2853c9f513690ba6b71072d8eb65da16a upstream.\u000a\u000aThe VMCI handle array has an integer overflow in\u000avmci_handle_arr_append_entry when it tries to expand the array. This can be\u000atriggered from a guest, since the doorbell link hypercall doesn't impose a\u000alimit on the number of doorbell handles that a VM can create in the\u000ahypervisor, and these handles are stored in a handle array.\u000a\u000aIn this change, we introduce a mandatory max capacity for handle\u000aarrays/lists to avoid excessive memory usage.\u000a\u000aSigned-off-by: Vishnu Dasa \u000aReviewed-by: Adit Ranadive \u000aReviewed-by: Jorgen Hansen \u000aCc: stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "95688f33cb29efe90bb31b61e5d604e60ed35498", "msg" : "VMCI: Fix integer overflow in VMCI handle arrays", "paths" : [ { "editType" : "edit", "file" : "drivers/misc/vmw_vmci/vmci_handle_array.h" }, { "editType" : "edit", "file" : "drivers/misc/vmw_vmci/vmci_context.c" }, { "editType" : "edit", "file" : "include/linux/vmw_vmci_defs.h" }, { "editType" : "edit", "file" : "drivers/misc/vmw_vmci/vmci_handle_array.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c" ], "commitId" : "d04bcbb048755e423fcd0dbc239657cac6dfa11e", "timestamp" : 1563084591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: vchiq_2835_arm: revert \"quit using custom down_interruptible()\"\u000a\u000acommit 061ca1401f96c254e7f179bf97a1fc5c7f47e1e1 upstream.\u000a\u000aThe killable version of down() is meant to be used on situations where\u000ait should not fail at all costs, but still have the convenience of being\u000aable to kill it if really necessary. VCHIQ doesn't fit this criteria, as\u000ait's mainly used as an interface to V4L2 and ALSA devices.\u000a\u000aFixes: ff5979ad8636 (\"staging: vchiq_2835_arm: quit using custom down_interruptible()\")\u000aSigned-off-by: Nicolas Saenz Julienne \u000aAcked-by: Stefan Wahren \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:51 +0200", "id" : "d04bcbb048755e423fcd0dbc239657cac6dfa11e", "msg" : "staging: vchiq_2835_arm: revert \"quit using custom down_interruptible()\"", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c", "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_util.c", "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c" ], "commitId" : "de8bc7030aa0faa5b23000cb8f59805acdf774f3", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: vchiq: revert \"switch to wait_for_completion_killable\"\u000a\u000acommit 086efbabdc04563268372aaef4d66039d85ee76c upstream.\u000a\u000aThe killable version of wait_for_completion() is meant to be used on\u000asituations where it should not fail at all costs, but still have the\u000aconvenience of being able to kill it if really necessary. VCHIQ doesn't\u000afit this criteria, as it's mainly used as an interface to V4L2 and ALSA\u000adevices.\u000a\u000aFixes: a772f116702e (\"staging: vchiq: switch to wait_for_completion_killable\")\u000aSigned-off-by: Nicolas Saenz Julienne \u000aAcked-by: Stefan Wahren \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "de8bc7030aa0faa5b23000cb8f59805acdf774f3", "msg" : "staging: vchiq: revert \"switch to wait_for_completion_killable\"", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c" }, { "editType" : "edit", "file" : "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c" }, { "editType" : "edit", "file" : "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_util.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c" ], "commitId" : "5e8051fc13f9f73d58b352cf51e663a4e31689a7", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: vchiq: make wait events interruptible\u000a\u000acommit 77cf3f5dcf35c8f547f075213dbc15146d44cc76 upstream.\u000a\u000aThe killable version of wait_event() is meant to be used on situations\u000awhere it should not fail at all costs, but still have the convenience of\u000abeing able to kill it if really necessary. Wait events in VCHIQ doesn't\u000afit this criteria, as it's mainly used as an interface to V4L2 and ALSA\u000adevices.\u000a\u000aFixes: 852b2876a8a8 (\"staging: vchiq: rework remove_event handling\")\u000aSigned-off-by: Nicolas Saenz Julienne \u000aAcked-by: Stefan Wahren \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "5e8051fc13f9f73d58b352cf51e663a4e31689a7", "msg" : "staging: vchiq: make wait events interruptible", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/fsl-dpaa2/ethsw/ethsw.c" ], "commitId" : "4279f7b8e64de3690824b00047c1266390eff7f0", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: fsl-dpaa2/ethsw: fix memory leak of switchdev_work\u000a\u000acommit 5555ebbbac822b4fa28db2be15aaf98b3c21af26 upstream.\u000a\u000aIn the default event case switchdev_work is being leaked because\u000anothing is queued for work. Fix this by kfree'ing switchdev_work\u000abefore returning NOTIFY_DONE.\u000a\u000aAddresses-Coverity: (\"Resource leak\")\u000aFixes: 44baaa43d7cc (\"staging: fsl-dpaa2/ethsw: Add Freescale DPAA2 Ethernet Switch driver\")\u000aSigned-off-by: Colin Ian King \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "4279f7b8e64de3690824b00047c1266390eff7f0", "msg" : "staging: fsl-dpaa2/ethsw: fix memory leak of switchdev_work", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/fsl-dpaa2/ethsw/ethsw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c" ], "commitId" : "a305bc4d819f9f2bc38d05707ae0f432789cc0dd", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: bcm2835-camera: Replace spinlock protecting context_map with mutex\u000a\u000acommit 8dedab2903f152aa3cee9ae3d57c828dea0d356e upstream.\u000a\u000aThe commit \"staging: bcm2835-camera: Replace open-coded idr with a struct idr.\"\u000areplaced an internal implementation of an idr with the standard functions\u000aand a spinlock. idr_alloc(GFP_KERNEL) can sleep whilst calling kmem_cache_alloc\u000ato allocate the new node, but this is not valid whilst in an atomic context\u000adue to the spinlock.\u000a\u000aThere is no need for this to be a spinlock as a standard mutex is\u000asufficient.\u000a\u000aFixes: 950fd867c635 (\"staging: bcm2835-camera: Replace open-coded idr with a struct idr.\")\u000aSigned-off-by: Dave Stevenson \u000aSigned-off-by: Stefan Wahren \u000aAcked-by: Hans Verkuil \u000aAcked-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "a305bc4d819f9f2bc38d05707ae0f432789cc0dd", "msg" : "staging: bcm2835-camera: Replace spinlock protecting context_map with mutex", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c", "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.h", "drivers/staging/vc04_services/bcm2835-camera/bcm2835-camera.c" ], "commitId" : "8ba36aeb132e2728e060caa9422eef29957d88c5", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: bcm2835-camera: Ensure all buffers are returned on disable\u000a\u000acommit 70ec64ccdaac5d8f634338e33b016c1c99831499 upstream.\u000a\u000aWith the recent change to match MMAL and V4L2 buffers there\u000ais a need to wait for all MMAL buffers to be returned during\u000astop_streaming.\u000a\u000aFixes: 938416707071 (\"staging: bcm2835-camera: Remove V4L2/MMAL buffer remapping\")\u000aSigned-off-by: Dave Stevenson \u000aSigned-off-by: Stefan Wahren \u000aAcked-by: Hans Verkuil \u000aAcked-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "8ba36aeb132e2728e060caa9422eef29957d88c5", "msg" : "staging: bcm2835-camera: Ensure all buffers are returned on disable", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c" }, { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/bcm2835-camera.c" }, { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c" ], "commitId" : "bd1bf4d948af4c4374684e11b2a4fe6e5b73b62a", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: bcm2835-camera: Remove check of the number of buffers supplied\u000a\u000acommit bb8e97006d701ae725a177f8f322e5a75fa761b7 upstream.\u000a\u000aBefore commit \"staging: bcm2835-camera: Remove V4L2/MMAL buffer remapping\"\u000athere was a need to ensure that there were sufficient buffers supplied from\u000athe user to cover those being sent to the VPU (always 1).\u000a\u000aNow the buffers are linked 1:1 between MMAL and V4L2,\u000atherefore there is no need for that check, and indeed it is wrong\u000aas there is no need to submit all the buffers before starting streaming.\u000a\u000aFixes: 938416707071 (\"staging: bcm2835-camera: Remove V4L2/MMAL buffer remapping\")\u000aSigned-off-by: Dave Stevenson \u000aSigned-off-by: Stefan Wahren \u000aAcked-by: Hans Verkuil \u000aAcked-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "bd1bf4d948af4c4374684e11b2a4fe6e5b73b62a", "msg" : "staging: bcm2835-camera: Remove check of the number of buffers supplied", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c", "drivers/staging/vc04_services/bcm2835-camera/bcm2835-camera.c" ], "commitId" : "491a82beeded104572795e04e981d54a3c36464f", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: bcm2835-camera: Handle empty EOS buffers whilst streaming\u000a\u000acommit a26be06d6d96c10a9ab005e99d93fbb5d3babd98 upstream.\u000a\u000aThe change to mapping V4L2 to MMAL buffers 1:1 didn't handle\u000athe condition we get with raw pixel buffers (eg YUV and RGB)\u000adirect from the camera's stills port. That sends the pixel buffer\u000aand then an empty buffer with the EOS flag set. The EOS buffer\u000awasn't handled and returned an error up the stack.\u000a\u000aHandle the condition correctly by returning it to the component\u000aif streaming, or returning with an error if stopping streaming.\u000a\u000aFixes: 938416707071 (\"staging: bcm2835-camera: Remove V4L2/MMAL buffer remapping\")\u000aSigned-off-by: Dave Stevenson \u000aSigned-off-by: Stefan Wahren \u000aAcked-by: Hans Verkuil \u000aAcked-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "491a82beeded104572795e04e981d54a3c36464f", "msg" : "staging: bcm2835-camera: Handle empty EOS buffers whilst streaming", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c" }, { "editType" : "edit", "file" : "drivers/staging/vc04_services/bcm2835-camera/bcm2835-camera.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/rtl8712/rtl871x_ioctl_linux.c" ], "commitId" : "5dd8f535cbba31da584e8561f32f2656fc0190c5", "timestamp" : 1563084592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "staging: rtl8712: reduce stack usage, again\u000a\u000acommit fbd6b25009ac76b2034168cd21d5e01f8c2d83d1 upstream.\u000a\u000aAn earlier patch I sent reduced the stack usage enough to get\u000abelow the warning limit, and I could show this was safe, but with\u000aGCC_PLUGIN_STRUCTLEAK_BYREF_ALL, it gets worse again because large stack\u000avariables in the same function no longer overlap:\u000a\u000adrivers/staging/rtl8712/rtl871x_ioctl_linux.c: In function 'translate_scan.isra.2':\u000adrivers/staging/rtl8712/rtl871x_ioctl_linux.c:322:1: error: the frame size of 1200 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]\u000a\u000aSplit out the largest two blocks in the affected function into two\u000aseparate functions and mark those noinline_for_stack.\u000a\u000aFixes: 8c5af16f7953 (\"staging: rtl8712: reduce stack usage\")\u000aFixes: 81a56f6dcd20 (\"gcc-plugins: structleak: Generalize to all variable types\")\u000aSigned-off-by: Arnd Bergmann \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-14 08:09:52 +0200", "id" : "5dd8f535cbba31da584e8561f32f2656fc0190c5", "msg" : "staging: rtl8712: reduce stack usage, again", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/rtl8712/rtl871x_ioctl_linux.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Makefile" ], "commitId" : "22bc18377bd45c060733e1ed09f34b769e4b4bef", "timestamp" : 1563084593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Linux 5.1.18\u000a", "date" : "2019-07-14 08:09:53 +0200", "id" : "22bc18377bd45c060733e1ed09f34b769e4b4bef", "msg" : "Linux 5.1.18", "paths" : [ { "editType" : "edit", "file" : "Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/e1000e/netdev.c" ], "commitId" : "f8449ec9be283b9803e4b356445390fd1ed08e68", "timestamp" : 1563692511000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Revert \"e1000e: fix cyclic resets at link up with active tx\"\u000a\u000acommit caff422ea81e144842bc44bab408d85ac449377b upstream.\u000a\u000aThis reverts commit 0f9e980bf5ee1a97e2e401c846b2af989eb21c61.\u000a\u000aThat change cased false-positive warning about hardware hang:\u000a\u000ae1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx\u000aIPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready\u000ae1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:\u000a TDH <0>\u000a TDT <1>\u000a next_to_use <1>\u000a next_to_clean <0>\u000abuffer_info[next_to_clean]:\u000a time_stamp \u000a next_to_watch <0>\u000a jiffies \u000a next_to_watch.status <0>\u000aMAC Status <40080080>\u000aPHY Status <7949>\u000aPHY 1000BASE-T Status <0>\u000aPHY Extended Status <3000>\u000aPCI Status <10>\u000ae1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx\u000a\u000aBesides warning everything works fine.\u000aOriginal issue will be fixed property in following patch.\u000a\u000aSigned-off-by: Konstantin Khlebnikov \u000aReported-by: Joseph Yasi \u000aLink: https://bugzilla.kernel.org/show_bug.cgi?id=203175\u000aTested-by: Joseph Yasi \u000aTested-by: Aaron Brown \u000aTested-by: Oleksandr Natalenko \u000aSigned-off-by: Jeff Kirsher \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:01:51 +0200", "id" : "f8449ec9be283b9803e4b356445390fd1ed08e68", "msg" : "Revert \"e1000e: fix cyclic resets at link up with active tx\"", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/e1000e/netdev.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/e1000e/netdev.c" ], "commitId" : "90b9d474043f58ec469c6f9343c0883abff11f2b", "timestamp" : 1563692511000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "e1000e: start network tx queue only when link is up\u000a\u000acommit d17ba0f616a08f597d9348c372d89b8c0405ccf3 upstream.\u000a\u000aDriver does not want to keep packets in Tx queue when link is lost.\u000aBut present code only reset NIC to flush them, but does not prevent\u000aqueuing new packets. Moreover reset sequence itself could generate\u000anew packets via netconsole and NIC falls into endless reset loop.\u000a\u000aThis patch wakes Tx queue only when NIC is ready to send packets.\u000a\u000aThis is proper fix for problem addressed by commit 0f9e980bf5ee\u000a(\"e1000e: fix cyclic resets at link up with active tx\").\u000a\u000aSigned-off-by: Konstantin Khlebnikov \u000aSuggested-by: Alexander Duyck \u000aTested-by: Joseph Yasi \u000aTested-by: Aaron Brown \u000aTested-by: Oleksandr Natalenko \u000aSigned-off-by: Jeff Kirsher \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:01:51 +0200", "id" : "90b9d474043f58ec469c6f9343c0883abff11f2b", "msg" : "e1000e: start network tx queue only when link is up", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/e1000e/netdev.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/mouse/synaptics.c" ], "commitId" : "662ec5a3689684ed90978622f0b1a2bb6a32ad5d", "timestamp" : 1563692511000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: synaptics - enable SMBUS on T480 thinkpad trackpad\u000a\u000acommit abbe3acd7d72ab4633ade6bd24e8306b67e0add3 upstream.\u000a\u000aThinkpad t480 laptops had some touchpad features disabled, resulting in the\u000aloss of pinch to activities in GNOME, on wayland, and other touch gestures\u000abeing slower. This patch adds the touchpad of the t480 to the smbus_pnp_ids\u000awhitelist to enable the extra features. In my testing this does not break\u000asuspend (on fedora, with wayland, and GNOME, using the rc-6 kernel), while\u000aalso fixing the feature on a T480.\u000a\u000aSigned-off-by: Cole Rogers \u000aAcked-by: Benjamin Tissoires \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:01:51 +0200", "id" : "662ec5a3689684ed90978622f0b1a2bb6a32ad5d", "msg" : "Input: synaptics - enable SMBUS on T480 thinkpad trackpad", "paths" : [ { "editType" : "edit", "file" : "drivers/input/mouse/synaptics.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/uapi/linux/nilfs2_ondisk.h" ], "commitId" : "0b6539699f4ea42bb5901fa5d3b0c61b0424c11a", "timestamp" : 1563692512000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header\u000a\u000acommit c32cc30c0544f13982ee0185d55f4910319b1a79 upstream.\u000a\u000acpu_to_le32/le32_to_cpu is defined in include/linux/byteorder/generic.h,\u000awhich is not exported to user-space.\u000a\u000aUAPI headers must use the ones prefixed with double-underscore.\u000a\u000aDetected by compile-testing exported headers:\u000a\u000a include/linux/nilfs2_ondisk.h: In function `nilfs_checkpoint_set_snapshot':\u000a include/linux/nilfs2_ondisk.h:536:17: error: implicit declaration of function `cpu_to_le32' [-Werror=implicit-function-declaration]\u000a cp->cp_flags = cpu_to_le32(le32_to_cpu(cp->cp_flags) | \\\u000a ^\u000a include/linux/nilfs2_ondisk.h:552:1: note: in expansion of macro `NILFS_CHECKPOINT_FNS'\u000a NILFS_CHECKPOINT_FNS(SNAPSHOT, snapshot)\u000a ^~~~~~~~~~~~~~~~~~~~\u000a include/linux/nilfs2_ondisk.h:536:29: error: implicit declaration of function `le32_to_cpu' [-Werror=implicit-function-declaration]\u000a cp->cp_flags = cpu_to_le32(le32_to_cpu(cp->cp_flags) | \\\u000a ^\u000a include/linux/nilfs2_ondisk.h:552:1: note: in expansion of macro `NILFS_CHECKPOINT_FNS'\u000a NILFS_CHECKPOINT_FNS(SNAPSHOT, snapshot)\u000a ^~~~~~~~~~~~~~~~~~~~\u000a include/linux/nilfs2_ondisk.h: In function `nilfs_segment_usage_set_clean':\u000a include/linux/nilfs2_ondisk.h:622:19: error: implicit declaration of function `cpu_to_le64' [-Werror=implicit-function-declaration]\u000a su->su_lastmod = cpu_to_le64(0);\u000a ^~~~~~~~~~~\u000a\u000aLink: http://lkml.kernel.org/r/20190605053006.14332-1-yamada.masahiro@socionext.com\u000aFixes: e63e88bc53ba (\"nilfs2: move ioctl interface and disk layout to uapi separately\")\u000aSigned-off-by: Masahiro Yamada \u000aAcked-by: Ryusuke Konishi \u000aCc: Arnd Bergmann \u000aCc: Greg KH \u000aCc: Joe Perches \u000aCc: \u0009[4.9+]\u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:01:52 +0200", "id" : "0b6539699f4ea42bb5901fa5d3b0c61b0424c11a", "msg" : "nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header", "paths" : [ { "editType" : "edit", "file" : "include/uapi/linux/nilfs2_ondisk.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/cpuhotplug.h", "drivers/base/cacheinfo.c" ], "commitId" : "2d08e0972ed77b00bf62b3173e60f1fd255cd8ae", "timestamp" : 1563692512000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT\u000a\u000acommit 83b44fe343b5abfcb1b2261289bd0cfcfcfd60a8 upstream.\u000a\u000aThe cacheinfo structures are alloced/freed by cpu online/offline\u000acallbacks. Originally these were only used by sysfs to expose the\u000acache topology to user space. Without any in-kernel dependencies\u000aCPUHP_AP_ONLINE_DYN was an appropriate choice.\u000a\u000aresctrl has started using these structures to identify CPUs that\u000ashare a cache. It updates its 'domain' structures from cpu\u000aonline/offline callbacks. These depend on the cacheinfo structures\u000a(resctrl_online_cpu()->domain_add_cpu()->get_cache_id()->\u000a get_cpu_cacheinfo()).\u000aThese also run as CPUHP_AP_ONLINE_DYN.\u000a\u000aNow that there is an in-kernel dependency, move the cacheinfo\u000awork earlier so we know its done before resctrl's CPUHP_AP_ONLINE_DYN\u000awork runs.\u000a\u000aFixes: 2264d9c74dda1 (\"x86/intel_rdt: Build structures for each resource based on cache topology\")\u000aCc: \u000aCc: Fenghua Yu \u000aCc: Reinette Chatre \u000aSigned-off-by: James Morse \u000aLink: https://lore.kernel.org/r/20190624173656.202407-1-james.morse@arm.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:01:52 +0200", "id" : "2d08e0972ed77b00bf62b3173e60f1fd255cd8ae", "msg" : "drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT", "paths" : [ { "editType" : "edit", "file" : "include/linux/cpuhotplug.h" }, { "editType" : "edit", "file" : "drivers/base/cacheinfo.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/base/firmware_loader/fallback.c" ], "commitId" : "f42cde4aa63d0bdb9a54c7d36cedf4c0fc5d8843", "timestamp" : 1563692512000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "firmware: improve LSM/IMA security behaviour\u000a\u000acommit 2472d64af2d3561954e2f05365a67692bb852f2a upstream.\u000a\u000aThe firmware loader queries if LSM/IMA permits it to load firmware\u000avia the sysfs fallback. Unfortunately, the code does the opposite:\u000ait expressly permits sysfs fw loading if security_kernel_load_data(\u000aLOADING_FIRMWARE) returns -EACCES. This happens because a\u000azero-on-success return value is cast to a bool that's true on success.\u000a\u000aFix the return value handling so we get the correct behaviour.\u000a\u000aFixes: 6e852651f28e (\"firmware: add call to LSM hook before firmware sysfs fallback\")\u000aCc: Stable \u000aCc: Mimi Zohar \u000aCc: Kees Cook \u000aTo: Luis Chamberlain \u000aCc: Greg Kroah-Hartman \u000aCc: \"Rafael J. Wysocki\" \u000aCc: linux-kernel@vger.kernel.org\u000aSigned-off-by: Sven Van Asbroeck \u000aReviewed-by: Mimi Zohar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:01:52 +0200", "id" : "f42cde4aa63d0bdb9a54c7d36cedf4c0fc5d8843", "msg" : "firmware: improve LSM/IMA security behaviour", "paths" : [ { "editType" : "edit", "file" : "drivers/base/firmware_loader/fallback.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/meson8.dtsi" ], "commitId" : "eb1cf49961a4d38e8098daecfc2be6589e955ef2", "timestamp" : 1563692513000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: meson8: fix GPU interrupts and drop an undocumented property\u000a\u000a[ Upstream commit 01dfdd7b4693496854ac92d1ebfb18d7b108f777 ]\u000a\u000aThe interrupts in Amlogic's vendor kernel sources are all contiguous.\u000aThere are two typos leading to pp2 and pp4 as well as ppmmu2 and ppmmu4\u000aincorrectly sharing the same interrupt line.\u000aFix this by using interrupt 170 for pp2 and 171 for ppmmu2.\u000a\u000aAlso drop the undocumented \"switch-delay\" which is a left-over from my\u000aexperiments with an early lima kernel driver when it was still\u000aout-of-tree and required this property on Amlogic SoCs.\u000a\u000aFixes: 7d3f6b536e72c9 (\"ARM: dts: meson8: add the Mali-450 MP6 GPU\")\u000aSigned-off-by: Martin Blumenstingl \u000aSigned-off-by: Kevin Hilman \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:53 +0200", "id" : "eb1cf49961a4d38e8098daecfc2be6589e955ef2", "msg" : "ARM: dts: meson8: fix GPU interrupts and drop an undocumented property", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/meson8.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/meson8b.dtsi" ], "commitId" : "f71b47b37e29099fbf968a48dbbd1bfd99d42bec", "timestamp" : 1563692513000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: meson8b: fix the operating voltage of the Mali GPU\u000a\u000a[ Upstream commit 26d65140e92a626e39c73c9abf769fd174bf5076 ]\u000a\u000aAmlogic's vendor kernel defines an OPP for the GPU on Meson8b boards\u000awith a voltage of 1.15V. It turns out that the vendor kernel relies on\u000athe bootloader to set up the voltage. The bootloader however sets a\u000afixed voltage of 1.10V.\u000a\u000aAmlogic's patched u-boot sources (uboot-2015-01-15-23a3562521) confirm\u000athis:\u000a$ grep -oiE \"VDD(EE|AO)_VOLTAGE[ ]+[0-9]+\" board/amlogic/configs/m8b_*\u000a board/amlogic/configs/m8b_m100_v1.h:VDDAO_VOLTAGE 1100\u000a board/amlogic/configs/m8b_m101_v1.h:VDDAO_VOLTAGE 1100\u000a board/amlogic/configs/m8b_m102_v1.h:VDDAO_VOLTAGE 1100\u000a board/amlogic/configs/m8b_m200_v1.h:VDDAO_VOLTAGE 1100\u000a board/amlogic/configs/m8b_m201_v1.h:VDDEE_VOLTAGE 1100\u000a board/amlogic/configs/m8b_m201_v1.h:VDDEE_VOLTAGE 1100\u000a board/amlogic/configs/m8b_m202_v1.h:VDDEE_VOLTAGE 1100\u000a\u000aAnother hint at this is the VDDEE voltage on the EC-100 and Odroid-C1\u000aboards. The VDDEE regulator supplies the Mali GPU. It's basically a copy\u000aof the VCCK (CPU supply) which means it's limited to 0.86V to 1.14V.\u000a\u000aUpdate the operating voltage of the Mali GPU on Meson8b to 1.10V so it\u000amatches with what the vendor u-boot sets.\u000a\u000aFixes: c3ea80b6138cae (\"ARM: dts: meson8b: add the Mali-450 MP2 GPU\")\u000aSigned-off-by: Martin Blumenstingl \u000aSigned-off-by: Kevin Hilman \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:53 +0200", "id" : "f71b47b37e29099fbf968a48dbbd1bfd99d42bec", "msg" : "ARM: dts: meson8b: fix the operating voltage of the Mali GPU", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/meson8b.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/irqchip/irq-csky-mpintc.c" ], "commitId" : "97b1f5aa15bde870943a87e394c5c2753b836dbc", "timestamp" : 1563692513000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "irqchip/irq-csky-mpintc: Support auto irq deliver to all cpus\u000a\u000a[ Upstream commit db56c5128e6625cb16efc4910b60627e46f608e3 ]\u000a\u000aThe csky,mpintc could deliver a external irq to one cpu or all cpus, but\u000ait couldn't deliver a external irq to a group of cpus with cpu_mask. So\u000awe only use auto deliver mode when affinity mask_val is equal to\u000acpu_present_mask.\u000a\u000aThere is no limitation for only two cpus in SMP system.\u000a\u000aSigned-off-by: Guo Ren \u000aCc: Marc Zyngier \u000aSigned-off-by: Marc Zyngier \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:53 +0200", "id" : "97b1f5aa15bde870943a87e394c5c2753b836dbc", "msg" : "irqchip/irq-csky-mpintc: Support auto irq deliver to all cpus", "paths" : [ { "editType" : "edit", "file" : "drivers/irqchip/irq-csky-mpintc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/irqchip/irq-gic-v3-its.c" ], "commitId" : "e8f05b163958982af2e3a0b1cc6477d4c3bc904f", "timestamp" : 1563692513000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "irqchip/gic-v3-its: Fix command queue pointer comparison bug\u000a\u000a[ Upstream commit a050fa5476d418fc16b25abe168b3d38ba11e13c ]\u000a\u000aWhen we run several VMs with PCI passthrough and GICv4 enabled, not\u000apinning vCPUs, we will occasionally see below warnings in dmesg:\u000a\u000aITS queue timeout (65440 65504 480)\u000aITS cmd its_build_vmovp_cmd failed\u000a\u000aThe reason for the above issue is that in BUILD_SINGLE_CMD_FUNC:\u000a1. Post the write command.\u000a2. Release the lock.\u000a3. Start to read GITS_CREADR to get the reader pointer.\u000a4. Compare the reader pointer to the target pointer.\u000a5. If reader pointer does not reach the target, sleep 1us and continue\u000ato try.\u000a\u000aIf we have several processors running the above concurrently, other\u000aCPUs will post write commands while the 1st CPU is waiting the\u000acompletion. So we may have below issue:\u000a\u000aphase 1:\u000a---rd_idx-----from_idx-----to_idx--0---------\u000a\u000await 1us:\u000a\u000aphase 2:\u000a--------------from_idx-----to_idx--0-rd_idx--\u000a\u000aThat is the rd_idx may fly ahead of to_idx, and if in case to_idx is\u000anear the wrap point, rd_idx will wrap around. So the below condition\u000awill not be met even after 1s:\u000a\u000aif (from_idx < to_idx && rd_idx >= to_idx)\u000a\u000aThere is another theoretical issue. For a slow and busy ITS, the\u000ainitial rd_idx may fall behind from_idx a lot, just as below:\u000a\u000a---rd_idx---0--from_idx-----to_idx-----------\u000a\u000aThis will cause the wait function exit too early.\u000a\u000aActually, it does not make much sense to use from_idx to judge if\u000ato_idx is wrapped, but we need a initial rd_idx when lock is still\u000aacquired, and it can be used to judge whether to_idx is wrapped and\u000athe current rd_idx is wrapped.\u000a\u000aWe switch to a method of calculating the delta of two adjacent reads\u000aand accumulating it to get the sum, so that we can get the real rd_idx\u000afrom the wrapped value even when the queue is almost full.\u000a\u000aCc: Thomas Gleixner \u000aCc: Jason Cooper \u000aSigned-off-by: Heyi Guo \u000aSigned-off-by: Marc Zyngier \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:53 +0200", "id" : "e8f05b163958982af2e3a0b1cc6477d4c3bc904f", "msg" : "irqchip/gic-v3-its: Fix command queue pointer comparison bug", "paths" : [ { "editType" : "edit", "file" : "drivers/irqchip/irq-gic-v3-its.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/clk/ti/clkctrl.c" ], "commitId" : "bfa9a4107def2aec5658cf66f160cc9aac32dfbe", "timestamp" : 1563692514000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "clk: ti: clkctrl: Fix returning uninitialized data\u000a\u000a[ Upstream commit 41b3588dba6ef4b7995735a97e47ff0aeea6c276 ]\u000a\u000aIf we do a clk_get() for a clock that does not exists, we have\u000a_ti_omap4_clkctrl_xlate() return uninitialized data if no match\u000ais found. This can be seen in some cases with SLAB_DEBUG enabled:\u000a\u000aUnable to handle kernel paging request at virtual address 5a5a5a5a\u000a...\u000aclk_hw_create_clk.part.33\u000asysc_notifier_call\u000anotifier_call_chain\u000ablocking_notifier_call_chain\u000adevice_add\u000a\u000aLet's fix this by setting a found flag only when we find a match.\u000a\u000aReported-by: Tomi Valkeinen \u000aFixes: 88a172526c32 (\"clk: ti: add support for clkctrl clocks\")\u000aSigned-off-by: Tony Lindgren \u000aTested-by: Peter Ujfalusi \u000aTested-by: Tomi Valkeinen \u000aSigned-off-by: Stephen Boyd \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:54 +0200", "id" : "bfa9a4107def2aec5658cf66f160cc9aac32dfbe", "msg" : "clk: ti: clkctrl: Fix returning uninitialized data", "paths" : [ { "editType" : "edit", "file" : "drivers/clk/ti/clkctrl.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/firmware/efi/efi-bgrt.c" ], "commitId" : "2f93e24e365781a4882532f9fb6eb7322aa1e331", "timestamp" : 1563692514000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "efi/bgrt: Drop BGRT status field reserved bits check\u000a\u000a[ Upstream commit a483fcab38b43fb34a7f12ab1daadd3907f150e2 ]\u000a\u000aStarting with ACPI 6.2 bits 1 and 2 of the BGRT status field are no longer\u000areserved. These bits are now used to indicate if the image needs to be\u000arotated before being displayed.\u000a\u000aThe first device using these bits has now shown up (the GPD MicroPC) and\u000athe reserved bits check causes us to reject the valid BGRT table on this\u000adevice.\u000a\u000aRather then changing the reserved bits check, allowing only the 2 new bits,\u000ainstead just completely remove it so that we do not end up with a similar\u000aproblem when more bits are added in the future.\u000a\u000aSigned-off-by: Hans de Goede \u000aSigned-off-by: Ard Biesheuvel \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:54 +0200", "id" : "2f93e24e365781a4882532f9fb6eb7322aa1e331", "msg" : "efi/bgrt: Drop BGRT status field reserved bits check", "paths" : [ { "editType" : "edit", "file" : "drivers/firmware/efi/efi-bgrt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi" ], "commitId" : "6cb7e771924af3f970a21ee06ffabf0dbe3ef92d", "timestamp" : 1563692514000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: dts: ls1028a: Fix CPU idle fail.\u000a\u000a[ Upstream commit 53f2ac9d3aa881ed419054076042898b77c27ee4 ]\u000a\u000aPSCI spec define 1st parameter's bit 16 of function CPU_SUSPEND to\u000aindicate CPU State Type: 0 for standby, 1 for power down. In this\u000acase, we want to select standby for CPU idle feature. But current\u000asetting wrongly select power down and cause CPU SUSPEND fail every\u000atime. Need this fix.\u000a\u000aFixes: 8897f3255c9c (\"arm64: dts: Add support for NXP LS1028A SoC\")\u000aSigned-off-by: Ran Wang \u000aSigned-off-by: Shawn Guo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:54 +0200", "id" : "6cb7e771924af3f970a21ee06ffabf0dbe3ef92d", "msg" : "arm64: dts: ls1028a: Fix CPU idle fail.", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/testing/selftests/powerpc/mm/.gitignore", "tools/testing/selftests/powerpc/mm/large_vm_fork_separation.c", "tools/testing/selftests/powerpc/mm/Makefile" ], "commitId" : "6f2030f88188cf909b2c3d31707800c92627d8d9", "timestamp" : 1563692515000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "selftests/powerpc: Add test of fork with mapping above 512TB\u000a\u000a[ Upstream commit 16391bfc862342f285195013b73c1394fab28b97 ]\u000a\u000aThis tests that when a process with a mapping above 512TB forks we\u000acorrectly separate the parent and child address spaces. This exercises\u000athe bug in the context id handling fixed in the previous commit.\u000a\u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:55 +0200", "id" : "6f2030f88188cf909b2c3d31707800c92627d8d9", "msg" : "selftests/powerpc: Add test of fork with mapping above 512TB", "paths" : [ { "editType" : "edit", "file" : "tools/testing/selftests/powerpc/mm/.gitignore" }, { "editType" : "edit", "file" : "tools/testing/selftests/powerpc/mm/Makefile" }, { "editType" : "add", "file" : "tools/testing/selftests/powerpc/mm/large_vm_fork_separation.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/events/core.c" ], "commitId" : "69f295c5fc2476c5fb92c0f422a26acb51611b2e", "timestamp" : 1563692515000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/core: Fix perf_sample_regs_user() mm check\u000a\u000a[ Upstream commit 085ebfe937d7a7a5df1729f35a12d6d655fea68c ]\u000a\u000aperf_sample_regs_user() uses 'current->mm' to test for the presence of\u000auserspace, but this is insufficient, consider use_mm().\u000a\u000aA better test is: '!(current->flags & PF_KTHREAD)', exec() clears\u000aPF_KTHREAD after it sets the new ->mm but before it drops to userspace\u000afor the first time.\u000a\u000aPossibly obsoletes: bf05fc25f268 (\"powerpc/perf: Fix oops when kthread execs user process\")\u000a\u000aReported-by: Ravi Bangoria \u000aReported-by: Young Xiao <92siuyang@gmail.com>\u000aSigned-off-by: Peter Zijlstra (Intel) \u000aAcked-by: Will Deacon \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Frederic Weisbecker \u000aCc: Jiri Olsa \u000aCc: Linus Torvalds \u000aCc: Michael Ellerman \u000aCc: Naveen N. Rao \u000aCc: Peter Zijlstra \u000aCc: Stephane Eranian \u000aCc: Thomas Gleixner \u000aFixes: 4018994f3d87 (\"perf: Add ability to attach user level registers dump to sample\")\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:55 +0200", "id" : "69f295c5fc2476c5fb92c0f422a26acb51611b2e", "msg" : "perf/core: Fix perf_sample_regs_user() mm check", "paths" : [ { "editType" : "edit", "file" : "kernel/events/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/gemini-dlink-dns-313.dts" ], "commitId" : "5ac287b813982a90479a4e3a9fd2a9ff023807d3", "timestamp" : 1563692515000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: gemini Fix up DNS-313 compatible string\u000a\u000a[ Upstream commit 36558020128b1a48b7bddd5792ee70e3f64b04b0 ]\u000a\u000aIt's a simple typo in the DNS file, which was pretty serious.\u000aNo scripts were working properly. Fix it up.\u000a\u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:55 +0200", "id" : "5ac287b813982a90479a4e3a9fd2a9ff023807d3", "msg" : "ARM: dts: gemini Fix up DNS-313 compatible string", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/gemini-dlink-dns-313.dts" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/mach-omap2/prm3xxx.c" ], "commitId" : "ae795e3f53c6fb84d60af5cda92fc693d4b983d3", "timestamp" : 1563692515000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: omap2: remove incorrect __init annotation\u000a\u000a[ Upstream commit 27e23d8975270df6999f8b5b3156fc0c04927451 ]\u000a\u000aomap3xxx_prm_enable_io_wakeup() is marked __init, but its caller is not, so\u000awe get a warning with clang-8:\u000a\u000aWARNING: vmlinux.o(.text+0x343c8): Section mismatch in reference from the function omap3xxx_prm_late_init() to the function .init.text:omap3xxx_prm_enable_io_wakeup()\u000aThe function omap3xxx_prm_late_init() references\u000athe function __init omap3xxx_prm_enable_io_wakeup().\u000aThis is often because omap3xxx_prm_late_init lacks a __init\u000aannotation or the annotation of omap3xxx_prm_enable_io_wakeup is wrong.\u000a\u000aWhen building with gcc, omap3xxx_prm_enable_io_wakeup() is always\u000ainlined, so we never noticed in the past.\u000a\u000aSigned-off-by: Arnd Bergmann \u000aReviewed-by: Nathan Chancellor \u000aAcked-by: Tony Lindgren \u000aReviewed-by: Andrew Murray \u000aSigned-off-by: Olof Johansson \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:55 +0200", "id" : "ae795e3f53c6fb84d60af5cda92fc693d4b983d3", "msg" : "ARM: omap2: remove incorrect __init annotation", "paths" : [ { "editType" : "edit", "file" : "arch/arm/mach-omap2/prm3xxx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/afs/volume.c", "fs/afs/internal.h", "fs/afs/callback.c" ], "commitId" : "7b0ef1ba26048ac3ca00408c6d689a717e65cf58", "timestamp" : 1563692516000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "afs: Fix uninitialised spinlock afs_volume::cb_break_lock\u000a\u000a[ Upstream commit 90fa9b64523a645a97edc0bdcf2d74759957eeee ]\u000a\u000aFix the cb_break_lock spinlock in afs_volume struct by initialising it when\u000athe volume record is allocated.\u000a\u000aAlso rename the lock to cb_v_break_lock to distinguish it from the lock of\u000athe same name in the afs_server struct.\u000a\u000aWithout this, the following trace may be observed when a volume-break\u000acallback is received:\u000a\u000a INFO: trying to register non-static key.\u000a the code is fine but needs lockdep annotation.\u000a turning off the locking correctness validator.\u000a CPU: 2 PID: 50 Comm: kworker/2:1 Not tainted 5.2.0-rc1-fscache+ #3045\u000a Hardware name: ASUS All Series/H97-PLUS, BIOS 2306 10/09/2014\u000a Workqueue: afs SRXAFSCB_CallBack\u000a Call Trace:\u000a dump_stack+0x67/0x8e\u000a register_lock_class+0x23b/0x421\u000a ? check_usage_forwards+0x13c/0x13c\u000a __lock_acquire+0x89/0xf73\u000a lock_acquire+0x13b/0x166\u000a ? afs_break_callbacks+0x1b2/0x3dd\u000a _raw_write_lock+0x2c/0x36\u000a ? afs_break_callbacks+0x1b2/0x3dd\u000a afs_break_callbacks+0x1b2/0x3dd\u000a ? trace_event_raw_event_afs_server+0x61/0xac\u000a SRXAFSCB_CallBack+0x11f/0x16c\u000a process_one_work+0x2c5/0x4ee\u000a ? worker_thread+0x234/0x2ac\u000a worker_thread+0x1d8/0x2ac\u000a ? cancel_delayed_work_sync+0xf/0xf\u000a kthread+0x11f/0x127\u000a ? kthread_park+0x76/0x76\u000a ret_from_fork+0x24/0x30\u000a\u000aFixes: 68251f0a6818 (\"afs: Fix whole-volume callback handling\")\u000aSigned-off-by: David Howells \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:56 +0200", "id" : "7b0ef1ba26048ac3ca00408c6d689a717e65cf58", "msg" : "afs: Fix uninitialised spinlock afs_volume::cb_break_lock", "paths" : [ { "editType" : "edit", "file" : "fs/afs/volume.c" }, { "editType" : "edit", "file" : "fs/afs/internal.h" }, { "editType" : "edit", "file" : "fs/afs/callback.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/platform/efi/quirks.c" ], "commitId" : "5f7bb2a5d565c33310f8bb57322affdd707b3e2a", "timestamp" : 1563692516000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/efi: fix a -Wtype-limits compilation warning\u000a\u000a[ Upstream commit 919aef44d73d5d0c04213cb1bc31149cc074e65e ]\u000a\u000aCompiling a kernel with W=1 generates this warning,\u000a\u000aarch/x86/platform/efi/quirks.c:731:16: warning: comparison of unsigned\u000aexpression >= 0 is always true [-Wtype-limits]\u000a\u000aFixes: 3425d934fc03 (\"efi/x86: Handle page faults occurring while running ...\")\u000aSigned-off-by: Qian Cai \u000aAcked-by: \"Prakhya, Sai Praneeth\" \u000aSigned-off-by: Ard Biesheuvel \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:56 +0200", "id" : "5f7bb2a5d565c33310f8bb57322affdd707b3e2a", "msg" : "x86/efi: fix a -Wtype-limits compilation warning", "paths" : [ { "editType" : "edit", "file" : "arch/x86/platform/efi/quirks.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/apic/apic.c" ], "commitId" : "99a40d66b87657ce27b13e6c98fcdfa8b924e0c1", "timestamp" : 1563692516000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz\u000a\u000a[ Upstream commit ea136a112d89bade596314a1ae49f748902f4727 ]\u000a\u000aThe left shift of unsigned int cpu_khz will overflow for large values of\u000acpu_khz, so cast it to a long long before shifting it to avoid overvlow.\u000aFor example, this can happen when cpu_khz is 4194305, i.e. ~4.2 GHz.\u000a\u000aAddresses-Coverity: (\"Unintentional integer overflow\")\u000aFixes: 8c3ba8d04924 (\"x86, apic: ack all pending irqs when crashed/on kexec\")\u000aSigned-off-by: Colin Ian King \u000aSigned-off-by: Thomas Gleixner \u000aCc: Borislav Petkov \u000aCc: \"H . Peter Anvin\" \u000aCc: kernel-janitors@vger.kernel.org\u000aLink: https://lkml.kernel.org/r/20190619181446.13635-1-colin.king@canonical.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:56 +0200", "id" : "99a40d66b87657ce27b13e6c98fcdfa8b924e0c1", "msg" : "x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/apic/apic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/emulex/benet/be_ethtool.c" ], "commitId" : "f8bc37f617447d2fa416ba0deab17324452c7aaa", "timestamp" : 1563692516000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "be2net: fix link failure after ethtool offline test\u000a\u000a[ Upstream commit 2e5db6eb3c23e5dc8171eb8f6af7a97ef9fcf3a9 ]\u000a\u000aCertain cards in conjunction with certain switches need a little more\u000atime for link setup that results in ethtool link test failure after\u000aoffline test. Patch adds a loop that waits for a link setup finish.\u000a\u000aChanges in v2:\u000a- added fixes header\u000a\u000aFixes: 4276e47e2d1c (\"be2net: Add link test to list of ethtool self tests.\")\u000aSigned-off-by: Petr Oros \u000aReviewed-by: Ivan Vecera \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:56 +0200", "id" : "f8bc37f617447d2fa416ba0deab17324452c7aaa", "msg" : "be2net: fix link failure after ethtool offline test", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/emulex/benet/be_ethtool.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ppp/ppp_mppe.c" ], "commitId" : "390431e628c697f6823cb9f73d59bebac92f637a", "timestamp" : 1563692517000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ppp: mppe: Add softdep to arc4\u000a\u000a[ Upstream commit aad1dcc4f011ea409850e040363dff1e59aa4175 ]\u000a\u000aThe arc4 crypto is mandatory at ppp_mppe probe time, so let's put a\u000asoftdep line, so that the corresponding module gets prepared\u000agracefully. Without this, a simple inclusion to initrd via dracut\u000afailed due to the missing dependency, for example.\u000a\u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:57 +0200", "id" : "390431e628c697f6823cb9f73d59bebac92f637a", "msg" : "ppp: mppe: Add softdep to arc4", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ppp/ppp_mppe.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/sis/sis900.c" ], "commitId" : "1bca8f4566795d383b3b74966d21b2c1802ab8ef", "timestamp" : 1563692517000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sis900: fix TX completion\u000a\u000a[ Upstream commit 8ac8a01092b2added0749ef937037bf1912e13e3 ]\u000a\u000aSince commit 605ad7f184b60cfaacbc038aa6c55ee68dee3c89 \"tcp: refine TSO autosizing\",\u000aoutbound throughput is dramatically reduced for some connections, as sis900\u000ais doing TX completion within idle states only.\u000a\u000aMake TX completion happen after every transmitted packet.\u000a\u000aTest:\u000anetperf\u000a\u000abefore patch:\u000a> netperf -H remote -l -2000000 -- -s 1000000\u000aMIGRATED TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to 95.223.112.76 () port 0 AF_INET : demo\u000aRecv Send Send\u000aSocket Socket Message Elapsed\u000aSize Size Size Time Throughput\u000abytes bytes bytes secs. 10^6bits/sec\u000a\u000a 87380 327680 327680 253.44 0.06\u000a\u000aafter patch:\u000a> netperf -H remote -l -10000000 -- -s 1000000\u000aMIGRATED TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to 95.223.112.76 () port 0 AF_INET : demo\u000aRecv Send Send\u000aSocket Socket Message Elapsed\u000aSize Size Size Time Throughput\u000abytes bytes bytes secs. 10^6bits/sec\u000a\u000a 87380 327680 327680 5.38 14.89\u000a\u000aThx to Dave Miller and Eric Dumazet for helpful hints\u000a\u000aSigned-off-by: Sergej Benilov \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:57 +0200", "id" : "1bca8f4566795d383b3b74966d21b2c1802ab8ef", "msg" : "sis900: fix TX completion", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/sis/sis900.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/imx6ul.dtsi" ], "commitId" : "aa08b940a00313b3c6704f5eec15f21ef69b6e5e", "timestamp" : 1563692517000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: imx6ul: fix PWM[1-4] interrupts\u000a\u000a[ Upstream commit 3cf10132ac8d536565f2c02f60a3aeb315863a52 ]\u000a\u000aAccording to the i.MX6UL/L RM, table 3.1 \"ARM Cortex A7 domain interrupt\u000asummary\", the interrupts for the PWM[1-4] go from 83 to 86.\u000a\u000aFixes: b9901fe84f02 (\"ARM: dts: imx6ul: add pwm[1-4] nodes\")\u000aSigned-off-by: Sébastien Szymanski \u000aReviewed-by: Fabio Estevam \u000aSigned-off-by: Shawn Guo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:57 +0200", "id" : "aa08b940a00313b3c6704f5eec15f21ef69b6e5e", "msg" : "ARM: dts: imx6ul: fix PWM[1-4] interrupts", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/imx6ul.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pinctrl/pinctrl-mcp23s08.c" ], "commitId" : "e6c2076b1421249682f02b345b484d9fcb3538f2", "timestamp" : 1563692518000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order\u000a\u000a[ Upstream commit 6dbc6e6f58556369bf999cd7d9793586f1b0e4b4 ]\u000a\u000aCurrently probing of the mcp23s08 results in an error message\u000a\"detected irqchip that is shared with multiple gpiochips:\u000aplease fix the driver\"\u000a\u000aThis is due to the following:\u000a\u000aCall to mcp23s08_irqchip_setup() with call hierarchy:\u000amcp23s08_irqchip_setup()\u000a gpiochip_irqchip_add_nested()\u000a gpiochip_irqchip_add_key()\u000a gpiochip_set_irq_hooks()\u000a\u000aCall to devm_gpiochip_add_data() with call hierarchy:\u000adevm_gpiochip_add_data()\u000a gpiochip_add_data_with_key()\u000a gpiochip_add_irqchip()\u000a gpiochip_set_irq_hooks()\u000a\u000aThe gpiochip_add_irqchip() returns immediately if there isn't a irqchip\u000abut we added a irqchip due to the previous mcp23s08_irqchip_setup()\u000acall. So it calls gpiochip_set_irq_hooks() a second time.\u000a\u000aFix this by moving the call to devm_gpiochip_add_data before\u000athe call to mcp23s08_irqchip_setup\u000a\u000aFixes: 02e389e63e35 (\"pinctrl: mcp23s08: fix irq setup order\")\u000aSuggested-by: Marco Felsch \u000aSigned-off-by: Phil Reid \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:58 +0200", "id" : "e6c2076b1421249682f02b345b484d9fcb3538f2", "msg" : "pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order", "paths" : [ { "editType" : "edit", "file" : "drivers/pinctrl/pinctrl-mcp23s08.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pinctrl/pinctrl-ocelot.c" ], "commitId" : "fc8f20ce6167be49f58bb347c30ea143a016965a", "timestamp" : 1563692518000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pinctrl: ocelot: fix gpio direction for pins after 31\u000a\u000a[ Upstream commit f2818ba3a0125670cb9999bb5a65ebb631a8da2f ]\u000a\u000aThe third argument passed to REG is not the correct one and\u000aocelot_gpio_set_direction is not working for pins after 31. Fix that by\u000apassing the pin number instead of the modulo 32 value.\u000a\u000aFixes: da801ab56ad8 pinctrl: ocelot: add MSCC Jaguar2 support\u000aSigned-off-by: Alexandre Belloni \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:58 +0200", "id" : "fc8f20ce6167be49f58bb347c30ea143a016965a", "msg" : "pinctrl: ocelot: fix gpio direction for pins after 31", "paths" : [ { "editType" : "edit", "file" : "drivers/pinctrl/pinctrl-ocelot.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pinctrl/pinctrl-ocelot.c" ], "commitId" : "8e9734fd9acb68d2d1c397b007062bbf7be4451e", "timestamp" : 1563692518000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pinctrl: ocelot: fix pinmuxing for pins after 31\u000a\u000a[ Upstream commit 4b36082e2e09c2769710756390d54cfca563ed96 ]\u000a\u000aThe actual layout for OCELOT_GPIO_ALT[01] when there are more than 32 pins\u000ais interleaved, i.e. OCELOT_GPIO_ALT0[0], OCELOT_GPIO_ALT1[0],\u000aOCELOT_GPIO_ALT0[1], OCELOT_GPIO_ALT1[1]. Introduce a new REG_ALT macro to\u000afacilitate the register offset calculation and use it where necessary.\u000a\u000aFixes: da801ab56ad8 pinctrl: ocelot: add MSCC Jaguar2 support\u000aSigned-off-by: Alexandre Belloni \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:58 +0200", "id" : "8e9734fd9acb68d2d1c397b007062bbf7be4451e", "msg" : "pinctrl: ocelot: fix pinmuxing for pins after 31", "paths" : [ { "editType" : "edit", "file" : "drivers/pinctrl/pinctrl-ocelot.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/dm-table.c" ], "commitId" : "929f7f169066a23e61c6bcb3588feeab00ab59d7", "timestamp" : 1563692518000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dm table: don't copy from a NULL pointer in realloc_argv()\u000a\u000a[ Upstream commit a0651926553cfe7992166432e418987760882652 ]\u000a\u000aFor the first call to realloc_argv() in dm_split_args(), old_argv is\u000aNULL and size is zero. Then memcpy is called, with the NULL old_argv\u000aas the source argument and a zero size argument. AFAIK, this is\u000aundefined behavior and generates the following warning when compiled\u000awith UBSAN on ppc64le:\u000a\u000aIn file included from ./arch/powerpc/include/asm/paca.h:19,\u000a from ./arch/powerpc/include/asm/current.h:16,\u000a from ./include/linux/sched.h:12,\u000a from ./include/linux/kthread.h:6,\u000a from drivers/md/dm-core.h:12,\u000a from drivers/md/dm-table.c:8:\u000aIn function 'memcpy',\u000a inlined from 'realloc_argv' at drivers/md/dm-table.c:565:3,\u000a inlined from 'dm_split_args' at drivers/md/dm-table.c:588:9:\u000a./include/linux/string.h:345:9: error: argument 2 null where non-null expected [-Werror=nonnull]\u000a return __builtin_memcpy(p, q, size);\u000a ^~~~~~~~~~~~~~~~~~~~~~~~~~~~\u000adrivers/md/dm-table.c: In function 'dm_split_args':\u000a./include/linux/string.h:345:9: note: in a call to built-in function '__builtin_memcpy'\u000a\u000aSigned-off-by: Jerome Marchand \u000aSigned-off-by: Mike Snitzer \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:58 +0200", "id" : "929f7f169066a23e61c6bcb3588feeab00ab59d7", "msg" : "dm table: don't copy from a NULL pointer in realloc_argv()", "paths" : [ { "editType" : "edit", "file" : "drivers/md/dm-table.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/dm-verity-target.c" ], "commitId" : "79231082b13a11601113e87201e3a1cdd13c8724", "timestamp" : 1563692519000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dm verity: use message limit for data block corruption message\u000a\u000a[ Upstream commit 2eba4e640b2c4161e31ae20090a53ee02a518657 ]\u000a\u000aDM verity should also use DMERR_LIMIT to limit repeat data block\u000acorruption messages.\u000a\u000aSigned-off-by: Milan Broz \u000aSigned-off-by: Mike Snitzer \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:59 +0200", "id" : "79231082b13a11601113e87201e3a1cdd13c8724", "msg" : "dm verity: use message limit for data block corruption message", "paths" : [ { "editType" : "edit", "file" : "drivers/md/dm-verity-target.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/head64.c" ], "commitId" : "840b12259097779e6dd908388aeda23bb94fbbe4", "timestamp" : 1563692519000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/boot/64: Fix crash if kernel image crosses page table boundary\u000a\u000a[ Upstream commit 81c7ed296dcd02bc0b4488246d040e03e633737a ]\u000a\u000aA kernel which boots in 5-level paging mode crashes in a small percentage\u000aof cases if KASLR is enabled.\u000a\u000aThis issue was tracked down to the case when the kernel image unpacks in a\u000away that it crosses an 1G boundary. The crash is caused by an overrun of\u000athe PMD page table in __startup_64() and corruption of P4D page table\u000aallocated next to it. This particular issue is not visible with 4-level\u000apaging as P4D page tables are not used.\u000a\u000aBut the P4D and the PUD calculation have similar problems.\u000a\u000aThe PMD index calculation is wrong due to operator precedence, which fails\u000ato confine the PMDs in the PMD array on wrap around.\u000a\u000aThe P4D calculation for 5-level paging and the PUD calculation calculate\u000athe first index correctly, but then blindly increment it which causes the\u000asame issue when a kernel image is located across a 512G and for 5-level\u000apaging across a 46T boundary.\u000a\u000aThis wrap around mishandling was introduced when these parts moved from\u000aassembly to C.\u000a\u000aRestore it to the correct behaviour.\u000a\u000aFixes: c88d71508e36 (\"x86/boot/64: Rewrite startup_64() in C\")\u000aSigned-off-by: Kirill A. Shutemov \u000aSigned-off-by: Thomas Gleixner \u000aCc: Borislav Petkov \u000aCc: \"H. Peter Anvin\" \u000aCc: Dave Hansen \u000aCc: Andy Lutomirski \u000aCc: Peter Zijlstra \u000aLink: https://lkml.kernel.org/r/20190620112345.28833-1-kirill.shutemov@linux.intel.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:59 +0200", "id" : "840b12259097779e6dd908388aeda23bb94fbbe4", "msg" : "x86/boot/64: Fix crash if kernel image crosses page table boundary", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/head64.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/head64.c" ], "commitId" : "3dee6a914f5c3c0621ede93205c39278a41865ec", "timestamp" : 1563692519000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/boot/64: Add missing fixup_pointer() for next_early_pgt access\u000a\u000a[ Upstream commit c1887159eb48ba40e775584cfb2a443962cf1a05 ]\u000a\u000a__startup_64() uses fixup_pointer() to access global variables in a\u000aposition-independent fashion. Access to next_early_pgt was wrapped into the\u000ahelper, but one instance in the 5-level paging branch was missed.\u000a\u000aGCC generates a R_X86_64_PC32 PC-relative relocation for the access which\u000adoesn't trigger the issue, but Clang emmits a R_X86_64_32S which leads to\u000aan invalid memory access and system reboot.\u000a\u000aFixes: 187e91fe5e91 (\"x86/boot/64/clang: Use fixup_pointer() to access 'next_early_pgt'\")\u000aSigned-off-by: Kirill A. Shutemov \u000aSigned-off-by: Thomas Gleixner \u000aCc: Borislav Petkov \u000aCc: \"H. Peter Anvin\" \u000aCc: Dave Hansen \u000aCc: Andy Lutomirski \u000aCc: Peter Zijlstra \u000aCc: Alexander Potapenko \u000aLink: https://lkml.kernel.org/r/20190620112422.29264-1-kirill.shutemov@linux.intel.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:59 +0200", "id" : "3dee6a914f5c3c0621ede93205c39278a41865ec", "msg" : "x86/boot/64: Add missing fixup_pointer() for next_early_pgt access", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/head64.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/hid-ids.h", "drivers/hid/hid-quirks.c" ], "commitId" : "499380084c040d22b78581021c8ce3559ff6ebbd", "timestamp" : 1563692519000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: chicony: add another quirk for PixArt mouse\u000a\u000a[ Upstream commit dcf768b0ac868630e7bdb6f2f1c9fe72788012fa ]\u000a\u000aI've spotted another Chicony PixArt mouse in the wild, which requires\u000aHID_QUIRK_ALWAYS_POLL quirk, otherwise it disconnects each minute.\u000a\u000aUSB ID of this device is 0x04f2:0x0939.\u000a\u000aWe've introduced quirks like this for other models before, so lets add\u000athis mouse too.\u000a\u000aLink: https://github.com/sriemer/fix-linux-mouse#usb-mouse-disconnectsreconnects-every-minute-on-linux\u000aSigned-off-by: Oleksandr Natalenko \u000aAcked-by: Sebastian Parschauer \u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:01:59 +0200", "id" : "499380084c040d22b78581021c8ce3559ff6ebbd", "msg" : "HID: chicony: add another quirk for PixArt mouse", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/hid-quirks.c" }, { "editType" : "edit", "file" : "drivers/hid/hid-ids.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/hid-uclogic-core.c", "drivers/hid/hid-uclogic-params.c", "drivers/hid/hid-ids.h" ], "commitId" : "c82aaf094557c1e43723cd0bffab932506a8c573", "timestamp" : 1563692520000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: uclogic: Add support for Huion HS64 tablet\u000a\u000a[ Upstream commit 315ffcc9a1e054bb460f9203058b52dc26b1173d ]\u000a\u000aAdd support for Huion HS64 drawing tablet to hid-uclogic\u000a\u000aSigned-off-by: Kyle Godbey \u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:00 +0200", "id" : "c82aaf094557c1e43723cd0bffab932506a8c573", "msg" : "HID: uclogic: Add support for Huion HS64 tablet", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/hid-ids.h" }, { "editType" : "edit", "file" : "drivers/hid/hid-uclogic-core.c" }, { "editType" : "edit", "file" : "drivers/hid/hid-uclogic-params.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/hid-multitouch.c", "drivers/hid/hid-ids.h" ], "commitId" : "b9cdcdf70289260d79517dc51e8771498375bb15", "timestamp" : 1563692520000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: multitouch: Add pointstick support for ALPS Touchpad\u000a\u000a[ Upstream commit 0a95fc733da375de0688d0f1fd3a2869a1c1d499 ]\u000a\u000aThere's a new ALPS touchpad/pointstick combo device that requires\u000aMT_CLS_WIN_8_DUAL to make its pointsitck work as a mouse.\u000a\u000aThe device can be found on HP ZBook 17 G5.\u000a\u000aSigned-off-by: Kai-Heng Feng \u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:00 +0200", "id" : "b9cdcdf70289260d79517dc51e8771498375bb15", "msg" : "HID: multitouch: Add pointstick support for ALPS Touchpad", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/hid-multitouch.c" }, { "editType" : "edit", "file" : "drivers/hid/hid-ids.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pinctrl/mediatek/mtk-eint.c" ], "commitId" : "ea722ba498eb510f395e94814121d401add7648e", "timestamp" : 1563692520000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pinctrl: mediatek: Ignore interrupts that are wake only during resume\u000a\u000a[ Upstream commit 35594bc7cecf3a78504b590e350570e8f4d7779e ]\u000a\u000aBefore suspending, mtk-eint would set the interrupt mask to the\u000aone in wake_mask. However, some of these interrupts may not have a\u000acorresponding interrupt handler, or the interrupt may be disabled.\u000a\u000aOn resume, the eint irq handler would trigger nevertheless,\u000aand irq/pm.c:irq_pm_check_wakeup would be called, which would\u000atry to call irq_disable. However, if the interrupt is not enabled\u000a(irqd_irq_disabled(&desc->irq_data) is true), the call does nothing,\u000aand the interrupt is left enabled in the eint driver.\u000a\u000aEspecially for level-sensitive interrupts, this will lead to an\u000ainterrupt storm on resume.\u000a\u000aIf we detect that an interrupt is only in wake_mask, but not in\u000acur_mask, we can just mask it out immediately (as mtk_eint_resume\u000awould do anyway at a later stage in the resume sequence, when\u000arestoring cur_mask).\u000a\u000aFixes: bf22ff45bed6 (\"genirq: Avoid unnecessary low level irq function calls\")\u000aSigned-off-by: Nicolas Boichat \u000aAcked-by: Sean Wang \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:00 +0200", "id" : "ea722ba498eb510f395e94814121d401add7648e", "msg" : "pinctrl: mediatek: Ignore interrupts that are wake only during resume", "paths" : [ { "editType" : "edit", "file" : "drivers/pinctrl/mediatek/mtk-eint.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/cpu.c" ], "commitId" : "2970a55466e8d904ad41969c16c64f5d67c82332", "timestamp" : 1563692520000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cpu/hotplug: Fix out-of-bounds read when setting fail state\u000a\u000a[ Upstream commit 33d4a5a7a5b4d02915d765064b2319e90a11cbde ]\u000a\u000aSetting invalid value to /sys/devices/system/cpu/cpuX/hotplug/fail\u000acan control `struct cpuhp_step *sp` address, results in the following\u000aglobal-out-of-bounds read.\u000a\u000aReproducer:\u000a\u000a # echo -2 > /sys/devices/system/cpu/cpu0/hotplug/fail\u000a\u000aKASAN report:\u000a\u000a BUG: KASAN: global-out-of-bounds in write_cpuhp_fail+0x2cd/0x2e0\u000a Read of size 8 at addr ffffffff89734438 by task bash/1941\u000a\u000a CPU: 0 PID: 1941 Comm: bash Not tainted 5.2.0-rc6+ #31\u000a Call Trace:\u000a write_cpuhp_fail+0x2cd/0x2e0\u000a dev_attr_store+0x58/0x80\u000a sysfs_kf_write+0x13d/0x1a0\u000a kernfs_fop_write+0x2bc/0x460\u000a vfs_write+0x1e1/0x560\u000a ksys_write+0x126/0x250\u000a do_syscall_64+0xc1/0x390\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a RIP: 0033:0x7f05e4f4c970\u000a\u000a The buggy address belongs to the variable:\u000a cpu_hotplug_lock+0x98/0xa0\u000a\u000a Memory state around the buggy address:\u000a ffffffff89734300: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00\u000a ffffffff89734380: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00\u000a >ffffffff89734400: 00 00 00 00 fa fa fa fa 00 00 00 00 fa fa fa fa\u000a ^\u000a ffffffff89734480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\u000a ffffffff89734500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\u000a\u000aAdd a sanity check for the value written from user space.\u000a\u000aFixes: 1db49484f21ed (\"smp/hotplug: Hotplug state fail injection\")\u000aSigned-off-by: Eiichi Tsukata \u000aSigned-off-by: Thomas Gleixner \u000aCc: peterz@infradead.org\u000aLink: https://lkml.kernel.org/r/20190627024732.31672-1-devel@etsukata.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:00 +0200", "id" : "2970a55466e8d904ad41969c16c64f5d67c82332", "msg" : "cpu/hotplug: Fix out-of-bounds read when setting fail state", "paths" : [ { "editType" : "edit", "file" : "kernel/cpu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pinctrl/mediatek/mtk-eint.c" ], "commitId" : "056432bed244cb8c3229f875b51d59c477e70054", "timestamp" : 1563692520000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pinctrl: mediatek: Update cur_mask in mask/mask ops\u000a\u000a[ Upstream commit 9d957a959bc8c3dfe37572ac8e99affb5a885965 ]\u000a\u000aDuring suspend/resume, mtk_eint_mask may be called while\u000awake_mask is active. For example, this happens if a wake-source\u000awith an active interrupt handler wakes the system:\u000airq/pm.c:irq_pm_check_wakeup would disable the interrupt, so\u000athat it can be handled later on in the resume flow.\u000a\u000aHowever, this may happen before mtk_eint_do_resume is called:\u000ain this case, wake_mask is loaded, and cur_mask is restored\u000afrom an older copy, re-enabling the interrupt, and causing\u000aan interrupt storm (especially for level interrupts).\u000a\u000aStep by step, for a line that has both wake and interrupt enabled:\u000a 1. cur_mask[irq] = 1; wake_mask[irq] = 1; EINT_EN[irq] = 1 (interrupt\u000a enabled at hardware level)\u000a 2. System suspends, resumes due to that line (at this stage EINT_EN\u000a == wake_mask)\u000a 3. irq_pm_check_wakeup is called, and disables the interrupt =>\u000a EINT_EN[irq] = 0, but we still have cur_mask[irq] = 1\u000a 4. mtk_eint_do_resume is called, and restores EINT_EN = cur_mask, so\u000a it reenables EINT_EN[irq] = 1 => interrupt storm as the driver\u000a is not yet ready to handle the interrupt.\u000a\u000aThis patch fixes the issue in step 3, by recording all mask/unmask\u000achanges in cur_mask. This also avoids the need to read the current\u000amask in eint_do_suspend, and we can remove mtk_eint_chip_read_mask\u000afunction.\u000a\u000aThe interrupt will be re-enabled properly later on, sometimes after\u000amtk_eint_do_resume, when the driver is ready to handle it.\u000a\u000aFixes: 58a5e1b64bb0 (\"pinctrl: mediatek: Implement wake handler and suspend resume\")\u000aSigned-off-by: Nicolas Boichat \u000aAcked-by: Sean Wang \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:00 +0200", "id" : "056432bed244cb8c3229f875b51d59c477e70054", "msg" : "pinctrl: mediatek: Update cur_mask in mask/mask ops", "paths" : [ { "editType" : "edit", "file" : "drivers/pinctrl/mediatek/mtk-eint.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "mm/oom_kill.c" ], "commitId" : "1451f5647ae04b2f038aba58379888008a2f5d0e", "timestamp" : 1563692520000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mm/oom_kill.c: fix uninitialized oc->constraint\u000a\u000a[ Upstream commit 432b1de0de02a83f64695e69a2d83cbee10c236f ]\u000a\u000aIn dump_oom_summary() oc->constraint is used to show oom_constraint_text,\u000abut it hasn't been set before. So the value of it is always the default\u000avalue 0. We should inititialize it before.\u000a\u000aBellow is the output when memcg oom occurs,\u000a\u000abefore this patch:\u000a oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null), cpuset=/,mems_allowed=0,oom_memcg=/foo,task_memcg=/foo,task=bash,pid=7997,uid=0\u000a\u000aafter this patch:\u000a oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null), cpuset=/,mems_allowed=0,oom_memcg=/foo,task_memcg=/foo,task=bash,pid=13681,uid=0\u000a\u000aLink: http://lkml.kernel.org/r/1560522038-15879-1-git-send-email-laoar.shao@gmail.com\u000aFixes: ef8444ea01d7 (\"mm, oom: reorganize the oom report in dump_header\")\u000aSigned-off-by: Yafang Shao \u000aAcked-by: Michal Hocko \u000aCc: Wind Yu \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:00 +0200", "id" : "1451f5647ae04b2f038aba58379888008a2f5d0e", "msg" : "mm/oom_kill.c: fix uninitialized oc->constraint", "paths" : [ { "editType" : "edit", "file" : "mm/oom_kill.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/fork.c" ], "commitId" : "e97fe6ea900b72f98ab92ddce8947923bf67e239", "timestamp" : 1563692521000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "fork,memcg: alloc_thread_stack_node needs to set tsk->stack\u000a\u000a[ Upstream commit 1bf4580e00a248a2c86269125390eb3648e1877c ]\u000a\u000aCommit 5eed6f1dff87 (\"fork,memcg: fix crash in free_thread_stack on\u000amemcg charge fail\") corrected two instances, but there was a third\u000ainstance of this bug.\u000a\u000aWithout setting tsk->stack, if memcg_charge_kernel_stack fails, it'll\u000aexecute free_thread_stack() on a dangling pointer.\u000a\u000aEnterprise kernels are compiled with VMAP_STACK=y so this isn't\u000acritical, but custom VMAP_STACK=n builds should have some performance\u000aadvantage, with the drawback of risking to fail fork because compaction\u000adidn't succeed. So as long as VMAP_STACK=n is a supported option it's\u000aworth fixing it upstream.\u000a\u000aLink: http://lkml.kernel.org/r/20190619011450.28048-1-aarcange@redhat.com\u000aFixes: 9b6f7e163cd0 (\"mm: rework memcg kernel stack accounting\")\u000aSigned-off-by: Andrea Arcangeli \u000aReviewed-by: Rik van Riel \u000aAcked-by: Roman Gushchin \u000aAcked-by: Michal Hocko \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:01 +0200", "id" : "e97fe6ea900b72f98ab92ddce8947923bf67e239", "msg" : "fork,memcg: alloc_thread_stack_node needs to set tsk->stack", "paths" : [ { "editType" : "edit", "file" : "kernel/fork.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/kernel.h" ], "commitId" : "cbf125668acb30648e254b9669097e15d01aa601", "timestamp" : 1563692521000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL\u000a\u000a[ Upstream commit 8f9fab480c7a87b10bb5440b5555f370272a5d59 ]\u000a\u000aDIV_ROUND_UP_ULL adds the two arguments and then invokes\u000aDIV_ROUND_DOWN_ULL. But on a 32bit system the addition of two 32 bit\u000avalues can overflow. DIV_ROUND_DOWN_ULL does it correctly and stashes\u000athe addition into a unsigned long long so cast the result to unsigned\u000along long here to avoid the overflow condition.\u000a\u000a[akpm@linux-foundation.org: DIV_ROUND_UP_ULL must be an rval]\u000aLink: http://lkml.kernel.org/r/20190625100518.30753-1-vkoul@kernel.org\u000aSigned-off-by: Vinod Koul \u000aReviewed-by: Andrew Morton \u000aCc: Bjorn Andersson \u000aCc: Randy Dunlap \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:01 +0200", "id" : "cbf125668acb30648e254b9669097e15d01aa601", "msg" : "linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL", "paths" : [ { "editType" : "edit", "file" : "include/linux/kernel.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/irq/autoprobe.c", "kernel/irq/chip.c", "kernel/irq/manage.c", "kernel/irq/cpuhotplug.c", "kernel/irq/internals.h" ], "commitId" : "284f5105e493181f9a4e1015f0635999257580fa", "timestamp" : 1563692521000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "genirq: Delay deactivation in free_irq()\u000a\u000acommit 4001d8e8762f57d418b66e4e668601791900a1dd upstream.\u000a\u000aWhen interrupts are shutdown, they are immediately deactivated in the\u000airqdomain hierarchy. While this looks obviously correct there is a subtle\u000aissue:\u000a\u000aThere might be an interrupt in flight when free_irq() is invoking the\u000ashutdown. This is properly handled at the irq descriptor / primary handler\u000alevel, but the deactivation might completely disable resources which are\u000arequired to acknowledge the interrupt.\u000a\u000aSplit the shutdown code and deactivate the interrupt after synchronization\u000ain free_irq(). Fixup all other usage sites where this is not an issue to\u000ainvoke the combined shutdown_and_deactivate() function instead.\u000a\u000aThis still might be an issue if the interrupt in flight servicing is\u000adelayed on a remote CPU beyond the invocation of synchronize_irq(), but\u000athat cannot be handled at that level and needs to be handled in the\u000asynchronize_irq() context.\u000a\u000aFixes: f8264e34965a (\"irqdomain: Introduce new interfaces to support hierarchy irqdomains\")\u000aReported-by: Robert Hodaszi \u000aSigned-off-by: Thomas Gleixner \u000aReviewed-by: Marc Zyngier \u000aLink: https://lkml.kernel.org/r/20190628111440.098196390@linutronix.de\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:01 +0200", "id" : "284f5105e493181f9a4e1015f0635999257580fa", "msg" : "genirq: Delay deactivation in free_irq()", "paths" : [ { "editType" : "edit", "file" : "kernel/irq/autoprobe.c" }, { "editType" : "edit", "file" : "kernel/irq/manage.c" }, { "editType" : "edit", "file" : "kernel/irq/cpuhotplug.c" }, { "editType" : "edit", "file" : "kernel/irq/chip.c" }, { "editType" : "edit", "file" : "kernel/irq/internals.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/irq/manage.c" ], "commitId" : "cd0222960d81391e387416e5b5170b84947d4cdf", "timestamp" : 1563692521000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "genirq: Fix misleading synchronize_irq() documentation\u000a\u000acommit 1d21f2af8571c6a6a44e7c1911780614847b0253 upstream.\u000a\u000aThe function might sleep, so it cannot be called from interrupt\u000acontext. Not even with care.\u000a\u000aSigned-off-by: Thomas Gleixner \u000aCc: Marc Zyngier \u000aLink: https://lkml.kernel.org/r/20190628111440.189241552@linutronix.de\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:01 +0200", "id" : "cd0222960d81391e387416e5b5170b84947d4cdf", "msg" : "genirq: Fix misleading synchronize_irq() documentation", "paths" : [ { "editType" : "edit", "file" : "kernel/irq/manage.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/irq/manage.c", "kernel/irq/internals.h" ], "commitId" : "b9926c40e4d3a69a8400400c2fd8d6c777c71972", "timestamp" : 1563692521000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "genirq: Add optional hardware synchronization for shutdown\u000a\u000acommit 62e0468650c30f0298822c580f382b16328119f6 upstream.\u000a\u000afree_irq() ensures that no hardware interrupt handler is executing on a\u000adifferent CPU before actually releasing resources and deactivating the\u000ainterrupt completely in a domain hierarchy.\u000a\u000aBut that does not catch the case where the interrupt is on flight at the\u000ahardware level but not yet serviced by the target CPU. That creates an\u000ainteresing race condition:\u000a\u000a CPU 0 CPU 1 IRQ CHIP\u000a\u000a interrupt is raised\u000a sent to CPU1\u000a\u0009\u0009\u0009 Unable to handle\u000a\u0009\u0009\u0009 immediately\u000a\u0009\u0009\u0009 (interrupts off,\u000a\u0009\u0009\u0009 deep idle delay)\u000a mask()\u000a ...\u000a free()\u000a shutdown()\u000a synchronize_irq()\u000a release_resources()\u000a do_IRQ()\u000a -> resources are not available\u000a\u000aThat might be harmless and just trigger a spurious interrupt warning, but\u000asome interrupt chips might get into a wedged state.\u000a\u000aUtilize the existing irq_get_irqchip_state() callback for the\u000asynchronization in free_irq().\u000a\u000asynchronize_hardirq() is not using this mechanism as it might actually\u000adeadlock unter certain conditions, e.g. when called with interrupts\u000adisabled and the target CPU is the one on which the synchronization is\u000ainvoked. synchronize_irq() uses it because that function cannot be called\u000afrom non preemtible contexts as it might sleep.\u000a\u000aNo functional change intended and according to Marc the existing GIC\u000aimplementations where the driver supports the callback should be able\u000ato cope with that core change. Famous last words.\u000a\u000aFixes: 464d12309e1b (\"x86/vector: Switch IOAPIC to global reservation mode\")\u000aReported-by: Robert Hodaszi \u000aSigned-off-by: Thomas Gleixner \u000aReviewed-by: Marc Zyngier \u000aTested-by: Marc Zyngier \u000aLink: https://lkml.kernel.org/r/20190628111440.279463375@linutronix.de\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:01 +0200", "id" : "b9926c40e4d3a69a8400400c2fd8d6c777c71972", "msg" : "genirq: Add optional hardware synchronization for shutdown", "paths" : [ { "editType" : "edit", "file" : "kernel/irq/manage.c" }, { "editType" : "edit", "file" : "kernel/irq/internals.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/apic/io_apic.c" ], "commitId" : "557f2d49240bdff6aa3be2e3646aba5d5f83240c", "timestamp" : 1563692522000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/ioapic: Implement irq_get_irqchip_state() callback\u000a\u000acommit dfe0cf8b51b07e56ded571e3de0a4a9382517231 upstream.\u000a\u000aWhen an interrupt is shut down in free_irq() there might be an inflight\u000ainterrupt pending in the IO-APIC remote IRR which is not yet serviced. That\u000ameans the interrupt has been sent to the target CPUs local APIC, but the\u000atarget CPU is in a state which delays the servicing.\u000a\u000aSo free_irq() would proceed to free resources and to clear the vector\u000abecause synchronize_hardirq() does not see an interrupt handler in\u000aprogress.\u000a\u000aThat can trigger a spurious interrupt warning, which is harmless and just\u000aconfuses users, but it also can leave the remote IRR in a stale state\u000abecause once the handler is invoked the interrupt resources might be freed\u000aalready and therefore acknowledgement is not possible anymore.\u000a\u000aImplement the irq_get_irqchip_state() callback for the IO-APIC irq chip. The\u000acallback is invoked from free_irq() via __synchronize_hardirq(). Check the\u000aremote IRR bit of the interrupt and return 'in flight' if it is set and the\u000ainterrupt is configured in level mode. For edge mode the remote IRR has no\u000ameaning.\u000a\u000aAs this is only meaningful for level triggered interrupts this won't cure\u000athe potential spurious interrupt warning for edge triggered interrupts, but\u000athe edge trigger case does not result in stale hardware state. This has to\u000abe addressed at the vector/interrupt entry level seperately.\u000a\u000aFixes: 464d12309e1b (\"x86/vector: Switch IOAPIC to global reservation mode\")\u000aReported-by: Robert Hodaszi \u000aSigned-off-by: Thomas Gleixner \u000aCc: Marc Zyngier \u000aLink: https://lkml.kernel.org/r/20190628111440.370295517@linutronix.de\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:02 +0200", "id" : "557f2d49240bdff6aa3be2e3646aba5d5f83240c", "msg" : "x86/ioapic: Implement irq_get_irqchip_state() callback", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/apic/io_apic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/apic/vector.c", "arch/x86/include/asm/hw_irq.h", "arch/x86/kernel/irq.c" ], "commitId" : "3fa8d2a72fbab7745175339dfcfd15717a62ab3c", "timestamp" : 1563692522000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/irq: Handle spurious interrupt after shutdown gracefully\u000a\u000acommit b7107a67f0d125459fe41f86e8079afd1a5e0b15 upstream.\u000a\u000aSince the rework of the vector management, warnings about spurious\u000ainterrupts have been reported. Robert provided some more information and\u000adid an initial analysis. The following situation leads to these warnings:\u000a\u000a CPU 0 CPU 1 IO_APIC\u000a\u000a interrupt is raised\u000a sent to CPU1\u000a\u0009\u0009\u0009 Unable to handle\u000a\u0009\u0009\u0009 immediately\u000a\u0009\u0009\u0009 (interrupts off,\u000a\u0009\u0009\u0009 deep idle delay)\u000a mask()\u000a ...\u000a free()\u000a shutdown()\u000a synchronize_irq()\u000a clear_vector()\u000a do_IRQ()\u000a -> vector is clear\u000a\u000aBefore the rework the vector entries of legacy interrupts were statically\u000aassigned and occupied precious vector space while most of them were\u000aunused. Due to that the above situation was handled silently because the\u000avector was handled and the core handler of the assigned interrupt\u000adescriptor noticed that it is shut down and returned.\u000a\u000aWhile this has been usually observed with legacy interrupts, this situation\u000ais not limited to them. Any other interrupt source, e.g. MSI, can cause the\u000asame issue.\u000a\u000aAfter adding proper synchronization for level triggered interrupts, this\u000acan only happen for edge triggered interrupts where the IO-APIC obviously\u000acannot provide information about interrupts in flight.\u000a\u000aWhile the spurious warning is actually harmless in this case it worries\u000ausers and driver developers.\u000a\u000aHandle it gracefully by marking the vector entry as VECTOR_SHUTDOWN instead\u000aof VECTOR_UNUSED when the vector is freed up.\u000a\u000aIf that above late handling happens the spurious detector will not complain\u000aand switch the entry to VECTOR_UNUSED. Any subsequent spurious interrupt on\u000athat line will trigger the spurious warning as before.\u000a\u000aFixes: 464d12309e1b (\"x86/vector: Switch IOAPIC to global reservation mode\")\u000aReported-by: Robert Hodaszi \u000aSigned-off-by: Thomas Gleixner -\u000aTested-by: Robert Hodaszi \u000aCc: Marc Zyngier \u000aLink: https://lkml.kernel.org/r/20190628111440.459647741@linutronix.de\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:02 +0200", "id" : "3fa8d2a72fbab7745175339dfcfd15717a62ab3c", "msg" : "x86/irq: Handle spurious interrupt after shutdown gracefully", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/irq.c" }, { "editType" : "edit", "file" : "arch/x86/kernel/apic/vector.c" }, { "editType" : "edit", "file" : "arch/x86/include/asm/hw_irq.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/include/asm/hw_irq.h", "arch/x86/entry/entry_32.S", "arch/x86/kernel/apic/apic.c", "arch/x86/kernel/idt.c", "arch/x86/entry/entry_64.S" ], "commitId" : "4ac893646c2e7a234d0242ac7a02f675a923fd16", "timestamp" : 1563692522000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/irq: Seperate unused system vectors from spurious entry again\u000a\u000acommit f8a8fe61fec8006575699559ead88b0b833d5cad upstream.\u000a\u000aQuite some time ago the interrupt entry stubs for unused vectors in the\u000asystem vector range got removed and directly mapped to the spurious\u000ainterrupt vector entry point.\u000a\u000aSounds reasonable, but it's subtly broken. The spurious interrupt vector\u000aentry point pushes vector number 0xFF on the stack which makes the whole\u000alogic in __smp_spurious_interrupt() pointless.\u000a\u000aAs a consequence any spurious interrupt which comes from a vector != 0xFF\u000ais treated as a real spurious interrupt (vector 0xFF) and not\u000aacknowledged. That subsequently stalls all interrupt vectors of equal and\u000alower priority, which brings the system to a grinding halt.\u000a\u000aThis can happen because even on 64-bit the system vector space is not\u000aguaranteed to be fully populated. A full compile time handling of the\u000aunused vectors is not possible because quite some of them are conditonally\u000apopulated at runtime.\u000a\u000aBring the entry stubs back, which wastes 160 bytes if all stubs are unused,\u000abut gains the proper handling back. There is no point to selectively spare\u000asome of the stubs which are known at compile time as the required code in\u000athe IDT management would be way larger and convoluted.\u000a\u000aDo not route the spurious entries through common_interrupt and do_IRQ() as\u000athe original code did. Route it to smp_spurious_interrupt() which evaluates\u000athe vector number and acts accordingly now that the real vector numbers are\u000ahanded in.\u000a\u000aFixup the pr_warn so the actual spurious vector (0xff) is clearly\u000adistiguished from the other vectors and also note for the vectored case\u000awhether it was pending in the ISR or not.\u000a\u000a \"Spurious APIC interrupt (vector 0xFF) on CPU#0, should never happen.\"\u000a \"Spurious interrupt vector 0xed on CPU#1. Acked.\"\u000a \"Spurious interrupt vector 0xee on CPU#1. Not pending!.\"\u000a\u000aFixes: 2414e021ac8d (\"x86: Avoid building unused IRQ entry stubs\")\u000aReported-by: Jan Kiszka \u000aSigned-off-by: Thomas Gleixner \u000aCc: Marc Zyngier \u000aCc: Jan Beulich \u000aLink: https://lkml.kernel.org/r/20190628111440.550568228@linutronix.de\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:02 +0200", "id" : "4ac893646c2e7a234d0242ac7a02f675a923fd16", "msg" : "x86/irq: Seperate unused system vectors from spurious entry again", "paths" : [ { "editType" : "edit", "file" : "arch/x86/entry/entry_64.S" }, { "editType" : "edit", "file" : "arch/x86/entry/entry_32.S" }, { "editType" : "edit", "file" : "arch/x86/include/asm/hw_irq.h" }, { "editType" : "edit", "file" : "arch/x86/kernel/apic/apic.c" }, { "editType" : "edit", "file" : "arch/x86/kernel/idt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arc/kernel/unwind.c" ], "commitId" : "d6d65a2fc7cd6d538f42a50a3b8ef5852f900cdc", "timestamp" : 1563692523000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARC: hide unused function unw_hdr_alloc\u000a\u000acommit fd5de2721ea7d16e2b16c4049ac49f229551b290 upstream.\u000a\u000aAs kernelci.org reports, this function is not used in\u000avdk_hs38_defconfig:\u000a\u000aarch/arc/kernel/unwind.c:188:14: warning: 'unw_hdr_alloc' defined but not used [-Wunused-function]\u000a\u000aFixes: bc79c9a72165 (\"ARC: dw2 unwind: Reinstante unwinding out of modules\")\u000aLink: https://kernelci.org/build/id/5d1cae3f59b514300340c132/logs/\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Arnd Bergmann \u000aSigned-off-by: Vineet Gupta \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:03 +0200", "id" : "d6d65a2fc7cd6d538f42a50a3b8ef5852f900cdc", "msg" : "ARC: hide unused function unw_hdr_alloc", "paths" : [ { "editType" : "edit", "file" : "arch/arc/kernel/unwind.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/s390/include/asm/facility.h" ], "commitId" : "d6e7f5e8a13d4037ad1f1efc794989edb223d81b", "timestamp" : 1563692523000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "s390: fix stfle zero padding\u000a\u000acommit 4f18d869ffd056c7858f3d617c71345cf19be008 upstream.\u000a\u000aThe stfle inline assembly returns the number of double words written\u000a(condition code 0) or the double words it would have written\u000a(condition code 3), if the memory array it got as parameter would have\u000abeen large enough.\u000a\u000aThe current stfle implementation assumes that the array is always\u000alarge enough and clears those parts of the array that have not been\u000awritten to with a subsequent memset call.\u000a\u000aIf however the array is not large enough memset will get a negative\u000alength parameter, which means that memset clears memory until it gets\u000aan exception and the kernel crashes.\u000a\u000aTo fix this simply limit the maximum length. Move also the inline\u000aassembly to an extra function to avoid clobbering of register 0, which\u000amight happen because of the added min_t invocation together with code\u000ainstrumentation.\u000a\u000aThe bug was introduced with commit 14375bc4eb8d (\"[S390] cleanup\u000afacility list handling\") but was rather harmless, since it would only\u000awrite to a rather large array. It became a potential problem with\u000acommit 3ab121ab1866 (\"[S390] kernel: Add z/VM LGR detection\"). Since\u000athen it writes to an array with only four double words, while some\u000amachines already deliver three double words. As soon as machines have\u000aa facility bit within the fifth double a crash on IPL would happen.\u000a\u000aFixes: 14375bc4eb8d (\"[S390] cleanup facility list handling\")\u000aCc: # v2.6.37+\u000aReviewed-by: Vasily Gorbik \u000aSigned-off-by: Heiko Carstens \u000aSigned-off-by: Vasily Gorbik \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:03 +0200", "id" : "d6e7f5e8a13d4037ad1f1efc794989edb223d81b", "msg" : "s390: fix stfle zero padding", "paths" : [ { "editType" : "edit", "file" : "arch/s390/include/asm/facility.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/s390/cio/qdio_thinint.c", "drivers/s390/cio/qdio_setup.c" ], "commitId" : "1f5dcaa9207fb9cea3d31c3312388f679d00e569", "timestamp" : 1563692523000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "s390/qdio: (re-)initialize tiqdio list entries\u000a\u000acommit e54e4785cb5cb4896cf4285964aeef2125612fb2 upstream.\u000a\u000aWhen tiqdio_remove_input_queues() removes a queue from the tiq_list as\u000apart of qdio_shutdown(), it doesn't re-initialize the queue's list entry\u000aand the prev/next pointers go stale.\u000a\u000aIf a subsequent qdio_establish() fails while sending the ESTABLISH cmd,\u000ait calls qdio_shutdown() again in QDIO_IRQ_STATE_ERR state and\u000atiqdio_remove_input_queues() will attempt to remove the queue entry a\u000asecond time. This dereferences the stale pointers, and bad things ensue.\u000aFix this by re-initializing the list entry after removing it from the\u000alist.\u000a\u000aFor good practice also initialize the list entry when the queue is first\u000aallocated, and remove the quirky checks that papered over this omission.\u000aNote that prior to\u000acommit e521813468f7 (\"s390/qdio: fix access to uninitialized qdio_q fields\"),\u000athese checks were bogus anyway.\u000a\u000asetup_queues_misc() clears the whole queue struct, and thus needs to\u000are-init the prev/next pointers as well.\u000a\u000aFixes: 779e6e1c724d (\"[S390] qdio: new qdio driver.\")\u000aCc: \u000aSigned-off-by: Julian Wiedmann \u000aSigned-off-by: Vasily Gorbik \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:03 +0200", "id" : "1f5dcaa9207fb9cea3d31c3312388f679d00e569", "msg" : "s390/qdio: (re-)initialize tiqdio list entries", "paths" : [ { "editType" : "edit", "file" : "drivers/s390/cio/qdio_setup.c" }, { "editType" : "edit", "file" : "drivers/s390/cio/qdio_thinint.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/s390/cio/qdio_thinint.c" ], "commitId" : "9ca71f3de797898184e55ca2a56748b6748fb041", "timestamp" : 1563692523000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "s390/qdio: don't touch the dsci in tiqdio_add_input_queues()\u000a\u000acommit ac6639cd3db607d386616487902b4cc1850a7be5 upstream.\u000a\u000aCurrent code sets the dsci to 0x00000080. Which doesn't make any sense,\u000aas the indicator area is located in the _left-most_ byte.\u000a\u000aWorse: if the dsci is the _shared_ indicator, this potentially clears\u000athe indication of activity for a _different_ device.\u000atiqdio_thinint_handler() will then have no reason to call that device's\u000aIRQ handler, and the device ends up stalling.\u000a\u000aFixes: d0c9d4a89fff (\"[S390] qdio: set correct bit in dsci\")\u000aCc: \u000aSigned-off-by: Julian Wiedmann \u000aSigned-off-by: Vasily Gorbik \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:03 +0200", "id" : "9ca71f3de797898184e55ca2a56748b6748fb041", "msg" : "s390/qdio: don't touch the dsci in tiqdio_add_input_queues()", "paths" : [ { "editType" : "edit", "file" : "drivers/s390/cio/qdio_thinint.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/talitos.c", "drivers/crypto/talitos.h" ], "commitId" : "5da292580bd23cf67e7abd850349176ef6973571", "timestamp" : 1563692524000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: talitos - move struct talitos_edesc into talitos.h\u000a\u000acommit d44769e4ccb636e8238adbc151f25467a536711b upstream.\u000a\u000aMoves struct talitos_edesc into talitos.h so that it can be used\u000afrom any place in talitos.c\u000a\u000aIt will be required for next patch (\"crypto: talitos - fix hash\u000aon SEC1\")\u000a\u000aSigned-off-by: Christophe Leroy \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:04 +0200", "id" : "5da292580bd23cf67e7abd850349176ef6973571", "msg" : "crypto: talitos - move struct talitos_edesc into talitos.h", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/talitos.c" }, { "editType" : "edit", "file" : "drivers/crypto/talitos.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/talitos.c" ], "commitId" : "5b7e03647e91ededb1f6e52961c298d6927b1947", "timestamp" : 1563692524000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: talitos - fix hash on SEC1.\u000a\u000acommit 58cdbc6d2263beb36954408522762bbe73169306 upstream.\u000a\u000aOn SEC1, hash provides wrong result when performing hashing in several\u000asteps with input data SG list has more than one element. This was\u000adetected with CONFIG_CRYPTO_MANAGER_EXTRA_TESTS:\u000a\u000a[ 44.185947] alg: hash: md5-talitos test failed (wrong result) on test vector 6, cfg=\"random: may_sleep use_finup src_divs=[25.88%@+8063, 24.19%@+9588, 28.63%@+16333, 4.60%@+6756, 16.70%@+16281] dst_divs=[71.61%@alignmask+16361, 14.36%@+7756, 14.3%@+\"\u000a[ 44.325122] alg: hash: sha1-talitos test failed (wrong result) on test vector 3, cfg=\"random: inplace use_final src_divs=[16.56%@+16378, 52.0%@+16329, 21.42%@alignmask+16380, 10.2%@alignmask+16380] iv_offset=39\"\u000a[ 44.493500] alg: hash: sha224-talitos test failed (wrong result) on test vector 4, cfg=\"random: use_final nosimd src_divs=[52.27%@+7401, 17.34%@+16285, 17.71%@+26, 12.68%@+10644] iv_offset=43\"\u000a[ 44.673262] alg: hash: sha256-talitos test failed (wrong result) on test vector 4, cfg=\"random: may_sleep use_finup src_divs=[60.6%@+12790, 17.86%@+1329, 12.64%@alignmask+16300, 8.29%@+15, 0.40%@+13506, 0.51%@+16322, 0.24%@+16339] dst_divs\"\u000a\u000aThis is due to two issues:\u000a- We have an overlap between the buffer used for copying the input\u000adata (SEC1 doesn't do scatter/gather) and the chained descriptor.\u000a- Data copy is wrong when the previous hash left less than one\u000ablocksize of data to hash, implying a complement of the previous\u000ablock with a few bytes from the new request.\u000a\u000aFix it by:\u000a- Moving the second descriptor after the buffer, as moving the buffer\u000aafter the descriptor would make it more complex for other cipher\u000aoperations (AEAD, ABLKCIPHER)\u000a- Skip the bytes taken from the new request to complete the previous\u000aone by moving the SG list forward.\u000a\u000aFixes: 37b5e8897eb5 (\"crypto: talitos - chain in buffered data for ahash on SEC1\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Christophe Leroy \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-21 09:02:04 +0200", "id" : "5b7e03647e91ededb1f6e52961c298d6927b1947", "msg" : "crypto: talitos - fix hash on SEC1.", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/talitos.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/nx/nx-842-powernv.c" ], "commitId" : "845912c398165cc563ecc280ce429da98028e722", "timestamp" : 1563692524000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto/NX: Set receive window credits to max number of CRBs in RxFIFO\u000a\u000acommit e52d484d9869eb291140545746ccbe5ffc7c9306 upstream.\u000a\u000aSystem gets checkstop if RxFIFO overruns with more requests than the\u000amaximum possible number of CRBs in FIFO at the same time. The max number\u000aof requests per window is controlled by window credits. So find max\u000aCRBs from FIFO size and set it to receive window credits.\u000a\u000aFixes: b0d6c9bab5e4 (\"crypto/nx: Add P9 NX support for 842 compression engine\")\u000aCC: stable@vger.kernel.org # v4.14+\u000aSigned-off-by:Haren Myneni \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000aSigned-off-by: Herbert Xu \u000a\u000a", "date" : "2019-07-21 09:02:04 +0200", "id" : "845912c398165cc563ecc280ce429da98028e722", "msg" : "crypto/NX: Set receive window credits to max number of CRBs in RxFIFO", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/nx/nx-842-powernv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/entry/entry_32.S" ], "commitId" : "0e921583b935d64e89c428ce1c313ae717d1edbd", "timestamp" : 1563692524000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/entry/32: Fix ENDPROC of common_spurious\u000a\u000a[ Upstream commit 1cbec37b3f9cff074a67bef4fc34b30a09958a0a ]\u000a\u000acommon_spurious is currently ENDed erroneously. common_interrupt is used\u000ain its ENDPROC. So fix this mistake.\u000a\u000aFound by my asm macros rewrite patchset.\u000a\u000aFixes: f8a8fe61fec8 (\"x86/irq: Seperate unused system vectors from spurious entry again\")\u000aSigned-off-by: Jiri Slaby \u000aSigned-off-by: Thomas Gleixner \u000aLink: https://lkml.kernel.org/r/20190709063402.19847-1-jslaby@suse.cz\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-21 09:02:04 +0200", "id" : "0e921583b935d64e89c428ce1c313ae717d1edbd", "msg" : "x86/entry/32: Fix ENDPROC of common_spurious", "paths" : [ { "editType" : "edit", "file" : "arch/x86/entry/entry_32.S" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Makefile" ], "commitId" : "0d4f1b2afde8df3b0ca79818123a43a184a0e1ea", "timestamp" : 1563692525000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Linux 5.1.19\u000a", "date" : "2019-07-21 09:02:05 +0200", "id" : "0d4f1b2afde8df3b0ca79818123a43a184a0e1ea", "msg" : "Linux 5.1.19", "paths" : [ { "editType" : "edit", "file" : "Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/mips/include/asm/mach-ath79/ar933x_uart.h" ], "commitId" : "ca9071795bcc259bdefc5bbe47c80de4f437a85b", "timestamp" : 1564125140000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "MIPS: ath79: fix ar933x uart parity mode\u000a\u000a[ Upstream commit db13a5ba2732755cf13320f3987b77cf2a71e790 ]\u000a\u000aWhile trying to get the uart with parity working I found setting even\u000aparity enabled odd parity insted. Fix the register settings to match\u000athe datasheet of AR9331.\u000a\u000aA similar patch was created by 8devices, but not sent upstream.\u000ahttps://github.com/8devices/openwrt-8devices/commit/77c5586ade3bb72cda010afad3f209ed0c98ea7c\u000a\u000aSigned-off-by: Stefan Hellermann \u000aSigned-off-by: Paul Burton \u000aCc: linux-mips@vger.kernel.org\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:20 +0200", "id" : "ca9071795bcc259bdefc5bbe47c80de4f437a85b", "msg" : "MIPS: ath79: fix ar933x uart parity mode", "paths" : [ { "editType" : "edit", "file" : "arch/mips/include/asm/mach-ath79/ar933x_uart.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/mips/boot/compressed/Makefile", "arch/mips/boot/compressed/calc_vmlinuz_load_addr.c" ], "commitId" : "9264f5bd6c07ec40f5cf6d73eba4af127ec2004f", "timestamp" : 1564125140000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "MIPS: fix build on non-linux hosts\u000a\u000a[ Upstream commit 1196364f21ffe5d1e6d83cafd6a2edb89404a3ae ]\u000a\u000acalc_vmlinuz_load_addr.c requires SZ_64K to be defined for alignment\u000apurposes. It included \"../../../../include/linux/sizes.h\" to define\u000athat size, however \"sizes.h\" tries to include which\u000aassumes linux system headers. These may not exist eg. the following\u000aerror was encountered when building Linux for OpenWrt under macOS:\u000a\u000aIn file included from arch/mips/boot/compressed/calc_vmlinuz_load_addr.c:16:\u000aarch/mips/boot/compressed/../../../../include/linux/sizes.h:11:10: fatal error: 'linux/const.h' file not found\u000a ^~~~~~~~~~\u000a\u000aChange makefile to force building on local linux headers instead of\u000asystem headers. Also change eye-watering relative reference in include\u000afile spec.\u000a\u000aThanks to Jo-Philip Wich & Petr Štetiar for assistance in tracking this\u000adown & fixing.\u000a\u000aSuggested-by: Jo-Philipp Wich \u000aSigned-off-by: Petr Štetiar \u000aSigned-off-by: Kevin Darbyshire-Bryant \u000aSigned-off-by: Paul Burton \u000aCc: linux-mips@vger.kernel.org\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:20 +0200", "id" : "9264f5bd6c07ec40f5cf6d73eba4af127ec2004f", "msg" : "MIPS: fix build on non-linux hosts", "paths" : [ { "editType" : "edit", "file" : "arch/mips/boot/compressed/Makefile" }, { "editType" : "edit", "file" : "arch/mips/boot/compressed/calc_vmlinuz_load_addr.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/kernel/image.h" ], "commitId" : "12cf63a2fe0bfdd167808299f8443638bd6719af", "timestamp" : 1564125140000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly\u000a\u000a[ Upstream commit aa69fb62bea15126e744af2e02acc0d6cf3ed4da ]\u000a\u000aAfter r363059 and r363928 in LLVM, a build using ld.lld as the linker\u000awith CONFIG_RANDOMIZE_BASE enabled fails like so:\u000a\u000ald.lld: error: relocation R_AARCH64_ABS32 cannot be used against symbol\u000a__efistub_stext_offset; recompile with -fPIC\u000a\u000aFangrui and Peter figured out that ld.lld is incorrectly considering\u000a__efistub_stext_offset as a relative symbol because of the order in\u000awhich symbols are evaluated. _text is treated as an absolute symbol\u000aand stext is a relative symbol, making __efistub_stext_offset a\u000arelative symbol.\u000a\u000aAdding ABSOLUTE will force ld.lld to evalute this expression in the\u000aright context and does not change ld.bfd's behavior. ld.lld will\u000aneed to be fixed but the developers do not see a quick or simple fix\u000awithout some research (see the linked issue for further explanation).\u000aAdd this simple workaround so that ld.lld can continue to link kernels.\u000a\u000aLink: https://github.com/ClangBuiltLinux/linux/issues/561\u000aLink: https://github.com/llvm/llvm-project/commit/025a815d75d2356f2944136269aa5874721ec236\u000aLink: https://github.com/llvm/llvm-project/commit/249fde85832c33f8b06c6b4ac65d1c4b96d23b83\u000aAcked-by: Ard Biesheuvel \u000aDebugged-by: Fangrui Song \u000aDebugged-by: Peter Smith \u000aSuggested-by: Fangrui Song \u000aSigned-off-by: Nathan Chancellor \u000a[will: add comment]\u000aSigned-off-by: Will Deacon \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:20 +0200", "id" : "12cf63a2fe0bfdd167808299f8443638bd6719af", "msg" : "arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/kernel/image.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/target/iscsi/iscsi_target_auth.c" ], "commitId" : "69ea2b97d9d64d1c814c5b0e8032209654132100", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: iscsi: set auth_protocol back to NULL if CHAP_A value is not supported\u000a\u000a[ Upstream commit 5dd6c49339126c2c8df2179041373222362d6e49 ]\u000a\u000aIf the CHAP_A value is not supported, the chap_server_open() function\u000ashould free the auth_protocol pointer and set it to NULL, or we will leave\u000aa dangling pointer around.\u000a\u000a[ 66.010905] Unsupported CHAP_A value\u000a[ 66.011660] Security negotiation failed.\u000a[ 66.012443] iSCSI Login negotiation failed.\u000a[ 68.413924] general protection fault: 0000 [#1] SMP PTI\u000a[ 68.414962] CPU: 0 PID: 1562 Comm: targetcli Kdump: loaded Not tainted 4.18.0-80.el8.x86_64 #1\u000a[ 68.416589] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011\u000a[ 68.417677] RIP: 0010:__kmalloc_track_caller+0xc2/0x210\u000a\u000aSigned-off-by: Maurizio Lombardi \u000aReviewed-by: Chris Leech \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "69ea2b97d9d64d1c814c5b0e8032209654132100", "msg" : "scsi: iscsi: set auth_protocol back to NULL if CHAP_A value is not supported", "paths" : [ { "editType" : "edit", "file" : "drivers/target/iscsi/iscsi_target_auth.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/dma/imx-sdma.c" ], "commitId" : "94864d24c786a3bec94f821d0521684142fea08d", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dmaengine: imx-sdma: fix use-after-free on probe error path\u000a\u000a[ Upstream commit 2b8066c3deb9140fdf258417a51479b2aeaa7622 ]\u000a\u000aIf probe() fails anywhere beyond the point where\u000asdma_get_firmware() is called, then a kernel oops may occur.\u000a\u000aProblematic sequence of events:\u000a1. probe() calls sdma_get_firmware(), which schedules the\u000a firmware callback to run when firmware becomes available,\u000a using the sdma instance structure as the context\u000a2. probe() encounters an error, which deallocates the\u000a sdma instance structure\u000a3. firmware becomes available, firmware callback is\u000a called with deallocated sdma instance structure\u000a4. use after free - kernel oops !\u000a\u000aSolution: only attempt to load firmware when we're certain\u000athat probe() will succeed. This guarantees that the firmware\u000acallback's context will remain valid.\u000a\u000aNote that the remove() path is unaffected by this issue: the\u000afirmware loader will increment the driver module's use count,\u000aensuring that the module cannot be unloaded while the\u000afirmware callback is pending or running.\u000a\u000aSigned-off-by: Sven Van Asbroeck \u000aReviewed-by: Robin Gong \u000a[vkoul: fixed braces for if condition]\u000aSigned-off-by: Vinod Koul \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "94864d24c786a3bec94f821d0521684142fea08d", "msg" : "dmaengine: imx-sdma: fix use-after-free on probe error path", "paths" : [ { "editType" : "edit", "file" : "drivers/dma/imx-sdma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/debugfs_sta.c" ], "commitId" : "fa84cb2f26f31aa35b13717576829df5d1045a31", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: Check tx_stats before use it\u000a\u000a[ Upstream commit 9e7251fa38978b85108c44743e1436d48e8d0d76 ]\u000a\u000atx_stats will be freed and set to NULL before debugfs_sta node is\u000aremoved in station disconnetion process. So if read the debugfs_sta\u000anode there may be NULL pointer error. Add check for tx_stats before\u000ause it to resove this issue.\u000a\u000aSigned-off-by: Yingying Tang \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "fa84cb2f26f31aa35b13717576829df5d1045a31", "msg" : "ath10k: Check tx_stats before use it", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/debugfs_sta.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/htt_rx.c" ], "commitId" : "4c8cec9a0357cc2f788c257af8c4da5c287d416a", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: htt: don't use txdone_fifo with SDIO\u000a\u000a[ Upstream commit e2a6b711282a371c5153239e0468a48254f17ca6 ]\u000a\u000aHTT High Latency (ATH10K_DEV_TYPE_HL) does not use txdone_fifo at all, we don't\u000aeven initialise it by skipping ath10k_htt_tx_alloc_buf() in\u000aath10k_htt_tx_start(). Because of this using QCA6174 SDIO\u000aath10k_htt_rx_tx_compl_ind() will crash when it accesses unitialised\u000atxdone_fifo. So skip txdone_fifo when using High Latency mode.\u000a\u000aTested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-00007-QCARMSWP-1.\u000a\u000aCo-developed-by: Wen Gong \u000aSigned-off-by: Alagu Sankar \u000aSigned-off-by: Wen Gong \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "4c8cec9a0357cc2f788c257af8c4da5c287d416a", "msg" : "ath10k: htt: don't use txdone_fifo with SDIO", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/htt_rx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/mac.c" ], "commitId" : "fff1972f12f32f8e0f7fe5068911a248805229d0", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: fix incorrect multicast/broadcast rate setting\u000a\u000a[ Upstream commit 93ee3d108fc77e19efeac3ec5aa7d5886711bfef ]\u000a\u000aInvalid rate code is sent to firmware when multicast rate value of 0 is\u000asent to driver indicating disabled case, causing broken mesh path.\u000aso fix that.\u000a\u000aTested on QCA9984 with firmware 10.4-3.6.1-00827\u000a\u000aSven tested on IPQ4019 with 10.4-3.5.3-00057 and QCA9888 with 10.4-3.5.3-00053\u000a(ath10k-firmware) and 10.4-3.6-00140 (linux-firmware 2018-12-16-211de167).\u000a\u000aFixes: cd93b83ad92 (\"ath10k: support for multicast rate control\")\u000aCo-developed-by: Zhi Chen \u000aSigned-off-by: Zhi Chen \u000aSigned-off-by: Pradeep Kumar Chitrapu \u000aTested-by: Sven Eckelmann \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "fff1972f12f32f8e0f7fe5068911a248805229d0", "msg" : "ath10k: fix incorrect multicast/broadcast rate setting", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/mac.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath9k/xmit.c" ], "commitId" : "8091cfa7aa66b5a1569579a18b109e27c537793c", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath9k: Don't trust TX status TID number when reporting airtime\u000a\u000a[ Upstream commit 389b72e58259336c2d56d58b660b79cf4b9e0dcb ]\u000a\u000aAs already noted a comment in ath_tx_complete_aggr(), the hardware will\u000aoccasionally send a TX status with the wrong tid number. If we trust the\u000avalue, airtime usage will be reported to the wrong AC, which can cause the\u000adeficit on that AC to become very low, blocking subsequent attempts to\u000atransmit.\u000a\u000aTo fix this, account airtime usage to the TID number from the original skb,\u000ainstead of the one in the hardware TX status report.\u000a\u000aReported-by: Miguel Catalan Cid \u000aSigned-off-by: Toke Høiland-Jørgensen \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "8091cfa7aa66b5a1569579a18b109e27c537793c", "msg" : "ath9k: Don't trust TX status TID number when reporting airtime", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath9k/xmit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/wil6210/txrx.c" ], "commitId" : "03323a87f13a835501784caea3cdde84849723d0", "timestamp" : 1564125141000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "wil6210: fix potential out-of-bounds read\u000a\u000a[ Upstream commit bfabdd6997323adbedccb13a3fed1967fb8cf8f5 ]\u000a\u000aNotice that *rc* can evaluate to up to 5, include/linux/netdevice.h:\u000a\u000aenum gro_result {\u000a GRO_MERGED,\u000a GRO_MERGED_FREE,\u000a GRO_HELD,\u000a GRO_NORMAL,\u000a GRO_DROP,\u000a GRO_CONSUMED,\u000a};\u000atypedef enum gro_result gro_result_t;\u000a\u000aIn case *rc* evaluates to 5, we end up having an out-of-bounds read\u000aat drivers/net/wireless/ath/wil6210/txrx.c:821:\u000a\u000a\u0009wil_dbg_txrx(wil, \"Rx complete %d bytes => %s\\n\",\u000a\u0009\u0009 len, gro_res_str[rc]);\u000a\u000aFix this by adding element \"GRO_CONSUMED\" to array gro_res_str.\u000a\u000aAddresses-Coverity-ID: 1444666 (\"Out-of-bounds read\")\u000aFixes: 194b482b5055 (\"wil6210: Debug print GRO Rx result\")\u000aSigned-off-by: Gustavo A. R. Silva \u000aReviewed-by: Maya Erez \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:21 +0200", "id" : "03323a87f13a835501784caea3cdde84849723d0", "msg" : "wil6210: fix potential out-of-bounds read", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/wil6210/txrx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/mac.c" ], "commitId" : "a017f90a487379f9bcfbfbdd3fc07a41ab165dbc", "timestamp" : 1564125142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: Do not send probe response template for mesh\u000a\u000a[ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ]\u000a\u000aCurrently mac80211 do not support probe response template for\u000amesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host\u000adriver tries to configure probe response template for mesh, but\u000ait fails because the interface type is not NL80211_IFTYPE_AP but\u000aNL80211_IFTYPE_MESH_POINT.\u000a\u000aTo avoid this failure, skip sending probe response template to\u000afirmware for mesh point.\u000a\u000aTested HW: WCN3990/QCA6174/QCA9984\u000a\u000aSigned-off-by: Surabhi Vishnoi \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:22 +0200", "id" : "a017f90a487379f9bcfbfbdd3fc07a41ab165dbc", "msg" : "ath10k: Do not send probe response template for mesh", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/mac.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/spi/spi-rockchip.c" ], "commitId" : "aea21407374011f71a1233cdb7eca2e97d266b26", "timestamp" : 1564125142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "spi: rockchip: turn down tx dma bursts\u000a\u000a[ Upstream commit 47300728fb213486a830565d2af49da967c9d16a ]\u000a\u000aThis fixes tx and bi-directional dma transfers on rk3399-gru-kevin.\u000a\u000aIt seems the SPI fifo must have room for 2 bursts when the dma_tx_req\u000asignal is generated or it might skip some words. This in turn makes\u000athe rx dma channel never complete for bi-directional transfers.\u000a\u000aFix it by setting tx burst length to fifo_len / 4 and the dma\u000awatermark to fifo_len / 2.\u000a\u000aHowever the rk3399 TRM says (sic):\u000a\"DMAC support incrementing-address burst and fixed-address burst. But in\u000athe case of access SPI and UART at byte or halfword size, DMAC only\u000asupport fixed-address burst and the address must be aligned to word.\"\u000a\u000aSo this relies on fifo_len being a multiple of 16 such that the\u000aburst length (= fifo_len / 4) is a multiple of 4 and the addresses\u000awill be word-aligned.\u000a\u000aFixes: dcfc861d24ec (\"spi: rockchip: adjust dma watermark and burstlen\")\u000aSigned-off-by: Emil Renner Berthing \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:22 +0200", "id" : "aea21407374011f71a1233cdb7eca2e97d266b26", "msg" : "spi: rockchip: turn down tx dma bursts", "paths" : [ { "editType" : "edit", "file" : "drivers/spi/spi-rockchip.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath9k/hw.c" ], "commitId" : "b1e7cc224d4273f1ab60ed348a9ae3d9afbd4396", "timestamp" : 1564125142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath9k: Check for errors when reading SREV register\u000a\u000a[ Upstream commit 2f90c7e5d09437a4d8d5546feaae9f1cf48cfbe1 ]\u000a\u000aRight now, if an error is encountered during the SREV register\u000aread (i.e. an EIO in ath9k_regread()), that error code gets\u000apassed all the way to __ath9k_hw_init(), where it is visible\u000aduring the \"Chip rev not supported\" message.\u000a\u000a ath9k_htc 1-1.4:1.0: ath9k_htc: HTC initialized with 33 credits\u000a ath: phy2: Mac Chip Rev 0x0f.3 is not supported by this driver\u000a ath: phy2: Unable to initialize hardware; initialization status: -95\u000a ath: phy2: Unable to initialize hardware; initialization status: -95\u000a ath9k_htc: Failed to initialize the device\u000a\u000aCheck for -EIO explicitly in ath9k_hw_read_revisions() and return\u000aa boolean based on the success of the operation. Check for that in\u000a__ath9k_hw_init() and abort with a more debugging-friendly message\u000aif reading the revisions wasn't successful.\u000a\u000a ath9k_htc 1-1.4:1.0: ath9k_htc: HTC initialized with 33 credits\u000a ath: phy2: Failed to read SREV register\u000a ath: phy2: Could not read hardware revision\u000a ath: phy2: Unable to initialize hardware; initialization status: -95\u000a ath: phy2: Unable to initialize hardware; initialization status: -95\u000a ath9k_htc: Failed to initialize the device\u000a\u000aThis helps when debugging by directly showing the first point of\u000afailure and it could prevent possible errors if a 0x0f.3 revision\u000ais ever supported.\u000a\u000aSigned-off-by: Tim Schumacher \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:22 +0200", "id" : "b1e7cc224d4273f1ab60ed348a9ae3d9afbd4396", "msg" : "ath9k: Check for errors when reading SREV register", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath9k/hw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/wmi.h" ], "commitId" : "587ae5ef666a77837d289ac6edff735f3eb74a0c", "timestamp" : 1564125142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: Fix the wrong value of enums for wmi tlv stats id\u000a\u000a[ Upstream commit 9280f4fc06f44d0b4dc9e831f72d97b3d7cd35d3 ]\u000a\u000aThe enum value for WMI_TLV_STAT_PDEV, WMI_TLV_STAT_VDEV\u000aand WMI_TLV_STAT_PEER is wrong, due to which the vdev stats\u000aare not received from firmware in wmi_update_stats event.\u000a\u000aFix the enum values for above stats to receive all stats\u000afrom firmware in WMI_TLV_UPDATE_STATS_EVENTID.\u000a\u000aTested HW: WCN3990\u000aTested FW: WLAN.HL.3.1-00784-QCAHLSWMTPLZ-1\u000a\u000aFixes: f40a307eb92c (\"ath10k: Fill rx duration for each peer in fw_stats for WCN3990)\u000aSigned-off-by: Surabhi Vishnoi \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:22 +0200", "id" : "587ae5ef666a77837d289ac6edff735f3eb74a0c", "msg" : "ath10k: Fix the wrong value of enums for wmi tlv stats id", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/wmi.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/wil6210/interrupt.c" ], "commitId" : "5aa61f24821a73b889975b2e6cbac61216d867d5", "timestamp" : 1564125142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "wil6210: fix missed MISC mbox interrupt\u000a\u000a[ Upstream commit 7441be71ba7e07791fd4fa2b07c932dff14ff4d9 ]\u000a\u000aWhen MISC interrupt is triggered due to HALP bit, in parallel\u000ato mbox events handling by the MISC threaded IRQ, new mbox\u000ainterrupt can be missed in the following scenario:\u000a1. MISC ICR is read in the IRQ handler\u000a2. Threaded IRQ is completed and all MISC interrupts are unmasked\u000a3. mbox interrupt is set by FW\u000a4. HALP is masked\u000aThe mbox interrupt in step 3 can be missed due to constant high level\u000aof ICM.\u000aMasking all MISC IRQs instead of masking only HALP bit in step 4\u000awill guarantee that ICM will drop to 0 and interrupt will be triggered\u000aonce MISC interrupts will be unmasked.\u000a\u000aSigned-off-by: Maya Erez \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:22 +0200", "id" : "5aa61f24821a73b889975b2e6cbac61216d867d5", "msg" : "wil6210: fix missed MISC mbox interrupt", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/wil6210/interrupt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath6kl/wmi.c" ], "commitId" : "207cdbd6e299299fe442c1da0c0ece97c99b4b49", "timestamp" : 1564125142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath6kl: add some bounds checking\u000a\u000a[ Upstream commit 5d6751eaff672ea77642e74e92e6c0ac7f9709ab ]\u000a\u000aThe \"ev->traffic_class\" and \"reply->ac\" variables come from the network\u000aand they're used as an offset into the wmi->stream_exist_for_ac[] array.\u000aThose variables are u8 so they can be 0-255 but the stream_exist_for_ac[]\u000aarray only has WMM_NUM_AC (4) elements. We need to add a couple bounds\u000achecks to prevent array overflows.\u000a\u000aI also modified one existing check from \"if (traffic_class > 3) {\" to\u000a\"if (traffic_class >= WMM_NUM_AC) {\" just to make them all consistent.\u000a\u000aFixes: bdcd81707973 (\" Add ath6kl cleaned up driver\")\u000aSigned-off-by: Dan Carpenter \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:22 +0200", "id" : "207cdbd6e299299fe442c1da0c0ece97c99b4b49", "msg" : "ath6kl: add some bounds checking", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath6kl/wmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/txrx.c" ], "commitId" : "ffb9277b00bf91677eade49c021e9e8d9d67ab87", "timestamp" : 1564125143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: add peer id check in ath10k_peer_find_by_id\u000a\u000a[ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ]\u000a\u000aFor some SDIO chip, the peer id is 65535 for MPDU with error status,\u000athen test_bit will trigger buffer overflow for peer's memory, if kasan\u000aenabled, it will report error.\u000a\u000aReason is when station is in disconnecting status, firmware do not delete\u000athe peer info since it not disconnected completely, meanwhile some AP will\u000astill send data packet to station, then hardware will receive the packet\u000aand send to firmware, firmware's logic will report peer id of 65535 for\u000aMPDU with error status.\u000a\u000aAdd check for overflow the size of peer's peer_ids will avoid the buffer\u000aoverflow access.\u000a\u000aCall trace of kasan:\u000adump_backtrace+0x0/0x2ec\u000ashow_stack+0x20/0x2c\u000a__dump_stack+0x20/0x28\u000adump_stack+0xc8/0xec\u000aprint_address_description+0x74/0x240\u000akasan_report+0x250/0x26c\u000a__asan_report_load8_noabort+0x20/0x2c\u000aath10k_peer_find_by_id+0x180/0x1e4 [ath10k_core]\u000aath10k_htt_t2h_msg_handler+0x100c/0x2fd4 [ath10k_core]\u000aath10k_htt_htc_t2h_msg_handler+0x20/0x34 [ath10k_core]\u000aath10k_sdio_irq_handler+0xcc8/0x1678 [ath10k_sdio]\u000aprocess_sdio_pending_irqs+0xec/0x370\u000asdio_run_irqs+0x68/0xe4\u000asdio_irq_work+0x1c/0x28\u000aprocess_one_work+0x3d8/0x8b0\u000aworker_thread+0x508/0x7cc\u000akthread+0x24c/0x264\u000aret_from_fork+0x10/0x18\u000a\u000aTested with QCA6174 SDIO with firmware\u000aWLAN.RMH.4.4.1-00007-QCARMSWP-1.\u000a\u000aSigned-off-by: Wen Gong \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:23 +0200", "id" : "ffb9277b00bf91677eade49c021e9e8d9d67ab87", "msg" : "ath10k: add peer id check in ath10k_peer_find_by_id", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/txrx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/wil6210/interrupt.c" ], "commitId" : "2da6d47c24b63b57abe99f97e38f6a34b1b5cc73", "timestamp" : 1564125143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "wil6210: fix spurious interrupts in 3-msi\u000a\u000a[ Upstream commit e10b0eddd5235aa5aef4e40b970e34e735611a80 ]\u000a\u000aInterrupt is set in ICM (ICR & ~IMV) rising trigger.\u000aAs the driver masks the IRQ after clearing it, there can\u000abe a race where an additional spurious interrupt is triggered\u000awhen the driver unmask the IRQ.\u000aThis can happen in case HW triggers an interrupt after the clear\u000aand before the mask.\u000a\u000aTo prevent the second spurious interrupt the driver needs to mask the\u000aIRQ before reading and clearing it.\u000a\u000aSigned-off-by: Maya Erez \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:23 +0200", "id" : "2da6d47c24b63b57abe99f97e38f6a34b1b5cc73", "msg" : "wil6210: fix spurious interrupts in 3-msi", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/wil6210/interrupt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/dfs_pattern_detector.c" ], "commitId" : "140b0aaeb9d35afb355b124ad9f152c7d4c5ab95", "timestamp" : 1564125143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath: DFS JP domain W56 fixed pulse type 3 RADAR detection\u000a\u000a[ Upstream commit d8792393a783158cbb2c39939cb897dc5e5299b6 ]\u000a\u000aIncrease pulse width range from 1-2usec to 0-4usec.\u000aDuring data traffic HW occasionally fails detecting radar pulses,\u000aso that SW cannot get enough radar reports to achieve the success rate.\u000a\u000aTested ath10k hw and fw:\u000a\u0009* QCA9888(10.4-3.5.1-00052)\u000a\u0009* QCA4019(10.4-3.2.1.1-00017)\u000a\u0009* QCA9984(10.4-3.6-00104)\u000a\u0009* QCA988X(10.2.4-1.0-00041)\u000a\u000aTested ath9k hw: AR9300\u000a\u000aTested-by: Tamizh chelvam \u000aSigned-off-by: Tamizh chelvam \u000aSigned-off-by: Anilkumar Kolli \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:23 +0200", "id" : "140b0aaeb9d35afb355b124ad9f152c7d4c5ab95", "msg" : "ath: DFS JP domain W56 fixed pulse type 3 RADAR detection", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/dfs_pattern_detector.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/wmi-tlv.c" ], "commitId" : "cc381a13d79b2913bcf9b5d4608414dcb1ade142", "timestamp" : 1564125143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: Fix encoding for protected management frames\u000a\u000a[ Upstream commit 42f1bc43e6a97b9ddbe976eba9bd05306c990c75 ]\u000a\u000aCurrently the protected management frames are\u000anot appended with the MIC_LEN which results in\u000athe protected management frames being encoded\u000aincorrectly.\u000a\u000aAdd the extra space at the end of the protected\u000amanagement frames to fix this encoding error for\u000athe protected management frames.\u000a\u000aTested HW: WCN3990\u000aTested FW: WLAN.HL.3.1-00784-QCAHLSWMTPLZ-1\u000a\u000aFixes: 1807da49733e (\"ath10k: wmi: add management tx by reference support over wmi\")\u000aSigned-off-by: Rakesh Pillai \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:23 +0200", "id" : "cc381a13d79b2913bcf9b5d4608414dcb1ade142", "msg" : "ath10k: Fix encoding for protected management frames", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/wmi-tlv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/base/regmap/regmap-debugfs.c" ], "commitId" : "a179540c0f47da94705157215e38f8e83cd162e9", "timestamp" : 1564125143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "regmap: debugfs: Fix memory leak in regmap_debugfs_init\u000a\u000a[ Upstream commit 2899872b627e99b7586fe3b6c9f861da1b4d5072 ]\u000a\u000aAs detected by kmemleak running on i.MX6ULL board:\u000a\u000anreferenced object 0xd8366600 (size 64):\u000a comm \"swapper/0\", pid 1, jiffies 4294937370 (age 933.220s)\u000a hex dump (first 32 bytes):\u000a 64 75 6d 6d 79 2d 69 6f 6d 75 78 63 2d 67 70 72 dummy-iomuxc-gpr\u000a 40 32 30 65 34 30 30 30 00 e3 f3 ab fe d1 1b dd @20e4000........\u000a backtrace:\u000a [] kasprintf+0x2c/0x54\u000a [] regmap_debugfs_init+0x7c/0x31c\u000a [<9c8d91fa>] __regmap_init+0xb5c/0xcf4\u000a [<5b1c3d2a>] of_syscon_register+0x164/0x2c4\u000a [<596a5d80>] syscon_node_to_regmap+0x64/0x90\u000a [<49bd597b>] imx6ul_init_machine+0x34/0xa0\u000a [<250a4dac>] customize_machine+0x1c/0x30\u000a [<2d19fdaf>] do_one_initcall+0x7c/0x398\u000a [] kernel_init_freeable+0x328/0x448\u000a [<168c9101>] kernel_init+0x8/0x114\u000a [<913268aa>] ret_from_fork+0x14/0x20\u000a [] 0x0\u000a\u000aRoot cause is that map->debugfs_name is allocated using kasprintf\u000aand then the pointer is lost by assigning it other memory address.\u000a\u000aReported-by: Stefan Wahren \u000aSigned-off-by: Daniel Baluta \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:23 +0200", "id" : "a179540c0f47da94705157215e38f8e83cd162e9", "msg" : "regmap: debugfs: Fix memory leak in regmap_debugfs_init", "paths" : [ { "editType" : "edit", "file" : "drivers/base/regmap/regmap-debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/batman-adv/translation-table.c" ], "commitId" : "6c2ab28a434c00b091a5ab56b6cf96773ad74d92", "timestamp" : 1564125143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "batman-adv: fix for leaked TVLV handler.\u000a\u000a[ Upstream commit 17f78dd1bd624a4dd78ed5db3284a63ee807fcc3 ]\u000a\u000aA handler for BATADV_TVLV_ROAM was being registered when the\u000atranslation-table was initialized, but not unregistered when the\u000atranslation-table was freed. Unregister it.\u000a\u000aFixes: 122edaa05940 (\"batman-adv: tvlv - convert roaming adv packet to use tvlv unicast packets\")\u000aReported-by: syzbot+d454a826e670502484b8@syzkaller.appspotmail.com\u000aSigned-off-by: Jeremy Sowden \u000aSigned-off-by: Sven Eckelmann \u000aSigned-off-by: Simon Wunderlich \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:23 +0200", "id" : "6c2ab28a434c00b091a5ab56b6cf96773ad74d92", "msg" : "batman-adv: fix for leaked TVLV handler.", "paths" : [ { "editType" : "edit", "file" : "net/batman-adv/translation-table.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/usb/dvb-usb/dvb-usb-init.c" ], "commitId" : "d1b2021c98845fe4d32571f6e9e8432a7d63cd22", "timestamp" : 1564125144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: dvb: usb: fix use after free in dvb_usb_device_exit\u000a\u000a[ Upstream commit 6cf97230cd5f36b7665099083272595c55d72be7 ]\u000a\u000advb_usb_device_exit() frees and uses the device name in that order.\u000aFix by storing the name in a buffer before freeing it.\u000a\u000aSigned-off-by: Oliver Neukum \u000aReported-by: syzbot+26ec41e9f788b3eba396@syzkaller.appspotmail.com\u000aSigned-off-by: Sean Young \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:24 +0200", "id" : "d1b2021c98845fe4d32571f6e9e8432a7d63cd22", "msg" : "media: dvb: usb: fix use after free in dvb_usb_device_exit", "paths" : [ { "editType" : "edit", "file" : "drivers/media/usb/dvb-usb/dvb-usb-init.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/rc/ir-spi.c" ], "commitId" : "e22fd962ba473961d7efae87366ca3932cb6a47b", "timestamp" : 1564125144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: spi: IR LED: add missing of table registration\u000a\u000a[ Upstream commit 24e4cf770371df6ad49ed873f21618d9878f64c8 ]\u000a\u000aMODULE_DEVICE_TABLE(of, should be called to complete DT\u000aOF mathing mechanism and register it.\u000a\u000aBefore this patch:\u000amodinfo drivers/media/rc/ir-spi.ko | grep alias\u000a\u000aAfter this patch:\u000amodinfo drivers/media/rc/ir-spi.ko | grep alias\u000aalias: of:N*T*Cir-spi-ledC*\u000aalias: of:N*T*Cir-spi-led\u000a\u000aReported-by: Javier Martinez Canillas \u000aSigned-off-by: Daniel Gomez \u000aSigned-off-by: Sean Young \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:24 +0200", "id" : "e22fd962ba473961d7efae87366ca3932cb6a47b", "msg" : "media: spi: IR LED: add missing of table registration", "paths" : [ { "editType" : "edit", "file" : "drivers/media/rc/ir-spi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/talitos.c" ], "commitId" : "61a361dff48e398004b9c9b1b1766695d76ff242", "timestamp" : 1564125144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: talitos - fix skcipher failure due to wrong output IV\u000a\u000a[ Upstream commit 3e03e792865ae48b8cfc69a0b4d65f02f467389f ]\u000a\u000aSelftests report the following:\u000a\u000a[ 2.984845] alg: skcipher: cbc-aes-talitos encryption test failed (wrong output IV) on test vector 0, cfg=\"in-place\"\u000a[ 2.995377] 00000000: 3d af ba 42 9d 9e b4 30 b4 22 da 80 2c 9f ac 41\u000a[ 3.032673] alg: skcipher: cbc-des-talitos encryption test failed (wrong output IV) on test vector 0, cfg=\"in-place\"\u000a[ 3.043185] 00000000: fe dc ba 98 76 54 32 10\u000a[ 3.063238] alg: skcipher: cbc-3des-talitos encryption test failed (wrong output IV) on test vector 0, cfg=\"in-place\"\u000a[ 3.073818] 00000000: 7d 33 88 93 0f 93 b2 42\u000a\u000aThis above dumps show that the actual output IV is indeed the input IV.\u000aThis is due to the IV not being copied back into the request.\u000a\u000aThis patch fixes that.\u000a\u000aSigned-off-by: Christophe Leroy \u000aReviewed-by: Horia Geantă \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:24 +0200", "id" : "61a361dff48e398004b9c9b1b1766695d76ff242", "msg" : "crypto: talitos - fix skcipher failure due to wrong output IV", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/talitos.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/i2c/ov7740.c" ], "commitId" : "61273670bcefdcf1cc39a91293f7c8453a891247", "timestamp" : 1564125144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: ov7740: avoid invalid framesize setting\u000a\u000a[ Upstream commit 6e4ab830ac6d6a0d7cd7f87dc5d6536369bf24a8 ]\u000a\u000aIf the requested framesize by VIDIOC_SUBDEV_S_FMT is larger than supported\u000aframesizes, it causes an out of bounds array access and the resulting\u000aframesize is unexpected.\u000a\u000aAvoid out of bounds array access and select the default framesize.\u000a\u000aCc: Wenyou Yang \u000aCc: Eugen Hristev \u000aSigned-off-by: Akinobu Mita \u000aSigned-off-by: Sakari Ailus \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:24 +0200", "id" : "61273670bcefdcf1cc39a91293f7c8453a891247", "msg" : "media: ov7740: avoid invalid framesize setting", "paths" : [ { "editType" : "edit", "file" : "drivers/media/i2c/ov7740.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/marvell-ccic/mcam-core.c" ], "commitId" : "c515bd87f0f04ad8ebaa18cd615fdb6bb3e5c29a", "timestamp" : 1564125144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: marvell-ccic: fix DMA s/g desc number calculation\u000a\u000a[ Upstream commit 0c7aa32966dab0b8a7424e1b34c7f206817953ec ]\u000a\u000aThe commit d790b7eda953 (\"[media] vb2-dma-sg: move dma_(un)map_sg here\")\u000aleft dma_desc_nent unset. It previously contained the number of DMA\u000adescriptors as returned from dma_map_sg().\u000a\u000aWe can now (since the commit referred to above) obtain the same value from\u000athe sg_table and drop dma_desc_nent altogether.\u000a\u000aTested on OLPC XO-1.75 machine. Doesn't affect the OLPC XO-1's Cafe\u000adriver, since that one doesn't do DMA.\u000a\u000a[mchehab+samsung@kernel.org: fix a checkpatch warning]\u000a\u000aFixes: d790b7eda953 (\"[media] vb2-dma-sg: move dma_(un)map_sg here\")\u000aSigned-off-by: Lubomir Rintel \u000aSigned-off-by: Sakari Ailus \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:24 +0200", "id" : "c515bd87f0f04ad8ebaa18cd615fdb6bb3e5c29a", "msg" : "media: marvell-ccic: fix DMA s/g desc number calculation", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/marvell-ccic/mcam-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/davinci/vpss.c" ], "commitId" : "4b4abbe0560869452f1b00ec8b1677615814f751", "timestamp" : 1564125144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: vpss: fix a potential NULL pointer dereference\u000a\u000a[ Upstream commit e08f0761234def47961d3252eac09ccedfe4c6a0 ]\u000a\u000aIn case ioremap fails, the fix returns -ENOMEM to avoid NULL\u000apointer dereference.\u000a\u000aSigned-off-by: Kangjie Lu \u000aAcked-by: Lad, Prabhakar \u000aReviewed-by: Mukesh Ojha \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:24 +0200", "id" : "4b4abbe0560869452f1b00ec8b1677615814f751", "msg" : "media: vpss: fix a potential NULL pointer dereference", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/davinci/vpss.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/media-device.c" ], "commitId" : "5d7590c842ed2251f1332f944ba49e7adf60e87c", "timestamp" : 1564125145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: media_device_enum_links32: clean a reserved field\u000a\u000a[ Upstream commit f49308878d7202e07d8761238e01bd0e5fce2750 ]\u000a\u000aIn v4l2-compliance utility, test MEDIA_IOC_ENUM_ENTITIES\u000awill check whether reserved field of media_links_enum filled\u000awith zero.\u000a\u000aHowever, for 32 bit program, the reserved field is missing\u000acopy from kernel space to user space in media_device_enum_links32\u000afunction.\u000a\u000aThis patch adds the cleaning a reserved field logic in\u000amedia_device_enum_links32 function.\u000a\u000aSigned-off-by: Jungo Lin \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:25 +0200", "id" : "5d7590c842ed2251f1332f944ba49e7adf60e87c", "msg" : "media: media_device_enum_links32: clean a reserved field", "paths" : [ { "editType" : "edit", "file" : "drivers/media/media-device.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/qcom/venus/firmware.c" ], "commitId" : "dee89bf6129c58a738a02752150c37abbceab7dc", "timestamp" : 1564125145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: venus: firmware: fix leaked of_node references\u000a\u000a[ Upstream commit 2c41cc0be07b5ee2f1167f41cd8a86fc5b53d82c ]\u000a\u000aThe call to of_parse_phandle returns a node pointer with refcount\u000aincremented thus it must be explicitly decremented after the last\u000ausage.\u000a\u000aDetected by coccinelle with the following warnings:\u000adrivers/media/platform/qcom/venus/firmware.c:90:2-8: ERROR: missing of_node_put; acquired a node pointer with refcount incremented on line 82, but without a corresponding object release within this function.\u000adrivers/media/platform/qcom/venus/firmware.c:94:2-8: ERROR: missing of_node_put; acquired a node pointer with refcount incremented on line 82, but without a corresponding object release within this function.\u000adrivers/media/platform/qcom/venus/firmware.c:128:1-7: ERROR: missing of_node_put; acquired a node pointer with refcount incremented on line 82, but without a corresponding object release within this function.\u000a\u000aSigned-off-by: Wen Yang \u000aAcked-by: Stanimir Varbanov \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:25 +0200", "id" : "dee89bf6129c58a738a02752150c37abbceab7dc", "msg" : "media: venus: firmware: fix leaked of_node references", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/qcom/venus/firmware.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/caam/qi.c", "drivers/crypto/caam/caamalg.c", "drivers/crypto/caam/caamalg_qi.c", "drivers/crypto/caam/caamalg_qi2.c" ], "commitId" : "e941cdbde8fa8bb6fdd6b52dce4e4d7bafb7aeef", "timestamp" : 1564125145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: caam - avoid S/G table fetching for AEAD zero-length output\u000a\u000a[ Upstream commit dcd9c76e5a183af4f793beb5141efcd260b8d09f ]\u000a\u000aWhen enabling IOMMU support, the following issue becomes visible\u000ain the AEAD zero-length case.\u000a\u000aEven though the output sequence length is set to zero, the crypto engine\u000atries to prefetch 4 S/G table entries (since SGF bit is set\u000ain SEQ OUT PTR command - which is either generated in SW in case of\u000acaam/jr or in HW in case of caam/qi, caam/qi2).\u000aThe DMA read operation will trigger an IOMMU fault since the address in\u000athe SEQ OUT PTR is \"dummy\" (set to zero / not obtained via DMA API\u000amapping).\u000a\u000a1. In case of caam/jr, avoid the IOMMU fault by clearing the SGF bit\u000ain SEQ OUT PTR command.\u000a\u000a2. In case of caam/qi - setting address, bpid, length to zero for output\u000aentry in the compound frame has a special meaning (cf. CAAM RM):\u000a\"Output frame = Unspecified, Input address = Y. A unspecified frame is\u000aindicated by an unused SGT entry (an entry in which the Address, Length,\u000aand BPID fields are all zero). SEC obtains output buffers from BMan as\u000aprescribed by the preheader.\"\u000a\u000aSince no output buffers are needed, modify the preheader by setting\u000a(ABS = 1, ADDBUF = 0):\u000a-\"ABS = 1 means obtain the number of buffers in ADDBUF (0 or 1) from\u000athe pool POOL ID\"\u000a-ADDBUF: \"If ABS is set, ADD BUF specifies whether to allocate\u000aa buffer or not\"\u000a\u000a3. In case of caam/qi2, since engine:\u000a-does not support FLE[FMT]=2'b11 (\"unused\" entry) mentioned in DPAA2 RM\u000a-requires output entry to be present, even if not used\u000athe solution chosen is to leave output frame list entry zeroized.\u000a\u000aFixes: 763069ba49d3 (\"crypto: caam - handle zero-length AEAD output\")\u000aSigned-off-by: Horia Geantă \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:25 +0200", "id" : "e941cdbde8fa8bb6fdd6b52dce4e4d7bafb7aeef", "msg" : "crypto: caam - avoid S/G table fetching for AEAD zero-length output", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/caam/caamalg_qi2.c" }, { "editType" : "edit", "file" : "drivers/crypto/caam/caamalg_qi.c" }, { "editType" : "edit", "file" : "drivers/crypto/caam/qi.c" }, { "editType" : "edit", "file" : "drivers/crypto/caam/caamalg.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/dwmac1000_core.c" ], "commitId" : "d91f9a55338d8bd91c4ad91d485f3b3d103314ff", "timestamp" : 1564125145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: dwmac1000: Clear unused address entries\u000a\u000a[ Upstream commit 9463c445590091202659cdfdd44b236acadfbd84 ]\u000a\u000aIn case we don't use a given address entry we need to clear it because\u000ait could contain previous values that are no longer valid.\u000a\u000aFound out while running stmmac selftests.\u000a\u000aSigned-off-by: Jose Abreu \u000aCc: Joao Pinto \u000aCc: David S. Miller \u000aCc: Giuseppe Cavallaro \u000aCc: Alexandre Torgue \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:25 +0200", "id" : "d91f9a55338d8bd91c4ad91d485f3b3d103314ff", "msg" : "net: stmmac: dwmac1000: Clear unused address entries", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/dwmac1000_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c" ], "commitId" : "3249b4fbd1174bd21efbfed184b7dd0a5976ebca", "timestamp" : 1564125145000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: dwmac4/5: Clear unused address entries\u000a\u000a[ Upstream commit 0620ec6c62a5a07625b65f699adc5d1b90394ee6 ]\u000a\u000aIn case we don't use a given address entry we need to clear it because\u000ait could contain previous values that are no longer valid.\u000a\u000aFound out while running stmmac selftests.\u000a\u000aSigned-off-by: Jose Abreu \u000aCc: Joao Pinto \u000aCc: David S. Miller \u000aCc: Giuseppe Cavallaro \u000aCc: Alexandre Torgue \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:25 +0200", "id" : "3249b4fbd1174bd21efbfed184b7dd0a5976ebca", "msg" : "net: stmmac: dwmac4/5: Clear unused address entries", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c" ], "commitId" : "e30df349015a4449c037a2f15f72ab106fbc4ba8", "timestamp" : 1564125146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: Prevent missing interrupts when running NAPI\u000a\u000a[ Upstream commit a976ca79e23f13bff79c14e7266cea4a0ea51e67 ]\u000a\u000aWhen we trigger NAPI we are disabling interrupts but in case we receive\u000aor send a packet in the meantime, as interrupts are disabled, we will\u000amiss this event.\u000a\u000aTrigger both NAPI instances (RX and TX) when at least one event happens\u000aso that we don't miss any interrupts.\u000a\u000aSigned-off-by: Jose Abreu \u000aCc: Joao Pinto \u000aCc: David S. Miller \u000aCc: Giuseppe Cavallaro \u000aCc: Alexandre Torgue \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:26 +0200", "id" : "e30df349015a4449c037a2f15f72ab106fbc4ba8", "msg" : "net: stmmac: Prevent missing interrupts when running NAPI", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" ], "commitId" : "4c5213f8ef63a94dfb6fa5764dc54cf73c773292", "timestamp" : 1564125146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: initialize CPU reverse mapping\u000a\u000a[ Upstream commit ffab9691bcb2fe2594f4c38bfceb4d9685b93b87 ]\u000a\u000aAllocate CPU rmap and add entry for each irq. CPU rmap is\u000aused in aRFS to get the queue number of the rx completion\u000ainterrupts.\u000a\u000aIn additional, remove the calling of\u000airq_set_affinity_notifier() in hns3_nic_init_irq(), because\u000awe have registered notifier in irq_cpu_rmap_add() for each\u000avector, otherwise it may cause use-after-free issue.\u000a\u000aSigned-off-by: Jian Shen \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:26 +0200", "id" : "4c5213f8ef63a94dfb6fa5764dc54cf73c773292", "msg" : "net: hns3: initialize CPU reverse mapping", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/qlogic/qed/qed_dev.c", "drivers/net/ethernet/qlogic/qed/qed_rdma.c" ], "commitId" : "4cabf0943067e8f55df83c5a2ad6ec42a6a7b95e", "timestamp" : 1564125146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "qed: Set the doorbell address correctly\u000a\u000a[ Upstream commit 8366d520019f366fabd6c7a13032bdcd837e18d4 ]\u000a\u000aIn 100g mode the doorbell bar is united for both engines. Set\u000athe correct offset in the hwfn so that the doorbell returned\u000afor RoCE is in the affined hwfn.\u000a\u000aSigned-off-by: Ariel Elior \u000aSigned-off-by: Denis Bolotin \u000aSigned-off-by: Michal Kalderon \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:26 +0200", "id" : "4cabf0943067e8f55df83c5a2ad6ec42a6a7b95e", "msg" : "qed: Set the doorbell address correctly", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/qlogic/qed/qed_dev.c" }, { "editType" : "edit", "file" : "drivers/net/ethernet/qlogic/qed/qed_rdma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/pid_namespace.c" ], "commitId" : "a6ebedd095723002fcc863dec5f6ff3917569498", "timestamp" : 1564125146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "signal/pid_namespace: Fix reboot_pid_ns to use send_sig not force_sig\u000a\u000a[ Upstream commit f9070dc94542093fd516ae4ccea17ef46a4362c5 ]\u000a\u000aThe locking in force_sig_info is not prepared to deal with a task that\u000aexits or execs (as sighand may change). The is not a locking problem\u000ain force_sig as force_sig is only built to handle synchronous\u000aexceptions.\u000a\u000aFurther the function force_sig_info changes the signal state if the\u000asignal is ignored, or blocked or if SIGNAL_UNKILLABLE will prevent the\u000adelivery of the signal. The signal SIGKILL can not be ignored and can\u000anot be blocked and SIGNAL_UNKILLABLE won't prevent it from being\u000adelivered.\u000a\u000aSo using force_sig rather than send_sig for SIGKILL is confusing\u000aand pointless.\u000a\u000aBecause it won't impact the sending of the signal and and because\u000ausing force_sig is wrong, replace force_sig with send_sig.\u000a\u000aCc: Daniel Lezcano \u000aCc: Serge Hallyn \u000aCc: Oleg Nesterov \u000aFixes: cf3f89214ef6 (\"pidns: add reboot_pid_ns() to handle the reboot syscall\")\u000aSigned-off-by: \"Eric W. Biederman\" \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:26 +0200", "id" : "a6ebedd095723002fcc863dec5f6ff3917569498", "msg" : "signal/pid_namespace: Fix reboot_pid_ns to use send_sig not force_sig", "paths" : [ { "editType" : "edit", "file" : "kernel/pid_namespace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/key/af_key.c" ], "commitId" : "ed83cefc26e63391fd4ff245653361fb6d637a8f", "timestamp" : 1564125146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "af_key: fix leaks in key_pol_get_resp and dump_sp.\u000a\u000a[ Upstream commit 7c80eb1c7e2b8420477fbc998971d62a648035d9 ]\u000a\u000aIn both functions, if pfkey_xfrm_policy2msg failed we leaked the newly\u000aallocated sk_buff. Free it on error.\u000a\u000aFixes: 55569ce256ce (\"Fix conversion between IPSEC_MODE_xxx and XFRM_MODE_xxx.\")\u000aReported-by: syzbot+4f0529365f7f2208d9f0@syzkaller.appspotmail.com\u000aSigned-off-by: Jeremy Sowden \u000aSigned-off-by: Steffen Klassert \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:26 +0200", "id" : "ed83cefc26e63391fd4ff245653361fb6d637a8f", "msg" : "af_key: fix leaks in key_pol_get_resp and dump_sp.", "paths" : [ { "editType" : "edit", "file" : "net/key/af_key.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/xfrm/xfrm_user.c" ], "commitId" : "191e0df41416442b5d33f95f79c4455d2a0f5485", "timestamp" : 1564125146000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xfrm: Fix xfrm sel prefix length validation\u000a\u000a[ Upstream commit b38ff4075a80b4da5cb2202d7965332ca0efb213 ]\u000a\u000aFamily of src/dst can be different from family of selector src/dst.\u000aUse xfrm selector family to validate address prefix length,\u000awhile verifying new sa from userspace.\u000a\u000aValidated patch with this command:\u000aip xfrm state add src 1.1.6.1 dst 1.1.6.2 proto esp spi 4260196 \\\u000areqid 20004 mode tunnel aead \"rfc4106(gcm(aes))\" \\\u000a0x1111016400000000000000000000000044440001 128 \\\u000asel src 1011:1:4::2/128 sel dst 1021:1:4::2/128 dev Port5\u000a\u000aFixes: 07bf7908950a (\"xfrm: Validate address prefix lengths in the xfrm selector.\")\u000aSigned-off-by: Anirudh Gupta \u000aAcked-by: Herbert Xu \u000aSigned-off-by: Steffen Klassert \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:26 +0200", "id" : "191e0df41416442b5d33f95f79c4455d2a0f5485", "msg" : "xfrm: Fix xfrm sel prefix length validation", "paths" : [ { "editType" : "edit", "file" : "net/xfrm/xfrm_user.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/vim2m.c" ], "commitId" : "f2bbf16739301267fbcb1d8669f7408d9e968aee", "timestamp" : 1564125147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: vim2m: fix two double-free issues\u000a\u000a[ Upstream commit 20059cbbf981ca954be56f7963ae494d18e2dda1 ]\u000a\u000avim2m_device_release() will be called by video_unregister_device() to release\u000avarious objects.\u000a\u000aThere are two double-free issue,\u000a1. dev->m2m_dev will be freed twice in error_m2m path/vim2m_device_release\u000a2. the error_v4l2 and error_free path in vim2m_probe() will release\u000a same objects, since vim2m_device_release has done.\u000a\u000aFixes: ea6c7e34f3b2 (\"media: vim2m: replace devm_kzalloc by kzalloc\")\u000a\u000aCc: Laurent Pinchart \u000aReported-by: Hulk Robot \u000aSigned-off-by: Kefeng Wang \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:27 +0200", "id" : "f2bbf16739301267fbcb1d8669f7408d9e968aee", "msg" : "media: vim2m: fix two double-free issues", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/vim2m.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/v4l2-core/v4l2-ctrls.c" ], "commitId" : "bcf628be4a69c4ee4ed55f51ebaff8c565d4daa0", "timestamp" : 1564125147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: v4l2-core: fix use-after-free error\u000a\u000a[ Upstream commit 3e0f724346e96daae7792262c6767449795ac3b5 ]\u000a\u000aFixing use-after-free within __v4l2_ctrl_handler_setup().\u000aMemory is being freed with kfree(new_ref) for duplicate\u000acontrol reference entry but ctrl->cluster pointer is still\u000areferring to freed duplicate entry resulting in error on\u000aaccess. Change done to update cluster pointer only when new\u000acontrol reference is added.\u000a\u000a ==================================================================\u000a BUG: KASAN: use-after-free in __v4l2_ctrl_handler_setup+0x388/0x428\u000a Read of size 8 at addr ffffffc324e78618 by task systemd-udevd/312\u000a\u000a Allocated by task 312:\u000a\u000a Freed by task 312:\u000a\u000a The buggy address belongs to the object at ffffffc324e78600\u000a which belongs to the cache kmalloc-64 of size 64\u000a The buggy address is located 24 bytes inside of\u000a 64-byte region [ffffffc324e78600, ffffffc324e78640)\u000a The buggy address belongs to the page:\u000a page:ffffffbf0c939e00 count:1 mapcount:0 mapping:\u000a\u0009\u0009\u0009\u0009\u0009(null) index:0xffffffc324e78f80\u000a flags: 0x4000000000000100(slab)\u000a raw: 4000000000000100 0000000000000000 ffffffc324e78f80 000000018020001a\u000a raw: 0000000000000000 0000000100000001 ffffffc37040fb80 0000000000000000\u000a page dumped because: kasan: bad access detected\u000a\u000a Memory state around the buggy address:\u000a ffffffc324e78500: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\u000a ffffffc324e78580: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\u000a >ffffffc324e78600: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\u000a ^\u000a ffffffc324e78680: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\u000a ffffffc324e78700: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc\u000a ==================================================================\u000a\u000aSuggested-by: Hans Verkuil \u000aSigned-off-by: Sumit Gupta \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:27 +0200", "id" : "bcf628be4a69c4ee4ed55f51ebaff8c565d4daa0", "msg" : "media: v4l2-core: fix use-after-free error", "paths" : [ { "editType" : "edit", "file" : "drivers/media/v4l2-core/v4l2-ctrls.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/crypto/crypto.c" ], "commitId" : "2bff4642593c618e711e8f152b5d9950564c2fe9", "timestamp" : 1564125147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "fscrypt: clean up some BUG_ON()s in block encryption/decryption\u000a\u000a[ Upstream commit eeacfdc68a104967162dfcba60f53f6f5b62a334 ]\u000a\u000aReplace some BUG_ON()s with WARN_ON_ONCE() and returning an error code,\u000aand move the check for len divisible by FS_CRYPTO_BLOCK_SIZE into\u000afscrypt_crypt_block() so that it's done for both encryption and\u000adecryption, not just encryption.\u000a\u000aReviewed-by: Chandan Rajendra \u000aSigned-off-by: Eric Biggers \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:27 +0200", "id" : "2bff4642593c618e711e8f152b5d9950564c2fe9", "msg" : "fscrypt: clean up some BUG_ON()s in block encryption/decryption", "paths" : [ { "editType" : "edit", "file" : "fs/crypto/crypto.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/usb/zr364xx/zr364xx.c" ], "commitId" : "dbabee0cac1e3c5502ed0e9298226d81ca71a441", "timestamp" : 1564125147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: usb:zr364xx:Fix KASAN:null-ptr-deref Read in zr364xx_vidioc_querycap\u000a\u000a[ Upstream commit 5d2e73a5f80a5b5aff3caf1ec6d39b5b3f54b26e ]\u000a\u000aSyzKaller hit the null pointer deref while reading from uninitialized\u000audev->product in zr364xx_vidioc_querycap().\u000a\u000a==================================================================\u000aBUG: KASAN: null-ptr-deref in read_word_at_a_time+0xe/0x20\u000ainclude/linux/compiler.h:274\u000aRead of size 1 at addr 0000000000000000 by task v4l_id/5287\u000a\u000aCPU: 1 PID: 5287 Comm: v4l_id Not tainted 5.1.0-rc3-319004-g43151d6 #6\u000aHardware name: Google Google Compute Engine/Google Compute Engine, BIOS\u000aGoogle 01/01/2011\u000aCall Trace:\u000a __dump_stack lib/dump_stack.c:77 [inline]\u000a dump_stack+0xe8/0x16e lib/dump_stack.c:113\u000a kasan_report.cold+0x5/0x3c mm/kasan/report.c:321\u000a read_word_at_a_time+0xe/0x20 include/linux/compiler.h:274\u000a strscpy+0x8a/0x280 lib/string.c:207\u000a zr364xx_vidioc_querycap+0xb5/0x210 drivers/media/usb/zr364xx/zr364xx.c:706\u000a v4l_querycap+0x12b/0x340 drivers/media/v4l2-core/v4l2-ioctl.c:1062\u000a __video_do_ioctl+0x5bb/0xb40 drivers/media/v4l2-core/v4l2-ioctl.c:2874\u000a video_usercopy+0x44e/0xf00 drivers/media/v4l2-core/v4l2-ioctl.c:3056\u000a v4l2_ioctl+0x14e/0x1a0 drivers/media/v4l2-core/v4l2-dev.c:364\u000a vfs_ioctl fs/ioctl.c:46 [inline]\u000a file_ioctl fs/ioctl.c:509 [inline]\u000a do_vfs_ioctl+0xced/0x12f0 fs/ioctl.c:696\u000a ksys_ioctl+0xa0/0xc0 fs/ioctl.c:713\u000a __do_sys_ioctl fs/ioctl.c:720 [inline]\u000a __se_sys_ioctl fs/ioctl.c:718 [inline]\u000a __x64_sys_ioctl+0x74/0xb0 fs/ioctl.c:718\u000a do_syscall_64+0xcf/0x4f0 arch/x86/entry/common.c:290\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000aRIP: 0033:0x7f3b56d8b347\u000aCode: 90 90 90 48 8b 05 f1 fa 2a 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff\u000aff c3 90 90 90 90 90 90 90 90 90 90 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff\u000aff 73 01 c3 48 8b 0d c1 fa 2a 00 31 d2 48 29 c2 64\u000aRSP: 002b:00007ffe005d5d68 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\u000aRAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f3b56d8b347\u000aRDX: 00007ffe005d5d70 RSI: 0000000080685600 RDI: 0000000000000003\u000aRBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\u000aR10: 0000000000000000 R11: 0000000000000202 R12: 0000000000400884\u000aR13: 00007ffe005d5ec0 R14: 0000000000000000 R15: 0000000000000000\u000a==================================================================\u000a\u000aFor this device udev->product is not initialized and accessing it causes a NULL pointer deref.\u000a\u000aThe fix is to check for NULL before strscpy() and copy empty string, if\u000aproduct is NULL\u000a\u000aReported-by: syzbot+66010012fd4c531a1a96@syzkaller.appspotmail.com\u000aSigned-off-by: Vandana BN \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:27 +0200", "id" : "dbabee0cac1e3c5502ed0e9298226d81ca71a441", "msg" : "media: usb:zr364xx:Fix KASAN:null-ptr-deref Read in zr364xx_vidioc_querycap", "paths" : [ { "editType" : "edit", "file" : "drivers/media/usb/zr364xx/zr364xx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/ui/browsers/annotate.c" ], "commitId" : "341b1fa4f0795a9250ee7647b3529c92a8431f5f", "timestamp" : 1564125147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf annotate TUI browser: Do not use member from variable within its own initialization\u000a\u000a[ Upstream commit da2019633f0b5c105ce658aada333422d8cb28fe ]\u000a\u000aSome compilers will complain when using a member of a struct to\u000ainitialize another member, in the same struct initialization.\u000a\u000aFor instance:\u000a\u000a debian:8 Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on LLVM 3.5.0)\u000a oraclelinux:7 clang version 3.4.2 (tags/RELEASE_34/dot2-final)\u000a\u000aProduce:\u000a\u000a ui/browsers/annotate.c:104:12: error: variable 'ops' is uninitialized when used within its own initialization [-Werror,-Wuninitialized]\u000a (!ops.current_entry ||\u000a ^~~\u000a 1 error generated.\u000a\u000aSo use an extra variable, initialized just before that struct, to have\u000athe value used in the expressions used to init two of the struct\u000amembers.\u000a\u000aCc: Adrian Hunter \u000aCc: Jiri Olsa \u000aCc: Namhyung Kim \u000aFixes: c298304bd747 (\"perf annotate: Use a ops table for annotation_line__write()\")\u000aLink: https://lkml.kernel.org/n/tip-f9nexro58q62l3o9hez8hr0i@git.kernel.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:27 +0200", "id" : "341b1fa4f0795a9250ee7647b3529c92a8431f5f", "msg" : "perf annotate TUI browser: Do not use member from variable within its own initialization", "paths" : [ { "editType" : "edit", "file" : "tools/perf/ui/browsers/annotate.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/media-device.c" ], "commitId" : "7816f742a1ce444ee0eebf970c76a7a12abec514", "timestamp" : 1564125147000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: mc-device.c: don't memset __user pointer contents\u000a\u000a[ Upstream commit 518fa4e0e0da97ea2e17c95ab57647ce748a96e2 ]\u000a\u000aYou can't memset the contents of a __user pointer. Instead, call copy_to_user to\u000acopy links.reserved (which is zeroed) to the user memory.\u000a\u000aThis fixes this sparse warning:\u000a\u000aSPARSE:drivers/media/mc/mc-device.c drivers/media/mc/mc-device.c:521:16: warning: incorrect type in argument 1 (different address spaces)\u000a\u000aFixes: f49308878d720 (\"media: media_device_enum_links32: clean a reserved field\")\u000a\u000aSigned-off-by: Hans Verkuil \u000aReviewed-by: Sakari Ailus \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:27 +0200", "id" : "7816f742a1ce444ee0eebf970c76a7a12abec514", "msg" : "media: mc-device.c: don't memset __user pointer contents", "paths" : [ { "editType" : "edit", "file" : "drivers/media/media-device.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/pci/saa7164/saa7164-core.c" ], "commitId" : "139f99f55fd2de1f3c2c7747cf26716cddec0b5b", "timestamp" : 1564125148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: saa7164: fix remove_proc_entry warning\u000a\u000a[ Upstream commit 50710eeefbc1ed25375942aad0c4d1eb4af0f330 ]\u000a\u000aif saa7164_proc_create() fails, saa7164_fini() will trigger a warning,\u000a\u000aname 'saa7164'\u000aWARNING: CPU: 1 PID: 6311 at fs/proc/generic.c:672 remove_proc_entry+0x1e8/0x3a0\u000a ? remove_proc_entry+0x1e8/0x3a0\u000a ? try_stop_module+0x7b/0x240\u000a ? proc_readdir+0x70/0x70\u000a ? rcu_read_lock_sched_held+0xd7/0x100\u000a saa7164_fini+0x13/0x1f [saa7164]\u000a __x64_sys_delete_module+0x30c/0x480\u000a ? __ia32_sys_delete_module+0x480/0x480\u000a ? __x64_sys_clock_gettime+0x11e/0x1c0\u000a ? __x64_sys_timer_create+0x1a0/0x1a0\u000a ? trace_hardirqs_off_caller+0x40/0x180\u000a ? do_syscall_64+0x18/0x450\u000a do_syscall_64+0x9f/0x450\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a\u000aFix it by checking the return of proc_create_single() before\u000acalling remove_proc_entry().\u000a\u000aSigned-off-by: Kefeng Wang \u000aSigned-off-by: Hans Verkuil \u000a[hverkuil-cisco@xs4all.nl: use 0444 instead of S_IRUGO]\u000a[hverkuil-cisco@xs4all.nl: use pr_info instead of KERN_INFO]\u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:28 +0200", "id" : "139f99f55fd2de1f3c2c7747cf26716cddec0b5b", "msg" : "media: saa7164: fix remove_proc_entry warning", "paths" : [ { "editType" : "edit", "file" : "drivers/media/pci/saa7164/saa7164-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/media/davinci_vpfe/vpfe_video.c" ], "commitId" : "8e53ed20240e99fd5a0e11346114378333853209", "timestamp" : 1564125148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: staging: media: davinci_vpfe: - Fix for memory leak if decoder initialization fails.\u000a\u000a[ Upstream commit 6995a659101bd4effa41cebb067f9dc18d77520d ]\u000a\u000aFix to avoid possible memory leak if the decoder initialization\u000agot failed.Free the allocated memory for file handle object\u000abefore return in case decoder initialization fails.\u000a\u000aSigned-off-by: Shailendra Verma \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:28 +0200", "id" : "8e53ed20240e99fd5a0e11346114378333853209", "msg" : "media: staging: media: davinci_vpfe: - Fix for memory leak if decoder initialization fails.", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/media/davinci_vpfe/vpfe_video.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/phy/phy_device.c" ], "commitId" : "8db10b192f96deb625f202013b0b0c6051f19031", "timestamp" : 1564125148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: phy: Check against net_device being NULL\u000a\u000a[ Upstream commit 82c76aca81187b3d28a6fb3062f6916450ce955e ]\u000a\u000aIn general, we don't want MAC drivers calling phy_attach_direct with the\u000anet_device being NULL. Add checks against this in all the functions\u000acalling it: phy_attach() and phy_connect_direct().\u000a\u000aSigned-off-by: Ioana Ciornei \u000aSuggested-by: Andrew Lunn \u000aReviewed-by: Andrew Lunn \u000aReviewed-by: Florian Fainelli \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:28 +0200", "id" : "8db10b192f96deb625f202013b0b0c6051f19031", "msg" : "net: phy: Check against net_device being NULL", "paths" : [ { "editType" : "edit", "file" : "drivers/net/phy/phy_device.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/talitos.c" ], "commitId" : "01f8f49d5350614c34ce4592677294bf89de93e4", "timestamp" : 1564125148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: talitos - properly handle split ICV.\u000a\u000a[ Upstream commit eae55a586c3c8b50982bad3c3426e9c9dd7a0075 ]\u000a\u000aThe driver assumes that the ICV is as a single piece in the last\u000aelement of the scatterlist. This assumption is wrong.\u000a\u000aThis patch ensures that the ICV is properly handled regardless of\u000athe scatterlist layout.\u000a\u000aFixes: 9c4a79653b35 (\"crypto: talitos - Freescale integrated security engine (SEC) driver\")\u000aSigned-off-by: Christophe Leroy \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:28 +0200", "id" : "01f8f49d5350614c34ce4592677294bf89de93e4", "msg" : "crypto: talitos - properly handle split ICV.", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/talitos.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/talitos.c" ], "commitId" : "e96316e561e872359b6e0f0951ac2864de4d58e1", "timestamp" : 1564125148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: talitos - Align SEC1 accesses to 32 bits boundaries.\u000a\u000a[ Upstream commit c9cca7034b34a2d82e9a03b757de2485c294851c ]\u000a\u000aThe MPC885 reference manual states:\u000a\u000aSEC Lite-initiated 8xx writes can occur only on 32-bit-word boundaries, but\u000areads can occur on any byte boundary. Writing back a header read from a\u000anon-32-bit-word boundary will yield unpredictable results.\u000a\u000aIn order to ensure that, cra_alignmask is set to 3 for SEC1.\u000a\u000aSigned-off-by: Christophe Leroy \u000aFixes: 9c4a79653b35 (\"crypto: talitos - Freescale integrated security engine (SEC) driver\")\u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:28 +0200", "id" : "e96316e561e872359b6e0f0951ac2864de4d58e1", "msg" : "crypto: talitos - Align SEC1 accesses to 32 bits boundaries.", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/talitos.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/dvb-frontends/tua6100.c" ], "commitId" : "6d4ed7919ae33a6604ee650f754a49a77a44619d", "timestamp" : 1564125148000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tua6100: Avoid build warnings.\u000a\u000a[ Upstream commit 621ccc6cc5f8d6730b740d31d4818227866c93c9 ]\u000a\u000aRename _P to _P_VAL and _R to _R_VAL to avoid global\u000anamespace conflicts:\u000a\u000adrivers/media/dvb-frontends/tua6100.c: In function ‘tua6100_set_params’:\u000adrivers/media/dvb-frontends/tua6100.c:79: warning: \"_P\" redefined\u000a #define _P 32\u000a\u000aIn file included from ./include/acpi/platform/aclinux.h:54,\u000a from ./include/acpi/platform/acenv.h:152,\u000a from ./include/acpi/acpi.h:22,\u000a from ./include/linux/acpi.h:34,\u000a from ./include/linux/i2c.h:17,\u000a from drivers/media/dvb-frontends/tua6100.h:30,\u000a from drivers/media/dvb-frontends/tua6100.c:32:\u000a./include/linux/ctype.h:14: note: this is the location of the previous definition\u000a #define _P 0x10 /* punct */\u000a\u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:28 +0200", "id" : "6d4ed7919ae33a6604ee650f754a49a77a44619d", "msg" : "tua6100: Avoid build warnings.", "paths" : [ { "editType" : "edit", "file" : "drivers/media/dvb-frontends/tua6100.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/batman-adv/hard-interface.c", "net/batman-adv/types.h", "net/batman-adv/bat_iv_ogm.c" ], "commitId" : "a2b46e78fa4c60142477626b4be53001f7d7a79b", "timestamp" : 1564125149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "batman-adv: Fix duplicated OGMs on NETDEV_UP\u000a\u000a[ Upstream commit 9e6b5648bbc4cd48fab62cecbb81e9cc3c6e7e88 ]\u000a\u000aThe state of slave interfaces are handled differently depending on whether\u000athe interface is up or not. All active interfaces (IFF_UP) will transmit\u000aOGMs. But for B.A.T.M.A.N. IV, also non-active interfaces are scheduling\u000a(low TTL) OGMs on active interfaces. The code which setups and schedules\u000athe OGMs must therefore already be called when the interfaces gets added as\u000aslave interface and the transmit function must then check whether it has to\u000asend out the OGM or not on the specific slave interface.\u000a\u000aBut the commit f0d97253fb5f (\"batman-adv: remove ogm_emit and ogm_schedule\u000aAPI calls\") moved the setup code from the enable function to the activate\u000afunction. The latter is called either when the added slave was already up\u000awhen batadv_hardif_enable_interface processed the new interface or when a\u000aNETDEV_UP event was received for this slave interfac. As result, each\u000aNETDEV_UP would schedule a new OGM worker for the interface and thus OGMs\u000awould be send a lot more than expected.\u000a\u000aFixes: f0d97253fb5f (\"batman-adv: remove ogm_emit and ogm_schedule API calls\")\u000aReported-by: Linus Lüssing \u000aTested-by: Linus Lüssing \u000aAcked-by: Marek Lindner \u000aSigned-off-by: Sven Eckelmann \u000aSigned-off-by: Simon Wunderlich \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:29 +0200", "id" : "a2b46e78fa4c60142477626b4be53001f7d7a79b", "msg" : "batman-adv: Fix duplicated OGMs on NETDEV_UP", "paths" : [ { "editType" : "edit", "file" : "net/batman-adv/bat_iv_ogm.c" }, { "editType" : "edit", "file" : "net/batman-adv/types.h" }, { "editType" : "edit", "file" : "net/batman-adv/hard-interface.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/locking/lockdep.c" ], "commitId" : "90b05e4ee4f6d40d2ee69aa899e0a6c99a36cb82", "timestamp" : 1564125149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "locking/lockdep: Fix OOO unlock when hlocks need merging\u000a\u000a[ Upstream commit 8c8889d8eaf4501ae4aaf870b6f8f55db5d5109a ]\u000a\u000aThe sequence\u000a\u000a\u0009static DEFINE_WW_CLASS(test_ww_class);\u000a\u000a\u0009struct ww_acquire_ctx ww_ctx;\u000a\u0009struct ww_mutex ww_lock_a;\u000a\u0009struct ww_mutex ww_lock_b;\u000a\u0009struct mutex lock_c;\u000a\u0009struct mutex lock_d;\u000a\u000a\u0009ww_acquire_init(&ww_ctx, &test_ww_class);\u000a\u000a\u0009ww_mutex_init(&ww_lock_a, &test_ww_class);\u000a\u0009ww_mutex_init(&ww_lock_b, &test_ww_class);\u000a\u000a\u0009mutex_init(&lock_c);\u000a\u000a\u0009ww_mutex_lock(&ww_lock_a, &ww_ctx);\u000a\u000a\u0009mutex_lock(&lock_c);\u000a\u000a\u0009ww_mutex_lock(&ww_lock_b, &ww_ctx);\u000a\u000a\u0009mutex_unlock(&lock_c);\u0009\u0009(*)\u000a\u000a\u0009ww_mutex_unlock(&ww_lock_b);\u000a\u0009ww_mutex_unlock(&ww_lock_a);\u000a\u000a\u0009ww_acquire_fini(&ww_ctx);\u000a\u000atriggers the following WARN in __lock_release() when doing the unlock at *:\u000a\u000a\u0009DEBUG_LOCKS_WARN_ON(curr->lockdep_depth != depth - 1);\u000a\u000aThe problem is that the WARN check doesn't take into account the merging\u000aof ww_lock_a and ww_lock_b which results in decreasing curr->lockdep_depth\u000aby 2 not only 1.\u000a\u000aNote that the following sequence doesn't trigger the WARN, since there\u000awon't be any hlock merging.\u000a\u000a\u0009ww_acquire_init(&ww_ctx, &test_ww_class);\u000a\u000a\u0009ww_mutex_init(&ww_lock_a, &test_ww_class);\u000a\u0009ww_mutex_init(&ww_lock_b, &test_ww_class);\u000a\u000a\u0009mutex_init(&lock_c);\u000a\u0009mutex_init(&lock_d);\u000a\u000a\u0009ww_mutex_lock(&ww_lock_a, &ww_ctx);\u000a\u000a\u0009mutex_lock(&lock_c);\u000a\u0009mutex_lock(&lock_d);\u000a\u000a\u0009ww_mutex_lock(&ww_lock_b, &ww_ctx);\u000a\u000a\u0009mutex_unlock(&lock_d);\u000a\u000a\u0009ww_mutex_unlock(&ww_lock_b);\u000a\u0009ww_mutex_unlock(&ww_lock_a);\u000a\u000a\u0009mutex_unlock(&lock_c);\u000a\u000a\u0009ww_acquire_fini(&ww_ctx);\u000a\u000aIn general both of the above two sequences are valid and shouldn't\u000atrigger any lockdep warning.\u000a\u000aFix this by taking the decrement due to the hlock merging into account\u000aduring lock release and hlock class re-setting. Merging can't happen\u000aduring lock downgrading since there won't be a new possibility to merge\u000ahlocks in that case, so add a WARN if merging still happens then.\u000a\u000aSigned-off-by: Imre Deak \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aCc: Will Deacon \u000aCc: ville.syrjala@linux.intel.com\u000aLink: https://lkml.kernel.org/r/20190524201509.9199-1-imre.deak@intel.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:29 +0200", "id" : "90b05e4ee4f6d40d2ee69aa899e0a6c99a36cb82", "msg" : "locking/lockdep: Fix OOO unlock when hlocks need merging", "paths" : [ { "editType" : "edit", "file" : "kernel/locking/lockdep.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/locking/lockdep.c" ], "commitId" : "3e6d03e7a5a2668c27b86797ce0bb0dc6699dbc4", "timestamp" : 1564125149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "locking/lockdep: Fix merging of hlocks with non-zero references\u000a\u000a[ Upstream commit d9349850e188b8b59e5322fda17ff389a1c0cd7d ]\u000a\u000aThe sequence\u000a\u000a\u0009static DEFINE_WW_CLASS(test_ww_class);\u000a\u000a\u0009struct ww_acquire_ctx ww_ctx;\u000a\u0009struct ww_mutex ww_lock_a;\u000a\u0009struct ww_mutex ww_lock_b;\u000a\u0009struct ww_mutex ww_lock_c;\u000a\u0009struct mutex lock_c;\u000a\u000a\u0009ww_acquire_init(&ww_ctx, &test_ww_class);\u000a\u000a\u0009ww_mutex_init(&ww_lock_a, &test_ww_class);\u000a\u0009ww_mutex_init(&ww_lock_b, &test_ww_class);\u000a\u0009ww_mutex_init(&ww_lock_c, &test_ww_class);\u000a\u000a\u0009mutex_init(&lock_c);\u000a\u000a\u0009ww_mutex_lock(&ww_lock_a, &ww_ctx);\u000a\u000a\u0009mutex_lock(&lock_c);\u000a\u000a\u0009ww_mutex_lock(&ww_lock_b, &ww_ctx);\u000a\u0009ww_mutex_lock(&ww_lock_c, &ww_ctx);\u000a\u000a\u0009mutex_unlock(&lock_c);\u0009(*)\u000a\u000a\u0009ww_mutex_unlock(&ww_lock_c);\u000a\u0009ww_mutex_unlock(&ww_lock_b);\u000a\u0009ww_mutex_unlock(&ww_lock_a);\u000a\u000a\u0009ww_acquire_fini(&ww_ctx); (**)\u000a\u000awill trigger the following error in __lock_release() when calling\u000amutex_release() at **:\u000a\u000a\u0009DEBUG_LOCKS_WARN_ON(depth <= 0)\u000a\u000aThe problem is that the hlock merging happening at * updates the\u000areferences for test_ww_class incorrectly to 3 whereas it should've\u000aupdated it to 4 (representing all the instances for ww_ctx and\u000aww_lock_[abc]).\u000a\u000aFix this by updating the references during merging correctly taking into\u000aaccount that we can have non-zero references (both for the hlock that we\u000amerge into another hlock or for the hlock we are merging into).\u000a\u000aSigned-off-by: Imre Deak \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aCc: Will Deacon \u000aLink: https://lkml.kernel.org/r/20190524201509.9199-2-imre.deak@intel.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:29 +0200", "id" : "3e6d03e7a5a2668c27b86797ce0bb0dc6699dbc4", "msg" : "locking/lockdep: Fix merging of hlocks with non-zero references", "paths" : [ { "editType" : "edit", "file" : "kernel/locking/lockdep.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/radio/wl128x/fmdrv_v4l2.c" ], "commitId" : "b46ef18cb8ded747c2d9f8fce626528aba876fcd", "timestamp" : 1564125149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: wl128x: Fix some error handling in fm_v4l2_init_video_device()\u000a\u000a[ Upstream commit 69fbb3f47327d959830c94bf31893972b8c8f700 ]\u000a\u000aX-Originating-IP: [10.175.113.25]\u000aX-CFilter-Loop: Reflected\u000aThe fm_v4l2_init_video_device() forget to unregister v4l2/video device\u000ain the error path, it could lead to UAF issue, eg,\u000a\u000a BUG: KASAN: use-after-free in atomic64_read include/asm-generic/atomic-instrumented.h:836 [inline]\u000a BUG: KASAN: use-after-free in atomic_long_read include/asm-generic/atomic-long.h:28 [inline]\u000a BUG: KASAN: use-after-free in __mutex_unlock_slowpath+0x92/0x690 kernel/locking/mutex.c:1206\u000a Read of size 8 at addr ffff8881e84a7c70 by task v4l_id/3659\u000a\u000a CPU: 1 PID: 3659 Comm: v4l_id Not tainted 5.1.0 #8\u000a Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014\u000a Call Trace:\u000a __dump_stack lib/dump_stack.c:77 [inline]\u000a dump_stack+0xa9/0x10e lib/dump_stack.c:113\u000a print_address_description+0x65/0x270 mm/kasan/report.c:187\u000a kasan_report+0x149/0x18d mm/kasan/report.c:317\u000a atomic64_read include/asm-generic/atomic-instrumented.h:836 [inline]\u000a atomic_long_read include/asm-generic/atomic-long.h:28 [inline]\u000a __mutex_unlock_slowpath+0x92/0x690 kernel/locking/mutex.c:1206\u000a fm_v4l2_fops_open+0xac/0x120 [fm_drv]\u000a v4l2_open+0x191/0x390 [videodev]\u000a chrdev_open+0x20d/0x570 fs/char_dev.c:417\u000a do_dentry_open+0x700/0xf30 fs/open.c:777\u000a do_last fs/namei.c:3416 [inline]\u000a path_openat+0x7c4/0x2a90 fs/namei.c:3532\u000a do_filp_open+0x1a5/0x2b0 fs/namei.c:3563\u000a do_sys_open+0x302/0x490 fs/open.c:1069\u000a do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a RIP: 0033:0x7f8180c17c8e\u000a ...\u000a Allocated by task 3642:\u000a set_track mm/kasan/common.c:87 [inline]\u000a __kasan_kmalloc.constprop.3+0xa0/0xd0 mm/kasan/common.c:497\u000a fm_drv_init+0x13/0x1000 [fm_drv]\u000a do_one_initcall+0xbc/0x47d init/main.c:901\u000a do_init_module+0x1b5/0x547 kernel/module.c:3456\u000a load_module+0x6405/0x8c10 kernel/module.c:3804\u000a __do_sys_finit_module+0x162/0x190 kernel/module.c:3898\u000a do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a\u000a Freed by task 3642:\u000a set_track mm/kasan/common.c:87 [inline]\u000a __kasan_slab_free+0x130/0x180 mm/kasan/common.c:459\u000a slab_free_hook mm/slub.c:1429 [inline]\u000a slab_free_freelist_hook mm/slub.c:1456 [inline]\u000a slab_free mm/slub.c:3003 [inline]\u000a kfree+0xe1/0x270 mm/slub.c:3958\u000a fm_drv_init+0x1e6/0x1000 [fm_drv]\u000a do_one_initcall+0xbc/0x47d init/main.c:901\u000a do_init_module+0x1b5/0x547 kernel/module.c:3456\u000a load_module+0x6405/0x8c10 kernel/module.c:3804\u000a __do_sys_finit_module+0x162/0x190 kernel/module.c:3898\u000a do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a\u000aAdd relevant unregister functions to fix it.\u000a\u000aCc: Hans Verkuil \u000aReported-by: Hulk Robot \u000aSigned-off-by: Kefeng Wang \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:29 +0200", "id" : "b46ef18cb8ded747c2d9f8fce626528aba876fcd", "msg" : "media: wl128x: Fix some error handling in fm_v4l2_init_video_device()", "paths" : [ { "editType" : "edit", "file" : "drivers/media/radio/wl128x/fmdrv_v4l2.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" ], "commitId" : "bd87e2a197f6958c8b613cee022d50ec7c9fca83", "timestamp" : 1564125149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: add a check to pointer in error_detected and slot_reset\u000a\u000a[ Upstream commit 661262bc3e0ecc9a1aed39c6b2a99766da2c22e2 ]\u000a\u000aIf we add a VF without loading hclgevf.ko and then there is a RAS error\u000aoccurs, PCIe AER will call error_detected and slot_reset of all functions,\u000aand will get a NULL pointer when we check ad_dev->ops->handle_hw_ras_error.\u000aThis will cause a call trace and failures on handling of follow-up RAS\u000aerrors.\u000a\u000aThis patch check ae_dev and ad_dev->ops at first to solve above issues.\u000a\u000aSigned-off-by: Weihang Li \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:29 +0200", "id" : "bd87e2a197f6958c8b613cee022d50ec7c9fca83", "msg" : "net: hns3: add a check to pointer in error_detected and slot_reset", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hnae3.c" ], "commitId" : "28a7d7a6dcd70c405c8added34a60a1049bb25cd", "timestamp" : 1564125149000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: set ops to null when unregister ad_dev\u000a\u000a[ Upstream commit 594a81b39525f0a17e92c2e0b167ae1400650380 ]\u000a\u000aThe hclge/hclgevf and hns3 module can be unloaded independently,\u000awhen hclge/hclgevf unloaded firstly, the ops of ae_dev should\u000abe set to NULL, otherwise it will cause an use-after-free problem.\u000a\u000aFixes: 38caee9d3ee8 (\"net: hns3: Add support of the HNAE3 framework\")\u000aSigned-off-by: Weihang Li \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:29 +0200", "id" : "28a7d7a6dcd70c405c8added34a60a1049bb25cd", "msg" : "net: hns3: set ops to null when unregister ad_dev", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hnae3.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/power/cpupower/utils/cpufreq-set.c" ], "commitId" : "6aed94de94042972053bab5168e834aae59288a2", "timestamp" : 1564125150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cpupower : frequency-set -r option misses the last cpu in related cpu list\u000a\u000a[ Upstream commit 04507c0a9385cc8280f794a36bfff567c8cc1042 ]\u000a\u000aTo set frequency on specific cpus using cpupower, following syntax can\u000abe used :\u000acpupower -c #i frequency-set -f #f -r\u000a\u000aWhile setting frequency using cpupower frequency-set command, if we use\u000a'-r' option, it is expected to set frequency for all cpus related to\u000acpu #i. But it is observed to be missing the last cpu in related cpu\u000alist. This patch fixes the problem.\u000a\u000aSigned-off-by: Abhishek Goel \u000aReviewed-by: Thomas Renninger \u000aSigned-off-by: Shuah Khan \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:30 +0200", "id" : "6aed94de94042972053bab5168e834aae59288a2", "msg" : "cpupower : frequency-set -r option misses the last cpu in related cpu list", "paths" : [ { "editType" : "edit", "file" : "tools/power/cpupower/utils/cpufreq-set.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/Kconfig", "arch/arm64/mm/init.c" ], "commitId" : "37243454d0be784b1e4f51b1e194e2937f531eec", "timestamp" : 1564125150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: mm: make CONFIG_ZONE_DMA32 configurable\u000a\u000a[ Upstream commit 0c1f14ed12262f45a3af1d588e4d7bd12438b8f5 ]\u000a\u000aThis change makes CONFIG_ZONE_DMA32 defuly y and allows users\u000ato overwrite it only when CONFIG_EXPERT=y.\u000a\u000aFor the SoCs that do not need CONFIG_ZONE_DMA32, this is the\u000afirst step to manage all available memory by a single\u000azone(normal zone) to reduce the overhead of multiple zones.\u000a\u000aThe change also fixes a build error when CONFIG_NUMA=y and\u000aCONFIG_ZONE_DMA32=n.\u000a\u000aarch/arm64/mm/init.c:195:17: error: use of undeclared identifier 'ZONE_DMA32'\u000a max_zone_pfns[ZONE_DMA32] = PFN_DOWN(max_zone_dma_phys());\u000a\u000aChange since v1:\u000a1. only expose CONFIG_ZONE_DMA32 when CONFIG_EXPERT=y\u000a2. remove redundant IS_ENABLED(CONFIG_ZONE_DMA32)\u000a\u000aCc: Robin Murphy \u000aSigned-off-by: Miles Chen \u000aSigned-off-by: Catalin Marinas \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:30 +0200", "id" : "37243454d0be784b1e4f51b1e194e2937f531eec", "msg" : "arm64: mm: make CONFIG_ZONE_DMA32 configurable", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/Kconfig" }, { "editType" : "edit", "file" : "arch/arm64/mm/init.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/staging/media/imx/imx7-mipi-csis.c" ], "commitId" : "5b41a2ede7b1bfd760156432ef04a954b5055ede", "timestamp" : 1564125150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: imx7-mipi-csis: Propagate the error if clock enabling fails\u000a\u000a[ Upstream commit 2b393f91c651c16d5c09f5c7aa689e58a79df34e ]\u000a\u000aCurrently the return value from clk_bulk_prepare_enable() is checked,\u000abut it is not propagate it in the case of failure.\u000a\u000aFix it and also move the error message to the caller of\u000amipi_csis_clk_enable().\u000a\u000aSigned-off-by: Fabio Estevam \u000aReviewed-by: Rui Miguel Silva \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:30 +0200", "id" : "5b41a2ede7b1bfd760156432ef04a954b5055ede", "msg" : "media: imx7-mipi-csis: Propagate the error if clock enabling fails", "paths" : [ { "editType" : "edit", "file" : "drivers/staging/media/imx/imx7-mipi-csis.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/jvmti/libjvmti.c" ], "commitId" : "94140c6f62a4fedf4431cb8d216f4be9845fa848", "timestamp" : 1564125150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf jvmti: Address gcc string overflow warning for strncpy()\u000a\u000a[ Upstream commit 279ab04dbea1370d2eac0f854270369ccaef8a44 ]\u000a\u000aWe are getting false positive gcc warning when we compile with gcc9 (9.1.1):\u000a\u000a CC jvmti/libjvmti.o\u000a In file included from /usr/include/string.h:494,\u000a from jvmti/libjvmti.c:5:\u000a In function ‘strncpy’,\u000a inlined from ‘copy_class_filename.constprop’ at jvmti/libjvmti.c:166:3:\u000a /usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ specified bound depends on the length of the source argument [-Werror=stringop-overflow=]\u000a 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));\u000a | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\u000a jvmti/libjvmti.c: In function ‘copy_class_filename.constprop’:\u000a jvmti/libjvmti.c:165:26: note: length computed here\u000a 165 | size_t file_name_len = strlen(file_name);\u000a | ^~~~~~~~~~~~~~~~~\u000a cc1: all warnings being treated as errors\u000a\u000aAs per Arnaldo's suggestion use strlcpy(), which does the same thing and keeps\u000agcc silent.\u000a\u000aSuggested-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Jiri Olsa \u000aCc: Alexander Shishkin \u000aCc: Ben Gainey \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aCc: Stephane Eranian \u000aLink: http://lkml.kernel.org/r/20190531131321.GB1281@krava\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:30 +0200", "id" : "94140c6f62a4fedf4431cb8d216f4be9845fa848", "msg" : "perf jvmti: Address gcc string overflow warning for strncpy()", "paths" : [ { "editType" : "edit", "file" : "tools/perf/jvmti/libjvmti.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/aspeed-video.c" ], "commitId" : "467d4560aea39bfc630049f5a39b053966a9fb14", "timestamp" : 1564125150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: aspeed: change irq to threaded irq\u000a\u000a[ Upstream commit 12ae1c1bf5db2f33fcd9092a96f630291c4b181a ]\u000a\u000aDifferently from other Aspeed drivers, this driver calls clock\u000acontrol APIs in interrupt context. Since ECLK is coupled with a\u000areset bit in clk-aspeed module, aspeed_clk_enable will make 10ms of\u000abusy waiting delay for triggering the reset and it will eventually\u000adisturb other drivers' interrupt handling. To fix this issue, this\u000acommit changes this driver's irq to threaded irq so that the delay\u000acan be happened in a thread context.\u000a\u000aSigned-off-by: Jae Hyun Yoo \u000aReviewed-by: Eddie James \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:30 +0200", "id" : "467d4560aea39bfc630049f5a39b053966a9fb14", "msg" : "media: aspeed: change irq to threaded irq", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/aspeed-video.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c" ], "commitId" : "ef5f55ea5ed9902c7550b03a5ae6ff4be6c7fc96", "timestamp" : 1564125150000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: dwmac4: fix flow control issue\u000a\u000a[ Upstream commit ee326fd01e79dfa42014d55931260b68b9fa3273 ]\u000a\u000aCurrent dwmac4_flow_ctrl will not clear\u000aGMAC_RX_FLOW_CTRL_RFE/GMAC_RX_FLOW_CTRL_RFE bits,\u000aso MAC hw will keep flow control on although expecting\u000aflow control off by ethtool. Add codes to fix it.\u000a\u000aFixes: 477286b53f55 (\"stmmac: add GMAC4 core support\")\u000aSigned-off-by: Biao Huang \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:30 +0200", "id" : "ef5f55ea5ed9902c7550b03a5ae6ff4be6c7fc96", "msg" : "net: stmmac: dwmac4: fix flow control issue", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/common.h" ], "commitId" : "bfaada52b0ad20ab61094fb4c14eb98616ae0564", "timestamp" : 1564125151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: modify default value of tx-frames\u000a\u000a[ Upstream commit d2facb4b3983425f6776c24dd678a82dbe673773 ]\u000a\u000athe default value of tx-frames is 25, it's too late when\u000apassing tstamp to stack, then the ptp4l will fail:\u000a\u000aptp4l -i eth0 -f gPTP.cfg -m\u000aptp4l: selected /dev/ptp0 as PTP clock\u000aptp4l: port 1: INITIALIZING to LISTENING on INITIALIZE\u000aptp4l: port 0: INITIALIZING to LISTENING on INITIALIZE\u000aptp4l: port 1: link up\u000aptp4l: timed out while polling for tx timestamp\u000aptp4l: increasing tx_timestamp_timeout may correct this issue,\u000a but it is likely caused by a driver bug\u000aptp4l: port 1: send peer delay response failed\u000aptp4l: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)\u000a\u000aptp4l tests pass when changing the tx-frames from 25 to 1 with\u000aethtool -C option.\u000aIt should be fine to set tx-frames default value to 1, so ptp4l will pass\u000aby default.\u000a\u000aSigned-off-by: Biao Huang \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:31 +0200", "id" : "bfaada52b0ad20ab61094fb4c14eb98616ae0564", "msg" : "net: stmmac: modify default value of tx-frames", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/common.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/inside-secure/safexcel_cipher.c" ], "commitId" : "c9fd5afc9c961d2a9153d2b94282d1f599e8d1ad", "timestamp" : 1564125151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: inside-secure - do not rely on the hardware last bit for result descriptors\u000a\u000a[ Upstream commit 89332590427235680236b9470e851afc49b3caa1 ]\u000a\u000aWhen performing a transformation the hardware is given result\u000adescriptors to save the result data. Those result descriptors are\u000abatched using a 'first' and a 'last' bit. There are cases were more\u000adescriptors than needed are given to the engine, leading to the engine\u000aonly using some of them, and not setting the last bit on the last\u000adescriptor we gave. This causes issues were the driver and the hardware\u000aaren't in sync anymore about the number of result descriptors given (as\u000athe driver do not give a pool of descriptor to use for any\u000atransformation, but a pool of descriptors to use *per* transformation).\u000a\u000aThis patch fixes it by attaching the number of given result descriptors\u000ato the requests, and by using this number instead of the 'last' bit\u000afound on the descriptors to process them.\u000a\u000aSigned-off-by: Antoine Tenart \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:31 +0200", "id" : "c9fd5afc9c961d2a9153d2b94282d1f599e8d1ad", "msg" : "crypto: inside-secure - do not rely on the hardware last bit for result descriptors", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/inside-secure/safexcel_cipher.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/freescale/fec_main.c" ], "commitId" : "a32d4cf2710b9326da60d9ffb8ee948e33d53828", "timestamp" : 1564125151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: fec: Do not use netdev messages too early\u000a\u000a[ Upstream commit a19a0582363b9a5f8ba812f34f1b8df394898780 ]\u000a\u000aWhen a valid MAC address is not found the current messages\u000aare shown:\u000a\u000afec 2188000.ethernet (unnamed net_device) (uninitialized): Invalid MAC address: 00:00:00:00:00:00\u000afec 2188000.ethernet (unnamed net_device) (uninitialized): Using random MAC address: aa:9f:25:eb:7e:aa\u000a\u000aSince the network device has not been registered at this point, it is better\u000ato use dev_err()/dev_info() instead, which will provide cleaner log\u000amessages like these:\u000a\u000afec 2188000.ethernet: Invalid MAC address: 00:00:00:00:00:00\u000afec 2188000.ethernet: Using random MAC address: aa:9f:25:eb:7e:aa\u000a\u000aTested on a imx6dl-pico-pi board.\u000a\u000aSigned-off-by: Fabio Estevam \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:31 +0200", "id" : "a32d4cf2710b9326da60d9ffb8ee948e33d53828", "msg" : "net: fec: Do not use netdev messages too early", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/freescale/fec_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/xilinx/xilinx_axienet_main.c" ], "commitId" : "5b0c0598d4c565f83b0e7882b83c4006d7a38f83", "timestamp" : 1564125151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: axienet: Fix race condition causing TX hang\u000a\u000a[ Upstream commit 7de44285c1f69ccfbe8be1d6a16fcd956681fee6 ]\u000a\u000aIt is possible that the interrupt handler fires and frees up space in\u000athe TX ring in between checking for sufficient TX ring space and\u000astopping the TX queue in axienet_start_xmit. If this happens, the\u000aqueue wake from the interrupt handler will occur before the queue is\u000astopped, causing a lost wakeup and the adapter's transmit hanging.\u000a\u000aTo avoid this, after stopping the queue, check again whether there is\u000asufficient space in the TX ring. If so, wake up the queue again.\u000a\u000aSigned-off-by: Robert Hancock \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:31 +0200", "id" : "5b0c0598d4c565f83b0e7882b83c4006d7a38f83", "msg" : "net: axienet: Fix race condition causing TX hang", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/xilinx/xilinx_axienet_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/s390/cio/qdio_main.c" ], "commitId" : "df2c88a7088dc154b7200c14755d8d85c474f3da", "timestamp" : 1564125151000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "s390/qdio: handle PENDING state for QEBSM devices\u000a\u000a[ Upstream commit 04310324c6f482921c071444833e70fe861b73d9 ]\u000a\u000aWhen a CQ-enabled device uses QEBSM for SBAL state inspection,\u000aget_buf_states() can return the PENDING state for an Output Queue.\u000aget_outbound_buffer_frontier() isn't prepared for this, and any PENDING\u000abuffer will permanently stall all further completion processing on this\u000aQueue.\u000a\u000aThis isn't a concern for non-QEBSM devices, as get_buf_states() for such\u000adevices will manually turn PENDING buffers into EMPTY ones.\u000a\u000aFixes: 104ea556ee7f (\"qdio: support asynchronous delivery of storage blocks\")\u000aSigned-off-by: Julian Wiedmann \u000aSigned-off-by: Heiko Carstens \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:31 +0200", "id" : "df2c88a7088dc154b7200c14755d8d85c474f3da", "msg" : "s390/qdio: handle PENDING state for QEBSM devices", "paths" : [ { "editType" : "edit", "file" : "drivers/s390/cio/qdio_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/ras/cec.c" ], "commitId" : "5b27bd98a9d21d0650b3f81fd6fa65ebf131f04e", "timestamp" : 1564125152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "RAS/CEC: Fix pfn insertion\u000a\u000a[ Upstream commit 6d8e294bf5f0e85c34e8b14b064e2965f53f38b0 ]\u000a\u000aWhen inserting random PFNs for debugging the CEC through\u000a(debugfs)/ras/cec/pfn, depending on the return value of pfn_set(),\u000amultiple values get inserted per a single write.\u000a\u000aThat is because simple_attr_write() interprets a retval of 0 as\u000asuccess and claims the whole input. However, pfn_set() returns the\u000acec_add_elem() value, which, if > 0 and smaller than the whole input\u000alength, makes glibc continue issuing the write syscall until there's\u000ainput left:\u000a\u000a pfn_set\u000a simple_attr_write\u000a debugfs_attr_write\u000a full_proxy_write\u000a vfs_write\u000a ksys_write\u000a do_syscall_64\u000a entry_SYSCALL_64_after_hwframe\u000a\u000aleading to those repeated calls.\u000a\u000aReturn 0 to fix that.\u000a\u000aSigned-off-by: Borislav Petkov \u000aCc: Tony Luck \u000aCc: linux-edac \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:32 +0200", "id" : "5b27bd98a9d21d0650b3f81fd6fa65ebf131f04e", "msg" : "RAS/CEC: Fix pfn insertion", "paths" : [ { "editType" : "edit", "file" : "drivers/ras/cec.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/phy/sfp.c" ], "commitId" : "b892e3cf62cc35109a618ba15d005858679979b1", "timestamp" : 1564125152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: sfp: add mutex to prevent concurrent state checks\u000a\u000a[ Upstream commit 2158e856f56bb762ef90f3ec244d41a519826f75 ]\u000a\u000asfp_check_state can potentially be called by both a threaded IRQ handler\u000aand delayed work. If it is concurrently called, it could result in\u000aincorrect state management. Add a st_mutex to protect the state - this\u000alock gets taken outside of code that checks and handle state changes, and\u000athe existing sm_mutex nests inside of it.\u000a\u000aSuggested-by: Russell King \u000aSigned-off-by: Robert Hancock \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:32 +0200", "id" : "b892e3cf62cc35109a618ba15d005858679979b1", "msg" : "net: sfp: add mutex to prevent concurrent state checks", "paths" : [ { "editType" : "edit", "file" : "drivers/net/phy/sfp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netfilter/ipset/ip_set_hash_gen.h" ], "commitId" : "3711cf1181bdc36cba1d1b77faf919ddb7938cdb", "timestamp" : 1564125152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipset: Fix memory accounting for hash types on resize\u000a\u000a[ Upstream commit 11921796f4799ca9c61c4b22cc54d84aa69f8a35 ]\u000a\u000aIf a fresh array block is allocated during resize, the current in-memory\u000aset size should be increased by the size of the block, not replaced by it.\u000a\u000aBefore the fix, adding entries to a hash set type, leading to a table\u000aresize, caused an inconsistent memory size to be reported. This becomes\u000amore obvious when swapping sets with similar sizes:\u000a\u000a # cat hash_ip_size.sh\u000a #!/bin/sh\u000a FAIL_RETRIES=10\u000a\u000a tries=0\u000a while [ ${tries} -lt ${FAIL_RETRIES} ]; do\u000a \u0009ipset create t1 hash:ip\u000a \u0009for i in `seq 1 4345`; do\u000a \u0009\u0009ipset add t1 1.2.$((i / 255)).$((i % 255))\u000a \u0009done\u000a \u0009t1_init=\"$(ipset list t1|sed -n 's/Size in memory: \\(.*\\)/\\1/p')\"\u000a\u000a \u0009ipset create t2 hash:ip\u000a \u0009for i in `seq 1 4360`; do\u000a \u0009\u0009ipset add t2 1.2.$((i / 255)).$((i % 255))\u000a \u0009done\u000a \u0009t2_init=\"$(ipset list t2|sed -n 's/Size in memory: \\(.*\\)/\\1/p')\"\u000a\u000a \u0009ipset swap t1 t2\u000a \u0009t1_swap=\"$(ipset list t1|sed -n 's/Size in memory: \\(.*\\)/\\1/p')\"\u000a \u0009t2_swap=\"$(ipset list t2|sed -n 's/Size in memory: \\(.*\\)/\\1/p')\"\u000a\u000a \u0009ipset destroy t1\u000a \u0009ipset destroy t2\u000a \u0009tries=$((tries + 1))\u000a\u000a \u0009if [ ${t1_init} -lt 10000 ] || [ ${t2_init} -lt 10000 ]; then\u000a \u0009\u0009echo \"FAIL after ${tries} tries:\"\u000a \u0009\u0009echo \"T1 size ${t1_init}, after swap ${t1_swap}\"\u000a \u0009\u0009echo \"T2 size ${t2_init}, after swap ${t2_swap}\"\u000a \u0009\u0009exit 1\u000a \u0009fi\u000a done\u000a echo \"PASS\"\u000a # echo -n 'func hash_ip4_resize +p' > /sys/kernel/debug/dynamic_debug/control\u000a # ./hash_ip_size.sh\u000a [ 2035.018673] attempt to resize set t1 from 10 to 11, t 00000000fe6551fa\u000a [ 2035.078583] set t1 resized from 10 (00000000fe6551fa) to 11 (00000000172a0163)\u000a [ 2035.080353] Table destroy by resize 00000000fe6551fa\u000a FAIL after 4 tries:\u000a T1 size 9064, after swap 71128\u000a T2 size 71128, after swap 9064\u000a\u000aReported-by: NOYB \u000aFixes: 9e41f26a505c (\"netfilter: ipset: Count non-static extension memory for userspace\")\u000aSigned-off-by: Stefano Brivio \u000aSigned-off-by: Jozsef Kadlecsik \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:32 +0200", "id" : "3711cf1181bdc36cba1d1b77faf919ddb7938cdb", "msg" : "ipset: Fix memory accounting for hash types on resize", "paths" : [ { "editType" : "edit", "file" : "net/netfilter/ipset/ip_set_hash_gen.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/arch/arm/util/cs-etm.c" ], "commitId" : "f511db18a708ed5c798f25f285ff81cecb401a55", "timestamp" : 1564125152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf cs-etm: Properly set the value of 'old' and 'head' in snapshot mode\u000a\u000a[ Upstream commit e45c48a9a4d20ebc7b639a62c3ef8f4b08007027 ]\u000a\u000aThis patch adds the necessary intelligence to properly compute the value\u000aof 'old' and 'head' when operating in snapshot mode. That way we can\u000aget the latest information in the AUX buffer and be compatible with the\u000ageneric AUX ring buffer mechanic.\u000a\u000aTester notes:\u000a\u000a> Leo, have you had the chance to test/review this one? Suzuki?\u000a\u000aSure. I applied this patch on the perf/core branch (with latest\u000acommit 3e4fbf36c1e3 'perf augmented_raw_syscalls: Move reading\u000afilename to the loop') and passed testing with below steps:\u000a\u000a # perf record -e cs_etm/@tmc_etr0/ -S -m,64 --per-thread ./sort &\u000a [1] 19097\u000a Bubble sorting array of 30000 elements\u000a\u000a # kill -USR2 19097\u000a # kill -USR2 19097\u000a # kill -USR2 19097\u000a [ perf record: Woken up 4 times to write data ]\u000a [ perf record: Captured and wrote 0.753 MB perf.data ]\u000a\u000aSigned-off-by: Mathieu Poirier \u000aTested-by: Leo Yan \u000aCc: Alexander Shishkin \u000aCc: Jiri Olsa \u000aCc: Peter Zijlstra \u000aCc: Suzuki Poulouse \u000aCc: linux-arm-kernel@lists.infradead.org\u000aLink: http://lkml.kernel.org/r/20190605161633.12245-1-mathieu.poirier@linaro.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:32 +0200", "id" : "f511db18a708ed5c798f25f285ff81cecb401a55", "msg" : "perf cs-etm: Properly set the value of 'old' and 'head' in snapshot mode", "paths" : [ { "editType" : "edit", "file" : "tools/perf/arch/arm/util/cs-etm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/tests/parse-events.c" ], "commitId" : "629bb02fbcc3fdebeed0a0afc3f290e62fccdf0f", "timestamp" : 1564125152000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf test 6: Fix missing kvm module load for s390\u000a\u000a[ Upstream commit 53fe307dfd309e425b171f6272d64296a54f4dff ]\u000a\u000aCommand\u000a\u000a # perf test -Fv 6\u000a\u000afails with error\u000a\u000a running test 100 'kvm-s390:kvm_s390_create_vm' failed to parse\u000a event 'kvm-s390:kvm_s390_create_vm', err -1, str 'unknown tracepoint'\u000a event syntax error: 'kvm-s390:kvm_s390_create_vm'\u000a \\___ unknown tracepoint\u000a\u000awhen the kvm module is not loaded or not built in.\u000a\u000aFix this by adding a valid function which tests if the module\u000ais loaded. Loaded modules (or builtin KVM support) have a\u000adirectory named\u000a /sys/kernel/debug/tracing/events/kvm-s390\u000afor this tracepoint.\u000a\u000aCheck for existence of this directory.\u000a\u000aSigned-off-by: Thomas Richter \u000aReviewed-by: Christian Borntraeger \u000aCc: Heiko Carstens \u000aCc: Hendrik Brueckner \u000aLink: http://lkml.kernel.org/r/20190604053504.43073-1-tmricht@linux.ibm.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:32 +0200", "id" : "629bb02fbcc3fdebeed0a0afc3f290e62fccdf0f", "msg" : "perf test 6: Fix missing kvm module load for s390", "paths" : [ { "editType" : "edit", "file" : "tools/perf/tests/parse-events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/annotate.c" ], "commitId" : "e8fb963cbda24b83a3e61464fc1d9ba15368a536", "timestamp" : 1564125153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf report: Fix OOM error in TUI mode on s390\u000a\u000a[ Upstream commit 8a07aa4e9b7b0222129c07afff81634a884b2866 ]\u000a\u000aDebugging a OOM error using the TUI interface revealed this issue\u000aon s390:\u000a\u000a[tmricht@m83lp54 perf]$ cat /proc/kallsyms |sort\u000a....\u000a00000001119b7158 B radix_tree_node_cachep\u000a00000001119b8000 B __bss_stop\u000a00000001119b8000 B _end\u000a000003ff80002850 t autofs_mount\u0009[autofs4]\u000a000003ff80002868 t autofs_show_options\u0009[autofs4]\u000a000003ff80002a98 t autofs_evict_inode\u0009[autofs4]\u000a....\u000a\u000aThere is a huge gap between the last kernel symbol\u000a__bss_stop/_end and the first kernel module symbol\u000aautofs_mount (from autofs4 module).\u000a\u000aAfter reading the kernel symbol table via functions:\u000a\u000a dso__load()\u000a +--> dso__load_kernel_sym()\u000a +--> dso__load_kallsyms()\u000a\u0009 +--> __dso_load_kallsyms()\u000a\u0009 +--> symbols__fixup_end()\u000a\u000athe symbol __bss_stop has a start address of 1119b8000 and\u000aan end address of 3ff80002850, as can be seen by this debug statement:\u000a\u000a symbols__fixup_end __bss_stop start:0x1119b8000 end:0x3ff80002850\u000a\u000aThe size of symbol __bss_stop is 0x3fe6e64a850 bytes!\u000aIt is the last kernel symbol and fills up the space until\u000athe first kernel module symbol.\u000a\u000aThis size kills the TUI interface when executing the following\u000acode:\u000a\u000a process_sample_event()\u000a hist_entry_iter__add()\u000a hist_iter__report_callback()\u000a hist_entry__inc_addr_samples()\u000a symbol__inc_addr_samples(symbol = __bss_stop)\u000a symbol__cycles_hist()\u000a annotated_source__alloc_histograms(...,\u000a\u0009\u0009\u0009\u0009 symbol__size(sym),\u000a\u0009\u0009 ...)\u000a\u000aThis function allocates memory to save sample histograms.\u000aThe symbol_size() marco is defined as sym->end - sym->start, which\u000aresults in above value of 0x3fe6e64a850 bytes and\u000athe call to calloc() in annotated_source__alloc_histograms() fails.\u000a\u000aThe histgram memory allocation might fail, make this failure\u000ano-fatal and continue processing.\u000a\u000aOutput before:\u000a[tmricht@m83lp54 perf]$ ./perf --debug stderr=1 report -vvvvv \\\u000a\u0009\u0009\u0009\u0009\u0009 -i ~/slow.data 2>/tmp/2\u000a[tmricht@m83lp54 perf]$ tail -5 /tmp/2\u000a __symbol__inc_addr_samples(875): ENOMEM! sym->name=__bss_stop,\u000a\u0009\u0009start=0x1119b8000, addr=0x2aa0005eb08, end=0x3ff80002850,\u000a\u0009\u0009func: 0\u000aproblem adding hist entry, skipping event\u000a0x938b8 [0x8]: failed to process type: 68 [Cannot allocate memory]\u000a[tmricht@m83lp54 perf]$\u000a\u000aOutput after:\u000a[tmricht@m83lp54 perf]$ ./perf --debug stderr=1 report -vvvvv \\\u000a\u0009\u0009\u0009\u0009\u0009 -i ~/slow.data 2>/tmp/2\u000a[tmricht@m83lp54 perf]$ tail -5 /tmp/2\u000a symbol__inc_addr_samples map:0x1597830 start:0x110730000 end:0x3ff80002850\u000a symbol__hists notes->src:0x2aa2a70 nr_hists:1\u000a symbol__inc_addr_samples sym:unlink_anon_vmas src:0x2aa2a70\u000a __symbol__inc_addr_samples: addr=0x11094c69e\u000a 0x11094c670 unlink_anon_vmas: period++ [addr: 0x11094c69e, 0x2e, evidx=0]\u000a \u0009=> nr_samples: 1, period: 526008\u000a[tmricht@m83lp54 perf]$\u000a\u000aThere is no error about failed memory allocation and the TUI interface\u000ashows all entries.\u000a\u000aSigned-off-by: Thomas Richter \u000aReviewed-by: Hendrik Brueckner \u000aCc: Heiko Carstens \u000aCc: Hendrik Brueckner \u000aLink: http://lkml.kernel.org/r/90cb5607-3e12-5167-682d-978eba7dafa8@linux.ibm.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:33 +0200", "id" : "e8fb963cbda24b83a3e61464fc1d9ba15368a536", "msg" : "perf report: Fix OOM error in TUI mode on s390", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/annotate.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/irqchip/irq-meson-gpio.c" ], "commitId" : "d47f5d1540ae9e4b1bb8b4251d0c8dca015ca4a5", "timestamp" : 1564125153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "irqchip/meson-gpio: Add support for Meson-G12A SoC\u000a\u000a[ Upstream commit c64a9e804ccf86eb202bfd1c6a8c5233c75a0431 ]\u000a\u000aThe Meson-G12A SoC uses the same GPIO interrupt controller IP block as the\u000aother Meson SoCs, A totle of 100 pins can be spied on, which is the sum of:\u000a\u000a- 223:100 undefined (no interrupt)\u000a- 99:97 3 pins on bank GPIOE\u000a- 96:77 20 pins on bank GPIOX\u000a- 76:61 16 pins on bank GPIOA\u000a- 60:53 8 pins on bank GPIOC\u000a- 52:37 16 pins on bank BOOT\u000a- 36:28 9 pins on bank GPIOH\u000a- 27:12 16 pins on bank GPIOZ\u000a- 11:0 12 pins in the AO domain\u000a\u000aSigned-off-by: Xingyu Chen \u000aSigned-off-by: Jianxin Pan \u000aSigned-off-by: Martin Blumenstingl \u000aSigned-off-by: Marc Zyngier \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:33 +0200", "id" : "d47f5d1540ae9e4b1bb8b4251d0c8dca015ca4a5", "msg" : "irqchip/meson-gpio: Add support for Meson-G12A SoC", "paths" : [ { "editType" : "edit", "file" : "drivers/irqchip/irq-meson-gpio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/usb/uvc/uvc_ctrl.c" ], "commitId" : "22b193c0c822fc624b133091c3fceffe3e81825c", "timestamp" : 1564125153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: uvcvideo: Fix access to uninitialized fields on probe error\u000a\u000a[ Upstream commit 11a087f484bf15ff65f0a9f277aa5a61fd07ed2a ]\u000a\u000aWe need to check whether this work we are canceling actually is\u000ainitialized.\u000a\u000aSigned-off-by: Oliver Neukum \u000aReported-by: syzbot+2e1ef9188251d9cc7944@syzkaller.appspotmail.com\u000aSigned-off-by: Laurent Pinchart \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:33 +0200", "id" : "22b193c0c822fc624b133091c3fceffe3e81825c", "msg" : "media: uvcvideo: Fix access to uninitialized fields on probe error", "paths" : [ { "editType" : "edit", "file" : "drivers/media/usb/uvc/uvc_ctrl.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/rcar_fdp1.c" ], "commitId" : "f7604fc3eae78eb4a4357f123b54ae87a390be7a", "timestamp" : 1564125153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: fdp1: Support M3N and E3 platforms\u000a\u000a[ Upstream commit 4e8c120de9268fc26f583268b9d22e7d37c4595f ]\u000a\u000aNew Gen3 R-Car platforms incorporate the FDP1 with an updated version\u000aregister. No code change is required to support these targets, but they\u000awill currently report an error stating that the device can not be\u000aidentified.\u000a\u000aUpdate the driver to match against the new device types.\u000a\u000aSigned-off-by: Kieran Bingham \u000aSigned-off-by: Laurent Pinchart \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:33 +0200", "id" : "f7604fc3eae78eb4a4357f123b54ae87a390be7a", "msg" : "media: fdp1: Support M3N and E3 platforms", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/rcar_fdp1.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/iommu/iommu.c" ], "commitId" : "47b6814f5446c4f33216166fd8cc919b4e6c6f20", "timestamp" : 1564125153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iommu: Fix a leak in iommu_insert_resv_region\u000a\u000a[ Upstream commit ad0834dedaa15c3a176f783c0373f836e44b4700 ]\u000a\u000aIn case we expand an existing region, we unlink\u000athis latter and insert the larger one. In\u000athat case we should free the original region after\u000athe insertion. Also we can immediately return.\u000a\u000aFixes: 6c65fb318e8b (\"iommu: iommu_get_group_resv_regions\")\u000a\u000aSigned-off-by: Eric Auger \u000aSigned-off-by: Joerg Roedel \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:33 +0200", "id" : "47b6814f5446c4f33216166fd8cc919b4e6c6f20", "msg" : "iommu: Fix a leak in iommu_insert_resv_region", "paths" : [ { "editType" : "edit", "file" : "drivers/iommu/iommu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpio-omap.c" ], "commitId" : "e1a324ccf033f2eacad940d560040880085b367f", "timestamp" : 1564125153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpio: omap: fix lack of irqstatus_raw0 for OMAP4\u000a\u000a[ Upstream commit 64ea3e9094a1f13b96c33244a3fb3a0f45690bd2 ]\u000a\u000aCommit 384ebe1c2849 (\"gpio/omap: Add DT support to GPIO driver\") added\u000athe register definition tables to the gpio-omap driver. Subsequently to\u000athat commit, commit 4e962e8998cc (\"gpio/omap: remove cpu_is_omapxxxx()\u000achecks from *_runtime_resume()\") added definitions for irqstatus_raw*\u000aregisters to the legacy OMAP4 definitions, but missed the DT\u000adefinitions.\u000a\u000aThis causes an unintentional change of behaviour for the 1.101 errata\u000aworkaround on OMAP4 platforms. Fix this oversight.\u000a\u000aFixes: 4e962e8998cc (\"gpio/omap: remove cpu_is_omapxxxx() checks from *_runtime_resume()\")\u000aSigned-off-by: Russell King \u000aSigned-off-by: Grygorii Strashko \u000aTested-by: Tony Lindgren \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:33 +0200", "id" : "e1a324ccf033f2eacad940d560040880085b367f", "msg" : "gpio: omap: fix lack of irqstatus_raw0 for OMAP4", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpio-omap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpio-omap.c" ], "commitId" : "fd40385f2cdd78bc58d835c8caa8362b36bf0307", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpio: omap: ensure irq is enabled before wakeup\u000a\u000a[ Upstream commit c859e0d479b3b4f6132fc12637c51e01492f31f6 ]\u000a\u000aDocumentation states:\u000a\u000a NOTE: There must be a correlation between the wake-up enable and\u000a interrupt-enable registers. If a GPIO pin has a wake-up configured\u000a on it, it must also have the corresponding interrupt enabled (on\u000a one of the two interrupt lines).\u000a\u000aEnsure that this condition is always satisfied by enabling the detection\u000aevents after enabling the interrupt, and disabling the detection before\u000adisabling the interrupt. This ensures interrupt/wakeup events can not\u000ahappen until both the wakeup and interrupt enables correlate.\u000a\u000aIf we do any clearing, clear between the interrupt enable/disable and\u000atrigger setting.\u000a\u000aSigned-off-by: Russell King \u000aSigned-off-by: Grygorii Strashko \u000aTested-by: Tony Lindgren \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "fd40385f2cdd78bc58d835c8caa8362b36bf0307", "msg" : "gpio: omap: ensure irq is enabled before wakeup", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpio-omap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/base/regmap/regmap.c" ], "commitId" : "5c4906f7d0bd3d55be70d31f966a016c4078a748", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "regmap: fix bulk writes on paged registers\u000a\u000a[ Upstream commit db057679de3e9e6a03c1bcd5aee09b0d25fd9f5b ]\u000a\u000aOn buses like SlimBus and SoundWire which does not support\u000agather_writes yet in regmap, A bulk write on paged register\u000awould be silently ignored after programming page.\u000aThis is because local variable 'ret' value in regmap_raw_write_impl()\u000agets reset to 0 once page register is written successfully and the\u000acode below checks for 'ret' value to be -ENOTSUPP before linearising\u000athe write buffer to send to bus->write().\u000a\u000aFix this by resetting the 'ret' value to -ENOTSUPP in cases where\u000agather_writes() is not supported or single register write is\u000anot possible.\u000a\u000aSigned-off-by: Srinivas Kandagatla \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "5c4906f7d0bd3d55be70d31f966a016c4078a748", "msg" : "regmap: fix bulk writes on paged registers", "paths" : [ { "editType" : "edit", "file" : "drivers/base/regmap/regmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpio-omap.c" ], "commitId" : "a2e7dcfd3594c26cc33902a77b6e7b82aefed462", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpio: omap: Fix lost edge wake-up interrupts\u000a\u000a[ Upstream commit a522f1d0c381c42f3ace13b8bbeeccabdd6d2e5c ]\u000a\u000aIf an edge interrupt triggers while entering idle just before we save\u000aGPIO datain register to saved_datain, the triggered GPIO will not be\u000anoticed on wake-up. This is because the saved_datain and GPIO datain\u000aare the same on wake-up in omap_gpio_unidle(). Let's fix this by\u000aignoring any pending edge interrupts for saved_datain.\u000a\u000aThis issue affects only idle states where the GPIO module internal\u000awake-up path is operational. For deeper idle states where the GPIO\u000amodule gets powered off, Linux generic wakeirqs must be used for\u000athe padconf wake-up events with pinctrl-single driver. For examples,\u000aplease see \"interrupts-extended\" dts usage in many drivers.\u000a\u000aThis issue can be somewhat easily reproduced by pinging an idle system\u000awith smsc911x Ethernet interface configured IRQ_TYPE_EDGE_FALLING. At\u000asome point the smsc911x interrupts will just stop triggering. Also if\u000aWLCORE WLAN is used with EDGE interrupt like it's documentation specifies,\u000awe can see lost interrupts without this patch.\u000a\u000aNote that in the long run we may be able to cancel entering idle by\u000areturning an error in gpio_omap_cpu_notifier() on pending interrupts.\u000aBut let's fix the bug first.\u000a\u000aAlso note that because of the recent clean-up efforts this patch does\u000anot apply directly to older kernels. This does fix a long term issue\u000athough, and can be backported as needed.\u000a\u000aCc: Aaro Koskinen \u000aCc: Grygorii Strashko \u000aCc: Keerthy \u000aCc: Ladislav Michl \u000aCc: Peter Ujfalusi \u000aCc: Russell King \u000aCc: Tero Kristo \u000aSigned-off-by: Tony Lindgren \u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "a2e7dcfd3594c26cc33902a77b6e7b82aefed462", "msg" : "gpio: omap: Fix lost edge wake-up interrupts", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpio-omap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/davinci/vpif_capture.c" ], "commitId" : "472a012407aec0a14ec3b17ad58eeee3d2eda4b7", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: davinci: vpif_capture: fix memory leak in vpif_probe()\u000a\u000a[ Upstream commit 64f883cd98c6d43013fb0cea788b63e50ebc068c ]\u000a\u000aIf vpif_probe() fails on v4l2_device_register() and vpif_probe_complete(),\u000athen memory allocated at initialize_vpif() for global vpif_obj.dev[i]\u000abecome unreleased.\u000a\u000aThe patch adds deallocation of vpif_obj.dev[i] on the error path.\u000a\u000aSigned-off-by: Young Xiao <92siuyang@gmail.com>\u000aAcked-by: Lad, Prabhakar \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "472a012407aec0a14ec3b17ad58eeee3d2eda4b7", "msg" : "media: davinci: vpif_capture: fix memory leak in vpif_probe()", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/davinci/vpif_capture.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/bpf/Makefile" ], "commitId" : "b4f85b139e45504e6b6cd92fc65a945f4c23de15", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: silence warning messages in core\u000a\u000a[ Upstream commit aee450cbe482a8c2f6fa5b05b178ef8b8ff107ca ]\u000a\u000aCompiling kernel/bpf/core.c with W=1 causes a flood of warnings:\u000a\u000akernel/bpf/core.c:1198:65: warning: initialized field overwritten [-Woverride-init]\u000a 1198 | #define BPF_INSN_3_TBL(x, y, z) [BPF_##x | BPF_##y | BPF_##z] = true\u000a | ^~~~\u000akernel/bpf/core.c:1087:2: note: in expansion of macro 'BPF_INSN_3_TBL'\u000a 1087 | INSN_3(ALU, ADD, X), \\\u000a | ^~~~~~\u000akernel/bpf/core.c:1202:3: note: in expansion of macro 'BPF_INSN_MAP'\u000a 1202 | BPF_INSN_MAP(BPF_INSN_2_TBL, BPF_INSN_3_TBL),\u000a | ^~~~~~~~~~~~\u000akernel/bpf/core.c:1198:65: note: (near initialization for 'public_insntable[12]')\u000a 1198 | #define BPF_INSN_3_TBL(x, y, z) [BPF_##x | BPF_##y | BPF_##z] = true\u000a | ^~~~\u000akernel/bpf/core.c:1087:2: note: in expansion of macro 'BPF_INSN_3_TBL'\u000a 1087 | INSN_3(ALU, ADD, X), \\\u000a | ^~~~~~\u000akernel/bpf/core.c:1202:3: note: in expansion of macro 'BPF_INSN_MAP'\u000a 1202 | BPF_INSN_MAP(BPF_INSN_2_TBL, BPF_INSN_3_TBL),\u000a | ^~~~~~~~~~~~\u000a\u000a98 copies of the above.\u000a\u000aThe attached patch silences the warnings, because we *know* we're overwriting\u000athe default initializer. That leaves bpf/core.c with only 6 other warnings,\u000awhich become more visible in comparison.\u000a\u000aSigned-off-by: Valdis Kletnieks \u000aAcked-by: Andrii Nakryiko \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "b4f85b139e45504e6b6cd92fc65a945f4c23de15", "msg" : "bpf: silence warning messages in core", "paths" : [ { "editType" : "edit", "file" : "kernel/bpf/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/s5p-mfc/s5p_mfc.c" ], "commitId" : "1e1b35441b5ff628fdb29d06de11a493c070e658", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: s5p-mfc: fix reading min scratch buffer size on MFC v6/v7\u000a\u000a[ Upstream commit be22203aec440c1761ce8542c2636ac6c8951e3a ]\u000a\u000aMFC v6 and v7 has no register to read min scratch buffer size, so it has\u000ato be read conditionally only if hardware supports it. This fixes following\u000aNULL pointer exception on SoCs with MFC v6/v7:\u000a\u000a8<--- cut here ---\u000aUnable to handle kernel NULL pointer dereference at virtual address 00000000\u000apgd = f25837f9\u000a[00000000] *pgd=bd93d835\u000aInternal error: Oops: 17 [#1] PREEMPT SMP ARM\u000aModules linked in: btmrvl_sdio btmrvl bluetooth mwifiex_sdio mwifiex ecdh_generic ecc\u000aHardware name: SAMSUNG EXYNOS (Flattened Device Tree)\u000aPC is at s5p_mfc_get_min_scratch_buf_size+0x30/0x3c\u000aLR is at s5p_mfc_get_min_scratch_buf_size+0x28/0x3c\u000a...\u000a[] (s5p_mfc_get_min_scratch_buf_size) from [] (s5p_mfc_irq+0x814/0xa5c)\u000a[] (s5p_mfc_irq) from [] (__handle_irq_event_percpu+0x64/0x3f8)\u000a[] (__handle_irq_event_percpu) from [] (handle_irq_event_percpu+0x2c/0x7c)\u000a[] (handle_irq_event_percpu) from [] (handle_irq_event+0x38/0x5c)\u000a[] (handle_irq_event) from [] (handle_fasteoi_irq+0xc4/0x180)\u000a[] (handle_fasteoi_irq) from [] (generic_handle_irq+0x24/0x34)\u000a[] (generic_handle_irq) from [] (__handle_domain_irq+0x7c/0xec)\u000a[] (__handle_domain_irq) from [] (gic_handle_irq+0x58/0x9c)\u000a[] (gic_handle_irq) from [] (__irq_svc+0x70/0xb0)\u000aException stack(0xe73ddc60 to 0xe73ddca8)\u000a...\u000a[] (__irq_svc) from [] (console_unlock+0x5a8/0x6a8)\u000a[] (console_unlock) from [] (vprintk_emit+0x118/0x2d8)\u000a[] (vprintk_emit) from [] (vprintk_default+0x20/0x28)\u000a[] (vprintk_default) from [] (printk+0x30/0x54)\u000a[] (printk) from [] (s5p_mfc_init_decode_v6+0x1d4/0x284)\u000a[] (s5p_mfc_init_decode_v6) from [] (vb2_start_streaming+0x24/0x150)\u000a[] (vb2_start_streaming) from [] (vb2_core_streamon+0x11c/0x15c)\u000a[] (vb2_core_streamon) from [] (vidioc_streamon+0x64/0xa0)\u000a[] (vidioc_streamon) from [] (__video_do_ioctl+0x28c/0x45c)\u000a[] (__video_do_ioctl) from [] (video_usercopy+0x260/0x8a4)\u000a[] (video_usercopy) from [] (do_vfs_ioctl+0xb0/0x9fc)\u000a[] (do_vfs_ioctl) from [] (ksys_ioctl+0x34/0x58)\u000a[] (ksys_ioctl) from [] (ret_fast_syscall+0x0/0x28)\u000aException stack(0xe73ddfa8 to 0xe73ddff0)\u000a...\u000a---[ end trace 376cf5ba6e0bee93 ]---\u000a\u000aSigned-off-by: Marek Szyprowski \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "1e1b35441b5ff628fdb29d06de11a493c070e658", "msg" : "media: s5p-mfc: fix reading min scratch buffer size on MFC v6/v7", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/s5p-mfc/s5p_mfc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "security/selinux/hooks.c" ], "commitId" : "005fa17c4a4cfbdce94bf4504f385927bc9ca062", "timestamp" : 1564125154000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "selinux: fix empty write to keycreate file\u000a\u000a[ Upstream commit 464c258aa45b09f16aa0f05847ed8895873262d9 ]\u000a\u000aWhen sid == 0 (we are resetting keycreate_sid to the default value), we\u000ashould skip the KEY__CREATE check.\u000a\u000aBefore this patch, doing a zero-sized write to /proc/self/keycreate\u000awould check if the current task can create unlabeled keys (which would\u000ausually fail with -EACCESS and generate an AVC). Now it skips the check\u000aand correctly sets the task's keycreate_sid to 0.\u000a\u000aBug report: https://bugzilla.redhat.com/show_bug.cgi?id=1719067\u000a\u000aTested using the reproducer from the report above.\u000a\u000aFixes: 4eb582cf1fbd (\"[PATCH] keys: add a way to store the appropriate context for newly-created keys\")\u000aReported-by: Kir Kolyshkin \u000aSigned-off-by: Ondrej Mosnacek \u000aSigned-off-by: Paul Moore \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:34 +0200", "id" : "005fa17c4a4cfbdce94bf4504f385927bc9ca062", "msg" : "selinux: fix empty write to keycreate file", "paths" : [ { "editType" : "edit", "file" : "security/selinux/hooks.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/testmgr.c" ], "commitId" : "c3fa410e620774a3b2df0dd9073caaa8c5860d21", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: testmgr - add some more preemption points\u000a\u000a[ Upstream commit e63e1b0dd0003dc31f73d875907432be3a2abe5d ]\u000a\u000aCall cond_resched() after each fuzz test iteration. This avoids stall\u000awarnings if fuzz_iterations is set very high for testing purposes.\u000a\u000aWhile we're at it, also call cond_resched() after finishing testing each\u000atest vector.\u000a\u000aSigned-off-by: Eric Biggers \u000aAcked-by: Ard Biesheuvel \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "c3fa410e620774a3b2df0dd9073caaa8c5860d21", "msg" : "crypto: testmgr - add some more preemption points", "paths" : [ { "editType" : "edit", "file" : "crypto/testmgr.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/include/asm/intel-family.h" ], "commitId" : "c3ee70b831273cd7d02f7ef4a2251e2f44dfc4b2", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/cpu: Add Ice Lake NNPI to Intel family\u000a\u000a[ Upstream commit e32d045cd4ba06b59878323e434bad010e78e658 ]\u000a\u000aAdd the CPUID model number of Ice Lake Neural Network Processor for Deep\u000aLearning Inference (ICL-NNPI) to the Intel family list. Ice Lake NNPI uses\u000amodel number 0x9D and this will be documented in a future version of Intel\u000aSoftware Development Manual.\u000a\u000aSigned-off-by: Rajneesh Bhardwaj \u000aSigned-off-by: Thomas Gleixner \u000aCc: bp@suse.de\u000aCc: Borislav Petkov \u000aCc: Dave Hansen \u000aCc: Andy Shevchenko \u000aCc: \"H. Peter Anvin\" \u000aCc: Kan Liang \u000aCc: Peter Zijlstra \u000aCc: platform-driver-x86@vger.kernel.org\u000aCc: Qiuxu Zhuo \u000aCc: Srinivas Pandruvada \u000aCc: Len Brown \u000aCc: Linux PM \u000aLink: https://lkml.kernel.org/r/20190606012419.13250-1-rajneesh.bhardwaj@linux.intel.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "c3ee70b831273cd7d02f7ef4a2251e2f44dfc4b2", "msg" : "x86/cpu: Add Ice Lake NNPI to Intel family", "paths" : [ { "editType" : "edit", "file" : "arch/x86/include/asm/intel-family.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/meson/axg-tdm.h" ], "commitId" : "031cf89b51d231d9e1e8f048320251fdd243c07e", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: meson: axg-tdm: fix sample clock inversion\u000a\u000a[ Upstream commit cb36ff785e868992e96e8b9e5a0c2822b680a9e2 ]\u000a\u000aThe content of SND_SOC_DAIFMT_FORMAT_MASK is a number, not a bitfield,\u000aso the test to check if the format is i2s is wrong. Because of this the\u000aclock setting may be wrong. For example, the sample clock gets inverted\u000ain DSP B mode, when it should not.\u000a\u000aFix the lrclk invert helper function\u000a\u000aFixes: 1a11d88f499c (\"ASoC: meson: add tdm formatter base driver\")\u000aSigned-off-by: Jerome Brunet \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "031cf89b51d231d9e1e8f048320251fdd243c07e", "msg" : "ASoC: meson: axg-tdm: fix sample clock inversion", "paths" : [ { "editType" : "edit", "file" : "sound/soc/meson/axg-tdm.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/rcupdate.h" ], "commitId" : "32d7d88fd9d80f7f36dc4934db356db0031406f2", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rcu: Force inlining of rcu_read_lock()\u000a\u000a[ Upstream commit 6da9f775175e516fc7229ceaa9b54f8f56aa7924 ]\u000a\u000aWhen debugging options are turned on, the rcu_read_lock() function\u000amight not be inlined. This results in lockdep's print_lock() function\u000aprinting \"rcu_read_lock+0x0/0x70\" instead of rcu_read_lock()'s caller.\u000aFor example:\u000a\u000a[ 10.579995] =============================\u000a[ 10.584033] WARNING: suspicious RCU usage\u000a[ 10.588074] 4.18.0.memcg_v2+ #1 Not tainted\u000a[ 10.593162] -----------------------------\u000a[ 10.597203] include/linux/rcupdate.h:281 Illegal context switch in\u000aRCU read-side critical section!\u000a[ 10.606220]\u000a[ 10.606220] other info that might help us debug this:\u000a[ 10.606220]\u000a[ 10.614280]\u000a[ 10.614280] rcu_scheduler_active = 2, debug_locks = 1\u000a[ 10.620853] 3 locks held by systemd/1:\u000a[ 10.624632] #0: (____ptrval____) (&type->i_mutex_dir_key#5){.+.+}, at: lookup_slow+0x42/0x70\u000a[ 10.633232] #1: (____ptrval____) (rcu_read_lock){....}, at: rcu_read_lock+0x0/0x70\u000a[ 10.640954] #2: (____ptrval____) (rcu_read_lock){....}, at: rcu_read_lock+0x0/0x70\u000a\u000aThese \"rcu_read_lock+0x0/0x70\" strings are not providing any useful\u000ainformation. This commit therefore forces inlining of the rcu_read_lock()\u000afunction so that rcu_read_lock()'s caller is instead shown.\u000a\u000aSigned-off-by: Waiman Long \u000aSigned-off-by: Paul E. McKenney \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "32d7d88fd9d80f7f36dc4934db356db0031406f2", "msg" : "rcu: Force inlining of rcu_read_lock()", "paths" : [ { "editType" : "edit", "file" : "include/linux/rcupdate.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/include/asm/cpufeatures.h" ], "commitId" : "eb3e01b6c2e8c49c451f34e28372f93c20de8ac9", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/cpufeatures: Add FDP_EXCPTN_ONLY and ZERO_FCS_FDS\u000a\u000a[ Upstream commit cbb99c0f588737ec98c333558922ce47e9a95827 ]\u000a\u000aAdd the CPUID enumeration for Intel's de-feature bits to accommodate\u000apassing these de-features through to kvm guests.\u000a\u000aThese de-features are (from SDM vol 1, section 8.1.8):\u000a - X86_FEATURE_FDP_EXCPTN_ONLY: If CPUID.(EAX=07H,ECX=0H):EBX[bit 6] = 1, the\u000a data pointer (FDP) is updated only for the x87 non-control instructions that\u000a incur unmasked x87 exceptions.\u000a - X86_FEATURE_ZERO_FCS_FDS: If CPUID.(EAX=07H,ECX=0H):EBX[bit 13] = 1, the\u000a processor deprecates FCS and FDS; it saves each as 0000H.\u000a\u000aSigned-off-by: Aaron Lewis \u000aSigned-off-by: Borislav Petkov \u000aReviewed-by: Jim Mattson \u000aCc: Fenghua Yu \u000aCc: Frederic Weisbecker \u000aCc: \"H. Peter Anvin\" \u000aCc: Ingo Molnar \u000aCc: Konrad Rzeszutek Wilk \u000aCc: marcorr@google.com\u000aCc: Peter Feiner \u000aCc: pshier@google.com\u000aCc: Robert Hoo \u000aCc: Thomas Gleixner \u000aCc: Thomas Lendacky \u000aCc: x86-ml \u000aLink: https://lkml.kernel.org/r/20190605220252.103406-1-aaronlewis@google.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "eb3e01b6c2e8c49c451f34e28372f93c20de8ac9", "msg" : "x86/cpufeatures: Add FDP_EXCPTN_ONLY and ZERO_FCS_FDS", "paths" : [ { "editType" : "edit", "file" : "arch/x86/include/asm/cpufeatures.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/qlogic/qed/qed_iwarp.c" ], "commitId" : "38d13b389d5b0757e062fcd98fdd6a166354c2c7", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "qed: iWARP - Fix tc for MPA ll2 connection\u000a\u000a[ Upstream commit cb94d52b93c74fe1f2595734fabeda9f8ae891ee ]\u000a\u000aThe driver needs to assign a lossless traffic class for the MPA ll2\u000aconnection to ensure no packets are dropped when returning from the\u000adriver as they will never be re-transmitted by the peer.\u000a\u000aFixes: ae3488ff37dc (\"qed: Add ll2 connection for processing unaligned MPA packets\")\u000aSigned-off-by: Ariel Elior \u000aSigned-off-by: Michal Kalderon \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "38d13b389d5b0757e062fcd98fdd6a166354c2c7", "msg" : "qed: iWARP - Fix tc for MPA ll2 connection", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/qlogic/qed/qed_iwarp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" ], "commitId" : "2da60b8e383d8ecef277d17d9796455c09b98ebe", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: fix for dereferencing before null checking\u000a\u000a[ Upstream commit 757188005f905664b0186b88cf26a7e844190a63 ]\u000a\u000aThe netdev is dereferenced before null checking in the function\u000ahns3_setup_tc.\u000a\u000aThis patch moves the dereferencing after the null checking.\u000a\u000aFixes: 76ad4f0ee747 (\"net: hns3: Add support of HNS3 Ethernet Driver for hip08 SoC\")\u000a\u000aSigned-off-by: Yunsheng Lin \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "2da60b8e383d8ecef277d17d9796455c09b98ebe", "msg" : "net: hns3: fix for dereferencing before null checking", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c" ], "commitId" : "09b3600ee3c473272a7c1403ea3ac1795e4054a1", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: fix for skb leak when doing selftest\u000a\u000a[ Upstream commit 8f9eed1a8791b83eb1c54c261d68424717e4111e ]\u000a\u000aIf hns3_nic_net_xmit does not return NETDEV_TX_BUSY when doing\u000aa loopback selftest, the skb is not freed in hns3_clean_tx_ring\u000aor hns3_nic_net_xmit, which causes skb not freed problem.\u000a\u000aThis patch fixes it by freeing skb when hns3_nic_net_xmit does\u000anot return NETDEV_TX_OK.\u000a\u000aFixes: c39c4d98dc65 (\"net: hns3: Add mac loopback selftest support in hns3 driver\")\u000a\u000aSigned-off-by: Yunsheng Lin \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "09b3600ee3c473272a7c1403ea3ac1795e4054a1", "msg" : "net: hns3: fix for skb leak when doing selftest", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" ], "commitId" : "6d3e3e03585de50c0d07992ea06b74a8d26b34bb", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: delay ring buffer clearing during reset\u000a\u000a[ Upstream commit 3a30964a2eef6aabd3ab18b979ea0eacf1147731 ]\u000a\u000aThe driver may not be able to disable the ring through firmware\u000awhen downing the netdev during reset process, which may cause\u000ahardware accessing freed buffer problem.\u000a\u000aThis patch delays the ring buffer clearing to reset uninit\u000aprocess because hardware will not access the ring buffer after\u000ahardware reset is completed.\u000a\u000aFixes: bb6b94a896d4 (\"net: hns3: Add reset interface implementation in client\")\u000aSigned-off-by: Yunsheng Lin \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "6d3e3e03585de50c0d07992ea06b74a8d26b34bb", "msg" : "net: hns3: delay ring buffer clearing during reset", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/block/null_blk_main.c" ], "commitId" : "7b6ee182b4d483c6fc5aa7b5977b7430620f8489", "timestamp" : 1564125155000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "block: null_blk: fix race condition for null_del_dev\u000a\u000a[ Upstream commit 7602843fd873cae43a444b83b14dfdd114a9659c ]\u000a\u000aDulicate call of null_del_dev() will trigger null pointer error like below.\u000aThe reason is a race condition between nullb_device_power_store() and\u000anullb_group_drop_item().\u000a\u000a CPU#0 CPU#1\u000a ---------------- -----------------\u000a do_rmdir()\u000a >configfs_rmdir()\u000a >client_drop_item()\u000a >nullb_group_drop_item()\u000a nullb_device_power_store()\u000a\u0009\u0009\u0009\u0009>null_del_dev()\u000a\u000a >test_and_clear_bit(NULLB_DEV_FL_UP\u000a >null_del_dev()\u000a ^^^^^\u000a Duplicated null_dev_dev() triger null pointer error\u000a\u000a\u0009\u0009\u0009\u0009>clear_bit(NULLB_DEV_FL_UP\u000a\u000aThe fix could be keep the sequnce of clear NULLB_DEV_FL_UP and null_del_dev().\u000a\u000a[ 698.613600] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018\u000a[ 698.613608] #PF error: [normal kernel read fault]\u000a[ 698.613611] PGD 0 P4D 0\u000a[ 698.613619] Oops: 0000 [#1] SMP PTI\u000a[ 698.613627] CPU: 3 PID: 6382 Comm: rmdir Not tainted 5.0.0+ #35\u000a[ 698.613631] Hardware name: LENOVO 20LJS2EV08/20LJS2EV08, BIOS R0SET33W (1.17 ) 07/18/2018\u000a[ 698.613644] RIP: 0010:null_del_dev+0xc/0x110 [null_blk]\u000a[ 698.613649] Code: 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb 97 e8 47 bb 2a e8 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 <8b> 77 18 48 89 fb 4c 8b 27 48 c7 c7 40 57 1e c1 e8 bf c7 cb e8 48\u000a[ 698.613654] RSP: 0018:ffffb887888bfde0 EFLAGS: 00010286\u000a[ 698.613659] RAX: 0000000000000000 RBX: ffff9d436d92bc00 RCX: ffff9d43a9184681\u000a[ 698.613663] RDX: ffffffffc11e5c30 RSI: 0000000068be6540 RDI: 0000000000000000\u000a[ 698.613667] RBP: ffffb887888bfdf0 R08: 0000000000000001 R09: 0000000000000000\u000a[ 698.613671] R10: ffffb887888bfdd8 R11: 0000000000000f16 R12: ffff9d436d92bc08\u000a[ 698.613675] R13: ffff9d436d94e630 R14: ffffffffc11e5088 R15: ffffffffc11e5000\u000a[ 698.613680] FS: 00007faa68be6540(0000) GS:ffff9d43d14c0000(0000) knlGS:0000000000000000\u000a[ 698.613685] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 698.613689] CR2: 0000000000000018 CR3: 000000042f70c002 CR4: 00000000003606e0\u000a[ 698.613693] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\u000a[ 698.613697] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\u000a[ 698.613700] Call Trace:\u000a[ 698.613712] nullb_group_drop_item+0x50/0x70 [null_blk]\u000a[ 698.613722] client_drop_item+0x29/0x40\u000a[ 698.613728] configfs_rmdir+0x1ed/0x300\u000a[ 698.613738] vfs_rmdir+0xb2/0x130\u000a[ 698.613743] do_rmdir+0x1c7/0x1e0\u000a[ 698.613750] __x64_sys_rmdir+0x17/0x20\u000a[ 698.613759] do_syscall_64+0x5a/0x110\u000a[ 698.613768] entry_SYSCALL_64_after_hwframe+0x44/0xa9\u000a\u000aSigned-off-by: Bob Liu \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:35 +0200", "id" : "7b6ee182b4d483c6fc5aa7b5977b7430620f8489", "msg" : "block: null_blk: fix race condition for null_del_dev", "paths" : [ { "editType" : "edit", "file" : "drivers/block/null_blk_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/fs-writeback.c" ], "commitId" : "ded521217bf5af8e8119de48d889770771d0a6ae", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "blkcg, writeback: dead memcgs shouldn't contribute to writeback ownership arbitration\u000a\u000a[ Upstream commit 6631142229005e1b1c311a09efe9fb3cfdac8559 ]\u000a\u000awbc_account_io() collects information on cgroup ownership of writeback\u000apages to determine which cgroup should own the inode. Pages can stay\u000aassociated with dead memcgs but we want to avoid attributing IOs to\u000adead blkcgs as much as possible as the association is likely to be\u000astale. However, currently, pages associated with dead memcgs\u000acontribute to the accounting delaying and/or confusing the\u000aarbitration.\u000a\u000aFix it by ignoring pages associated with dead memcgs.\u000a\u000aSigned-off-by: Tejun Heo \u000aCc: Jan Kara \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "ded521217bf5af8e8119de48d889770771d0a6ae", "msg" : "blkcg, writeback: dead memcgs shouldn't contribute to writeback ownership arbitration", "paths" : [ { "editType" : "edit", "file" : "fs/fs-writeback.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/xfrm/xfrm_user.c" ], "commitId" : "db1af6e8030327ed1d5aeec248299558d8adcc62", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xfrm: fix sa selector validation\u000a\u000a[ Upstream commit b8d6d0079757cbd1b69724cfd1c08e2171c68cee ]\u000a\u000aAfter commit b38ff4075a80, the following command does not work anymore:\u000a$ ip xfrm state add src 10.125.0.2 dst 10.125.0.1 proto esp spi 34 reqid 1 \\\u000a mode tunnel enc 'cbc(aes)' 0xb0abdba8b782ad9d364ec81e3a7d82a1 auth-trunc \\\u000a 'hmac(sha1)' 0xe26609ebd00acb6a4d51fca13e49ea78a72c73e6 96 flag align4\u000a\u000aIn fact, the selector is not mandatory, allow the user to provide an empty\u000aselector.\u000a\u000aFixes: b38ff4075a80 (\"xfrm: Fix xfrm sel prefix length validation\")\u000aCC: Anirudh Gupta \u000aSigned-off-by: Nicolas Dichtel \u000aAcked-by: Herbert Xu \u000aSigned-off-by: Steffen Klassert \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "db1af6e8030327ed1d5aeec248299558d8adcc62", "msg" : "xfrm: fix sa selector validation", "paths" : [ { "editType" : "edit", "file" : "net/xfrm/xfrm_user.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/sched/core.c" ], "commitId" : "1ce5c91477b4b53f7dc8012e8a257c6ad76a1cd8", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sched/core: Add __sched tag for io_schedule()\u000a\u000a[ Upstream commit e3b929b0a184edb35531153c5afcaebb09014f9d ]\u000a\u000aNon-inline io_schedule() was introduced in:\u000a\u000a commit 10ab56434f2f (\"sched/core: Separate out io_schedule_prepare() and io_schedule_finish()\")\u000a\u000aKeep in line with io_schedule_timeout(), otherwise \"/proc//wchan\" will\u000areport io_schedule() rather than its callers when waiting for IO.\u000a\u000aReported-by: Jilong Kou \u000aSigned-off-by: Gao Xiang \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aAcked-by: Tejun Heo \u000aCc: Andrew Morton \u000aCc: Linus Torvalds \u000aCc: Miao Xie \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aFixes: 10ab56434f2f (\"sched/core: Separate out io_schedule_prepare() and io_schedule_finish()\")\u000aLink: https://lkml.kernel.org/r/20190603091338.2695-1-gaoxiang25@huawei.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "1ce5c91477b4b53f7dc8012e8a257c6ad76a1cd8", "msg" : "sched/core: Add __sched tag for io_schedule()", "paths" : [ { "editType" : "edit", "file" : "kernel/sched/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/scheduler/sched-pelt.c", "kernel/sched/sched-pelt.h" ], "commitId" : "7104a8f31d11690b5f8ae8ec934b7b5afdf96fd0", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sched/fair: Fix \"runnable_avg_yN_inv\" not used warnings\u000a\u000a[ Upstream commit 509466b7d480bc5d22e90b9fbe6122ae0e2fbe39 ]\u000a\u000arunnable_avg_yN_inv[] is only used in kernel/sched/pelt.c but was\u000aincluded in several other places because they need other macros all\u000acame from kernel/sched/sched-pelt.h which was generated by\u000aDocumentation/scheduler/sched-pelt. As the result, it causes compilation\u000aa lot of warnings,\u000a\u000a kernel/sched/sched-pelt.h:4:18: warning: 'runnable_avg_yN_inv' defined but not used [-Wunused-const-variable=]\u000a kernel/sched/sched-pelt.h:4:18: warning: 'runnable_avg_yN_inv' defined but not used [-Wunused-const-variable=]\u000a kernel/sched/sched-pelt.h:4:18: warning: 'runnable_avg_yN_inv' defined but not used [-Wunused-const-variable=]\u000a ...\u000a\u000aSilence it by appending the __maybe_unused attribute for it, so all\u000agenerated variables and macros can still be kept in the same file.\u000a\u000aSigned-off-by: Qian Cai \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aLink: https://lkml.kernel.org/r/1559596304-31581-1-git-send-email-cai@lca.pw\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "7104a8f31d11690b5f8ae8ec934b7b5afdf96fd0", "msg" : "sched/fair: Fix \"runnable_avg_yN_inv\" not used warnings", "paths" : [ { "editType" : "edit", "file" : "Documentation/scheduler/sched-pelt.c" }, { "editType" : "edit", "file" : "kernel/sched/sched-pelt.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/events/intel/core.c" ], "commitId" : "826e73e7716d7df01c74ac2a6b792a32da60a6dc", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/x86/intel: Disable check_msr for real HW\u000a\u000a[ Upstream commit d0e1a507bdc761a14906f03399d933ea639a1756 ]\u000a\u000aTom Vaden reported false failure of the check_msr() function, because\u000asome servers can do POST tracing and enable LBR tracing during\u000abootup.\u000a\u000aKan confirmed that check_msr patch was to fix a bug report in\u000aguest, so it's ok to disable it for real HW.\u000a\u000aReported-by: Tom Vaden \u000aSigned-off-by: Jiri Olsa \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aAcked-by: Tom Vaden \u000aCc: Alexander Shishkin \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Liang Kan \u000aCc: Linus Torvalds \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aLink: https://lkml.kernel.org/r/20190616141313.GD2500@krava\u000a[ Readability edits. ]\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "826e73e7716d7df01c74ac2a6b792a32da60a6dc", "msg" : "perf/x86/intel: Disable check_msr for real HW", "paths" : [ { "editType" : "edit", "file" : "arch/x86/events/intel/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/events/intel/uncore.h", "arch/x86/events/intel/uncore_snbep.c" ], "commitId" : "5536b0ee5b8ef1342514be2b97eec8d8c719b778", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/x86/intel/uncore: Handle invalid event coding for free-running counter\u000a\u000a[ Upstream commit 543ac280b3576c0009e8c0fcd4d6bfc9978d7bd0 ]\u000a\u000aCounting with invalid event coding for free-running counter may cause\u000aOOPs, e.g. uncore_iio_free_running_0/event=1/.\u000a\u000aCurrent code only validate the event with free-running event format,\u000aevent=0xff,umask=0xXY. Non-free-running event format never be checked\u000afor the PMU with free-running counters.\u000a\u000aAdd generic hw_config() to check and reject the invalid event coding\u000afor free-running PMU.\u000a\u000aSigned-off-by: Kan Liang \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aCc: acme@kernel.org\u000aCc: eranian@google.com\u000aFixes: 0f519f0352e3 (\"perf/x86/intel/uncore: Support IIO free-running counters on SKX\")\u000aLink: https://lkml.kernel.org/r/1556672028-119221-2-git-send-email-kan.liang@linux.intel.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "5536b0ee5b8ef1342514be2b97eec8d8c719b778", "msg" : "perf/x86/intel/uncore: Handle invalid event coding for free-running counter", "paths" : [ { "editType" : "edit", "file" : "arch/x86/events/intel/uncore.h" }, { "editType" : "edit", "file" : "arch/x86/events/intel/uncore_snbep.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "security/integrity/digsig.c" ], "commitId" : "1d0d6eb472501edac2627103b1d019ecdae62d03", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "integrity: Fix __integrity_init_keyring() section mismatch\u000a\u000a[ Upstream commit 8c655784e2cf59cb6140759b8b546d98261d1ad9 ]\u000a\u000aWith gcc-4.6.3:\u000a\u000a WARNING: vmlinux.o(.text.unlikely+0x24c64): Section mismatch in reference from the function __integrity_init_keyring() to the function .init.text:set_platform_trusted_keys()\u000a The function __integrity_init_keyring() references\u000a the function __init set_platform_trusted_keys().\u000a This is often because __integrity_init_keyring lacks a __init\u000a annotation or the annotation of set_platform_trusted_keys is wrong.\u000a\u000aIndeed, if the compiler decides not to inline __integrity_init_keyring(),\u000aa warning is issued.\u000a\u000aFix this by adding the missing __init annotation.\u000a\u000aFixes: 9dc92c45177ab70e (\"integrity: Define a trusted platform keyring\")\u000aSigned-off-by: Geert Uytterhoeven \u000aReviewed-by: Nayna Jain \u000aReviewed-by: James Morris \u000aSigned-off-by: Mimi Zohar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "1d0d6eb472501edac2627103b1d019ecdae62d03", "msg" : "integrity: Fix __integrity_init_keyring() section mismatch", "paths" : [ { "editType" : "edit", "file" : "security/integrity/digsig.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/atomic_t.txt", "arch/x86/include/asm/atomic64_64.h", "arch/x86/include/asm/barrier.h", "arch/x86/include/asm/atomic.h" ], "commitId" : "380ca1300affcd5385d43d2c933c393346295531", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/atomic: Fix smp_mb__{before,after}_atomic()\u000a\u000a[ Upstream commit 69d927bba39517d0980462efc051875b7f4db185 ]\u000a\u000aRecent probing at the Linux Kernel Memory Model uncovered a\u000a'surprise'. Strongly ordered architectures where the atomic RmW\u000aprimitive implies full memory ordering and\u000asmp_mb__{before,after}_atomic() are a simple barrier() (such as x86)\u000afail for:\u000a\u000a\u0009*x = 1;\u000a\u0009atomic_inc(u);\u000a\u0009smp_mb__after_atomic();\u000a\u0009r0 = *y;\u000a\u000aBecause, while the atomic_inc() implies memory order, it\u000a(surprisingly) does not provide a compiler barrier. This then allows\u000athe compiler to re-order like so:\u000a\u000a\u0009atomic_inc(u);\u000a\u0009*x = 1;\u000a\u0009smp_mb__after_atomic();\u000a\u0009r0 = *y;\u000a\u000aWhich the CPU is then allowed to re-order (under TSO rules) like:\u000a\u000a\u0009atomic_inc(u);\u000a\u0009r0 = *y;\u000a\u0009*x = 1;\u000a\u000aAnd this very much was not intended. Therefore strengthen the atomic\u000aRmW ops to include a compiler barrier.\u000a\u000aNOTE: atomic_{or,and,xor} and the bitops already had the compiler\u000abarrier.\u000a\u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Thomas Gleixner \u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "380ca1300affcd5385d43d2c933c393346295531", "msg" : "x86/atomic: Fix smp_mb__{before,after}_atomic()", "paths" : [ { "editType" : "edit", "file" : "arch/x86/include/asm/atomic64_64.h" }, { "editType" : "edit", "file" : "Documentation/atomic_t.txt" }, { "editType" : "edit", "file" : "arch/x86/include/asm/barrier.h" }, { "editType" : "edit", "file" : "arch/x86/include/asm/atomic.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/evsel.c" ], "commitId" : "0b0e0d7475465c36da6b4c1215e0648425acedc1", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf evsel: Make perf_evsel__name() accept a NULL argument\u000a\u000a[ Upstream commit fdbdd7e8580eac9bdafa532746c865644d125e34 ]\u000a\u000aIn which case it simply returns \"unknown\", like when it can't figure out\u000athe evsel->name value.\u000a\u000aThis makes this code more robust and fixes a problem in 'perf trace'\u000awhere a NULL evsel was being passed to a routine that only used the\u000aevsel for printing its name when a invalid syscall id was passed.\u000a\u000aReported-by: Leo Yan \u000aCc: Adrian Hunter \u000aCc: Jiri Olsa \u000aCc: Namhyung Kim \u000aLink: https://lkml.kernel.org/n/tip-f30ztaasku3z935cn3ak3h53@git.kernel.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "0b0e0d7475465c36da6b4c1215e0648425acedc1", "msg" : "perf evsel: Make perf_evsel__name() accept a NULL argument", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/evsel.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/vhost/net.c" ], "commitId" : "46ffa1554f00314a0e502eb081c212f02d6e26be", "timestamp" : 1564125156000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "vhost_net: disable zerocopy by default\u000a\u000a[ Upstream commit 098eadce3c622c07b328d0a43dda379b38cf7c5e ]\u000a\u000aVhost_net was known to suffer from HOL[1] issues which is not easy to\u000afix. Several downstream disable the feature by default. What's more,\u000athe datapath was split and datacopy path got the support of batching\u000aand XDP support recently which makes it faster than zerocopy part for\u000asmall packets transmission.\u000a\u000aIt looks to me that disable zerocopy by default is more\u000aappropriate. It cold be enabled by default again in the future if we\u000afix the above issues.\u000a\u000a[1] https://patchwork.kernel.org/patch/3787671/\u000a\u000aSigned-off-by: Jason Wang \u000aAcked-by: Michael S. Tsirkin \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:36 +0200", "id" : "46ffa1554f00314a0e502eb081c212f02d6e26be", "msg" : "vhost_net: disable zerocopy by default", "paths" : [ { "editType" : "edit", "file" : "drivers/vhost/net.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/iavf/iavf_txrx.c" ], "commitId" : "2a51e334a0ade539e5b0fcfdbd8b43acb9c7547d", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iavf: allow null RX descriptors\u000a\u000a[ Upstream commit efa14c3985828da3163f5372137cb64d992b0f79 ]\u000a\u000aIn some circumstances, the hardware can hand us a null receive\u000adescriptor, with no data attached but otherwise valid. Unfortunately,\u000athe driver was ill-equipped to handle such an event, and would stop\u000aprocessing packets at that point.\u000a\u000aTo fix this, use the Descriptor Done bit instead of the size to\u000adetermine whether or not a descriptor is ready to be processed. Add some\u000achecks to allow for unused buffers.\u000a\u000aSigned-off-by: Mitch Williams \u000aTested-by: Andrew Bowers \u000aSigned-off-by: Jeff Kirsher \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "2a51e334a0ade539e5b0fcfdbd8b43acb9c7547d", "msg" : "iavf: allow null RX descriptors", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/iavf/iavf_txrx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/ulp/ipoib/ipoib_main.c" ], "commitId" : "c545bda33b97b0c88c621f3488faedb7a7d73932", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipoib: correcly show a VF hardware address\u000a\u000a[ Upstream commit 64d701c608fea362881e823b666327f5d28d7ffd ]\u000a\u000ain the case of IPoIB with SRIOV enabled hardware\u000aip link show command incorrecly prints\u000a0 instead of a VF hardware address.\u000a\u000aBefore:\u000a11: ib1: mtu 2044 qdisc pfifo_fast\u000astate UP mode DEFAULT group default qlen 256\u000a link/infiniband\u000a80:00:00:66:fe:80:00:00:00:00:00:00:24:8a:07:03:00:a4:3e:7c brd\u000a00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff\u000a vf 0 MAC 00:00:00:00:00:00, spoof checking off, link-state disable,\u000atrust off, query_rss off\u000a...\u000aAfter:\u000a11: ib1: mtu 2044 qdisc pfifo_fast\u000astate UP mode DEFAULT group default qlen 256\u000a link/infiniband\u000a80:00:00:66:fe:80:00:00:00:00:00:00:24:8a:07:03:00:a4:3e:7c brd\u000a00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff\u000a vf 0 link/infiniband\u000a80:00:00:66:fe:80:00:00:00:00:00:00:24:8a:07:03:00:a4:3e:7c brd\u000a00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof\u000achecking off, link-state disable, trust off, query_rss off\u000a\u000av1->v2: just copy an address without modifing ifla_vf_mac\u000av2->v3: update the changelog\u000a\u000aSigned-off-by: Denis Kirjanov \u000aAcked-by: Doug Ledford \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "c545bda33b97b0c88c621f3488faedb7a7d73932", "msg" : "ipoib: correcly show a VF hardware address", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/ulp/ipoib/ipoib_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/sh/rcar/ctu.c" ], "commitId" : "f89b29faf9760d0195170bd3f8e9ab22da85c407", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: rsnd: fixup mod ID calculation in rsnd_ctu_probe_\u000a\u000a[ Upstream commit ac28ec07ae1c5c1e18ed6855eb105a328418da88 ]\u000a\u000acommit c16015f36cc1 (\"ASoC: rsnd: add .get_id/.get_id_sub\")\u000aintroduces rsnd_ctu_id which calcualates and gives\u000athe main Device id of the CTU by dividing the id by 4.\u000arsnd_mod_id uses this interface to get the CTU main\u000aDevice id. But this commit forgets to revert the main\u000aDevice id calcution previously done in rsnd_ctu_probe_\u000awhich also divides the id by 4. This path corrects the\u000asame to get the correct main Device id.\u000a\u000aThe issue is observered when rsnd_ctu_probe_ is done for CTU1\u000a\u000aFixes: c16015f36cc1 (\"ASoC: rsnd: add .get_id/.get_id_sub\")\u000a\u000aSigned-off-by: Nilkanth Ahirrao \u000aSigned-off-by: Suresh Udipi \u000aSigned-off-by: Jiada Wang \u000aAcked-by: Kuninori Morimoto \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "f89b29faf9760d0195170bd3f8e9ab22da85c407", "msg" : "ASoC: rsnd: fixup mod ID calculation in rsnd_ctu_probe_", "paths" : [ { "editType" : "edit", "file" : "sound/soc/sh/rcar/ctu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/bpf/verifier.c" ], "commitId" : "70cc29dba925b8a99a4917c2b5fa6702d0d496d1", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: fix callees pruning callers\u000a\u000a[ Upstream commit eea1c227b9e9bad295e8ef984004a9acf12bb68c ]\u000a\u000aThe commit 7640ead93924 partially resolved the issue of callees\u000aincorrectly pruning the callers.\u000aWith introduction of bounded loops and jmps_processed heuristic\u000asingle verifier state may contain multiple branches and calls.\u000aIt's possible that new verifier state (for future pruning) will be\u000aallocated inside callee. Then callee will exit (still within the same\u000averifier state). It will go back to the caller and there R6-R9 registers\u000awill be read and will trigger mark_reg_read. But the reg->live for all frames\u000abut the top frame is not set to LIVE_NONE. Hence mark_reg_read will fail\u000ato propagate liveness into parent and future walking will incorrectly\u000aconclude that the states are equivalent because LIVE_READ is not set.\u000aIn other words the rule for parent/live should be:\u000awhenever register parentage chain is set the reg->live should be set to LIVE_NONE.\u000ais_state_visited logic already follows this rule for spilled registers.\u000a\u000aFixes: 7640ead93924 (\"bpf: verifier: make sure callees don't prune with caller differences\")\u000aFixes: f4d7e40a5b71 (\"bpf: introduce function calls (verification)\")\u000aSigned-off-by: Alexei Starovoitov \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "70cc29dba925b8a99a4917c2b5fa6702d0d496d1", "msg" : "bpf: fix callees pruning callers", "paths" : [ { "editType" : "edit", "file" : "kernel/bpf/verifier.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pci/pci.c", "drivers/pci/pci.h", "drivers/pci/pcie/portdrv_core.c" ], "commitId" : "3c795a8e3481e4dec071b5956e7177e816f6e7f1", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "PCI: Add missing link delays required by the PCIe spec\u000a\u000a[ Upstream commit c2bf1fc212f7e6f25ace1af8f0b3ac061ea48ba5 ]\u000a\u000aCurrently Linux does not follow PCIe spec regarding the required delays\u000aafter reset. A concrete example is a Thunderbolt add-in-card that\u000aconsists of a PCIe switch and two PCIe endpoints:\u000a\u000a +-1b.0-[01-6b]----00.0-[02-6b]--+-00.0-[03]----00.0 TBT controller\u000a +-01.0-[04-36]-- DS hotplug port\u000a +-02.0-[37]----00.0 xHCI controller\u000a \\-04.0-[38-6b]-- DS hotplug port\u000a\u000aThe root port (1b.0) and the PCIe switch downstream ports are all PCIe\u000agen3 so they support 8GT/s link speeds.\u000a\u000aWe wait for the PCIe hierarchy to enter D3cold (runtime):\u000a\u000a pcieport 0000:00:1b.0: power state changed by ACPI to D3cold\u000a\u000aWhen it wakes up from D3cold, according to the PCIe 4.0 section 5.8 the\u000aPCIe switch is put to reset and its power is re-applied. This means that\u000awe must follow the rules in PCIe 4.0 section 6.6.1.\u000a\u000aFor the PCIe gen3 ports we are dealing with here, the following applies:\u000a\u000a With a Downstream Port that supports Link speeds greater than 5.0\u000a GT/s, software must wait a minimum of 100 ms after Link training\u000a completes before sending a Configuration Request to the device\u000a immediately below that Port. Software can determine when Link training\u000a completes by polling the Data Link Layer Link Active bit or by setting\u000a up an associated interrupt (see Section 6.7.3.3).\u000a\u000aTranslating this into the above topology we would need to do this (DLLLA\u000astands for Data Link Layer Link Active):\u000a\u000a pcieport 0000:00:1b.0: wait for 100ms after DLLLA is set before access to 0000:01:00.0\u000a pcieport 0000:02:00.0: wait for 100ms after DLLLA is set before access to 0000:03:00.0\u000a pcieport 0000:02:02.0: wait for 100ms after DLLLA is set before access to 0000:37:00.0\u000a\u000aI've instrumented the kernel with additional logging so we can see the\u000aactual delays the kernel performs:\u000a\u000a pcieport 0000:00:1b.0: power state changed by ACPI to D0\u000a pcieport 0000:00:1b.0: waiting for D3cold delay of 100 ms\u000a pcieport 0000:00:1b.0: waking up bus\u000a pcieport 0000:00:1b.0: waiting for D3hot delay of 10 ms\u000a pcieport 0000:00:1b.0: restoring config space at offset 0x2c (was 0x60, writing 0x60)\u000a ...\u000a pcieport 0000:00:1b.0: PME# disabled\u000a pcieport 0000:01:00.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a ...\u000a pcieport 0000:01:00.0: PME# disabled\u000a pcieport 0000:02:00.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a ...\u000a pcieport 0000:02:00.0: PME# disabled\u000a pcieport 0000:02:01.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a ...\u000a pcieport 0000:02:01.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100407)\u000a pcieport 0000:02:01.0: PME# disabled\u000a pcieport 0000:02:02.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a ...\u000a pcieport 0000:02:02.0: PME# disabled\u000a pcieport 0000:02:04.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a ...\u000a pcieport 0000:02:04.0: PME# disabled\u000a pcieport 0000:02:01.0: PME# enabled\u000a pcieport 0000:02:01.0: waiting for D3hot delay of 10 ms\u000a pcieport 0000:02:04.0: PME# enabled\u000a pcieport 0000:02:04.0: waiting for D3hot delay of 10 ms\u000a thunderbolt 0000:03:00.0: restoring config space at offset 0x14 (was 0x0, writing 0x8a040000)\u000a ...\u000a thunderbolt 0000:03:00.0: PME# disabled\u000a xhci_hcd 0000:37:00.0: restoring config space at offset 0x10 (was 0x0, writing 0x73f00000)\u000a ...\u000a xhci_hcd 0000:37:00.0: PME# disabled\u000a\u000aFor the switch upstream port (01:00.0) we wait for 100ms but not taking\u000ainto account the DLLLA requirement. We then wait 10ms for D3hot -> D0\u000atransition of the root port and the two downstream hotplug ports. This\u000ameans that we deviate from what the spec requires.\u000a\u000aPerforming the same check for system sleep (s2idle) transitions we can\u000asee following when resuming from s2idle:\u000a\u000a pcieport 0000:00:1b.0: power state changed by ACPI to D0\u000a pcieport 0000:00:1b.0: restoring config space at offset 0x2c (was 0x60, writing 0x60)\u000a ...\u000a pcieport 0000:01:00.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a ...\u000a pcieport 0000:02:02.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x2c (was 0x0, writing 0x0)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x28 (was 0x0, writing 0x0)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x3c (was 0x1ff, writing 0x201ff)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x24 (was 0x10001, writing 0x1fff1)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x2c (was 0x0, writing 0x60)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x20 (was 0x0, writing 0x73f073f0)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x2c (was 0x0, writing 0x60)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x28 (was 0x0, writing 0x60)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x2c (was 0x0, writing 0x0)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x1c (was 0x101, writing 0x1f1)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x28 (was 0x0, writing 0x60)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x24 (was 0x10001, writing 0x1ff10001)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x28 (was 0x0, writing 0x0)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x18 (was 0x0, writing 0x373702)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x24 (was 0x10001, writing 0x49f12001)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x20 (was 0x0, writing 0x73e05c00)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x24 (was 0x10001, writing 0x1fff1)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x20 (was 0x0, writing 0x89f07400)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x1c (was 0x101, writing 0x5151)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x20 (was 0x0, writing 0x8a008a00)\u000a pcieport 0000:02:02.0: restoring config space at offset 0xc (was 0x10000, writing 0x10020)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x1c (was 0x101, writing 0x6161)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x18 (was 0x0, writing 0x360402)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x1c (was 0x101, writing 0x1f1)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x18 (was 0x0, writing 0x6b3802)\u000a pcieport 0000:02:02.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100407)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x18 (was 0x0, writing 0x30302)\u000a pcieport 0000:02:01.0: restoring config space at offset 0xc (was 0x10000, writing 0x10020)\u000a pcieport 0000:02:04.0: restoring config space at offset 0xc (was 0x10000, writing 0x10020)\u000a pcieport 0000:02:00.0: restoring config space at offset 0xc (was 0x10000, writing 0x10020)\u000a pcieport 0000:02:01.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100407)\u000a pcieport 0000:02:04.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100407)\u000a pcieport 0000:02:00.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100407)\u000a xhci_hcd 0000:37:00.0: restoring config space at offset 0x10 (was 0x0, writing 0x73f00000)\u000a ...\u000a thunderbolt 0000:03:00.0: restoring config space at offset 0x14 (was 0x0, writing 0x8a040000)\u000a\u000aThis is even worse. None of the mandatory delays are performed. If this\u000awould be S3 instead of s2idle then according to PCI FW spec 3.2 section\u000a4.6.8. there is a specific _DSM that allows the OS to skip the delays\u000abut this platform does not provide the _DSM and does not go to S3 anyway\u000aso no firmware is involved that could already handle these delays.\u000a\u000aIn this particular Intel Coffee Lake platform these delays are not\u000aactually needed because there is an additional delay as part of the ACPI\u000apower resource that is used to turn on power to the hierarchy but since\u000athat additional delay is not required by any of standards (PCIe, ACPI)\u000ait is not present in the Intel Ice Lake, for example where missing the\u000amandatory delays causes pciehp to start tearing down the stack too early\u000a(links are not yet trained).\u000a\u000aFor this reason, change the PCIe portdrv PM resume hooks so that they\u000aperform the mandatory delays before the downstream component gets\u000aresumed. We perform the delays before port services are resumed because\u000aotherwise pciehp might find that the link is not up (even if it is just\u000atraining) and tears-down the hierarchy.\u000a\u000aSigned-off-by: Mika Westerberg \u000aSigned-off-by: Rafael J. Wysocki \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "3c795a8e3481e4dec071b5956e7177e816f6e7f1", "msg" : "PCI: Add missing link delays required by the PCIe spec", "paths" : [ { "editType" : "edit", "file" : "drivers/pci/pci.c" }, { "editType" : "edit", "file" : "drivers/pci/pcie/portdrv_core.c" }, { "editType" : "edit", "file" : "drivers/pci/pci.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/socionext/netsec.c" ], "commitId" : "a98c15177f72ae3c0a736bb324e66c279bf94899", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: netsec: initialize tx ring on ndo_open\u000a\u000a[ Upstream commit 39e3622edeffa63c2871153d8743c5825b139968 ]\u000a\u000aSince we changed the Tx ring handling and now depends on bit31 to figure\u000aout the owner of the descriptor, we should initialize this every time\u000athe device goes down-up instead of doing it once on driver init. If the\u000avalue is not correctly initialized the device won't have any available\u000adescriptors\u000a\u000aChanges since v1:\u000a- Typo fixes\u000a\u000aFixes: 35e07d234739 (\"net: socionext: remove mmio reads on Tx\")\u000aSigned-off-by: Ilias Apalodimas \u000aAcked-by: Ard Biesheuvel \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "a98c15177f72ae3c0a736bb324e66c279bf94899", "msg" : "net: netsec: initialize tx ring on ndo_open", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/socionext/netsec.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/cpu/cacheinfo.c" ], "commitId" : "1d4bf99c6a601e56ed010a4c184e34a2d2aebc35", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/cacheinfo: Fix a -Wtype-limits warning\u000a\u000a[ Upstream commit 1b7aebf0487613033aff26420e32fa2076d52846 ]\u000a\u000acpuinfo_x86.x86_model is an unsigned type, so comparing against zero\u000awill generate a compilation warning:\u000a\u000a arch/x86/kernel/cpu/cacheinfo.c: In function 'cacheinfo_amd_init_llc_id':\u000a arch/x86/kernel/cpu/cacheinfo.c:662:19: warning: comparison is always true \\\u000a due to limited range of data type [-Wtype-limits]\u000a\u000aRemove the unnecessary lower bound check.\u000a\u000a [ bp: Massage. ]\u000a\u000aFixes: 68091ee7ac3c (\"x86/CPU/AMD: Calculate last level cache ID from number of sharing threads\")\u000aSigned-off-by: Qian Cai \u000aSigned-off-by: Borislav Petkov \u000aReviewed-by: Sean Christopherson \u000aCc: \"Gustavo A. R. Silva\" \u000aCc: \"H. Peter Anvin\" \u000aCc: Ingo Molnar \u000aCc: Masami Hiramatsu \u000aCc: Pu Wen \u000aCc: Suravee Suthikulpanit \u000aCc: Thomas Gleixner \u000aCc: x86-ml \u000aLink: https://lkml.kernel.org/r/1560954773-11967-1-git-send-email-cai@lca.pw\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "1d4bf99c6a601e56ed010a4c184e34a2d2aebc35", "msg" : "x86/cacheinfo: Fix a -Wtype-limits warning", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/cpu/cacheinfo.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/blk-iolatency.c" ], "commitId" : "c8632e34f614245c7299ccf7ad6d0976dff002de", "timestamp" : 1564125157000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "blk-iolatency: only account submitted bios\u000a\u000a[ Upstream commit a3fb01ba5af066521f3f3421839e501bb2c71805 ]\u000a\u000aAs is, iolatency recognizes done_bio and cleanup as ending paths. If a\u000arequest is marked REQ_NOWAIT and fails to get a request, the bio is\u000acleaned up via rq_qos_cleanup() and ended in bio_wouldblock_error().\u000aThis results in underflowing the inflight counter. Fix this by only\u000aaccounting bios that were actually submitted.\u000a\u000aSigned-off-by: Dennis Zhou \u000aCc: Josef Bacik \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:37 +0200", "id" : "c8632e34f614245c7299ccf7ad6d0976dff002de", "msg" : "blk-iolatency: only account submitted bios", "paths" : [ { "editType" : "edit", "file" : "block/blk-iolatency.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/acpi/acpica/evgpe.c", "drivers/acpi/acpica/evxfgpe.c", "drivers/acpi/acpica/evgpeblk.c", "drivers/acpi/acpica/acevents.h", "drivers/acpi/acpica/evxface.c" ], "commitId" : "467ebe4244808c560e9d93e8c0de3ef5da857523", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ACPICA: Clear status of GPEs on first direct enable\u000a\u000a[ Upstream commit 44758bafa53602f2581a6857bb20b55d4d8ad5b2 ]\u000a\u000aACPI GPEs (other than the EC one) can be enabled in two situations.\u000aFirst, the GPEs with existing _Lxx and _Exx methods are enabled\u000aimplicitly by ACPICA during system initialization. Second, the\u000aGPEs without these methods (like GPEs listed by _PRW objects for\u000awakeup devices) need to be enabled directly by the code that is\u000agoing to use them (e.g. ACPI power management or device drivers).\u000a\u000aIn the former case, if the status of a given GPE is set to start\u000awith, its handler method (either _Lxx or _Exx) needs to be invoked\u000ato take care of the events (possibly) signaled before the GPE was\u000aenabled. In the latter case, however, the first caller of\u000aacpi_enable_gpe() for a given GPE should not be expected to care\u000aabout any events that might be signaled through it earlier. In\u000athat case, it is better to clear the status of the GPE before\u000aenabling it, to prevent stale events from triggering unwanted\u000aactions (like spurious system resume, for example).\u000a\u000aFor this reason, modify acpi_ev_add_gpe_reference() to take an\u000aadditional boolean argument indicating whether or not the GPE\u000astatus needs to be cleared when its reference counter changes from\u000azero to one and make acpi_enable_gpe() pass TRUE to it through\u000athat new argument.\u000a\u000aFixes: 18996f2db918 (\"ACPICA: Events: Stop unconditionally clearing ACPI IRQs during suspend/resume\")\u000aReported-by: Furquan Shaikh \u000aTested-by: Furquan Shaikh \u000aTested-by: Mika Westerberg \u000aSigned-off-by: Rafael J. Wysocki \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "467ebe4244808c560e9d93e8c0de3ef5da857523", "msg" : "ACPICA: Clear status of GPEs on first direct enable", "paths" : [ { "editType" : "edit", "file" : "drivers/acpi/acpica/acevents.h" }, { "editType" : "edit", "file" : "drivers/acpi/acpica/evxface.c" }, { "editType" : "edit", "file" : "drivers/acpi/acpica/evgpe.c" }, { "editType" : "edit", "file" : "drivers/acpi/acpica/evgpeblk.c" }, { "editType" : "edit", "file" : "drivers/acpi/acpica/evxfgpe.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/spi/spi.c" ], "commitId" : "a2fd0a9bc30056a262831d6610d3edeaa3b04c1b", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "spi: fix ctrl->num_chipselect constraint\u000a\u000a[ Upstream commit f9481b08220d7dc1ff21e296a330ee8b721b44e4 ]\u000a\u000aat91sam9g25ek showed the following error at probe:\u000aatmel_spi f0000000.spi: Using dma0chan2 (tx) and dma0chan3 (rx)\u000afor DMA transfers\u000aatmel_spi: probe of f0000000.spi failed with error -22\u000a\u000aCommit 0a919ae49223 (\"spi: Don't call spi_get_gpio_descs() before device name is set\")\u000amoved the calling of spi_get_gpio_descs() after ctrl->dev is set,\u000abut didn't move the !ctrl->num_chipselect check. When there are\u000achip selects in the device tree, the spi-atmel driver lets the\u000aSPI core discover them when registering the SPI master.\u000aThe ctrl->num_chipselect is thus expected to be set by\u000aspi_get_gpio_descs().\u000a\u000aMove the !ctlr->num_chipselect after spi_get_gpio_descs() as it was\u000abefore the aforementioned commit. While touching this block, get rid\u000aof the explicit comparison with 0 and update the commenting style.\u000a\u000aFixes: 0a919ae49223 (\"spi: Don't call spi_get_gpio_descs() before device name is set\")\u000aSigned-off-by: Tudor Ambarus \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "a2fd0a9bc30056a262831d6610d3edeaa3b04c1b", "msg" : "spi: fix ctrl->num_chipselect constraint", "paths" : [ { "editType" : "edit", "file" : "drivers/spi/spi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/edac/edac_mc_sysfs.c" ], "commitId" : "4b0361247eedcfbdb743d99d3ea63a1838e8cf31", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "EDAC/sysfs: Drop device references properly\u000a\u000a[ Upstream commit 7adc05d2dc3af95e4e1534841d58f736262142cd ]\u000a\u000aDo put_device() if device_add() fails.\u000a\u000a [ bp: do device_del() for the successfully created devices in\u000a edac_create_csrow_objects(), on the unwind path. ]\u000a\u000aSigned-off-by: Greg KH \u000aSigned-off-by: Borislav Petkov \u000aLink: https://lkml.kernel.org/r/20190427214925.GE16338@kroah.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "4b0361247eedcfbdb743d99d3ea63a1838e8cf31", "msg" : "EDAC/sysfs: Drop device references properly", "paths" : [ { "editType" : "edit", "file" : "drivers/edac/edac_mc_sysfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/edac/edac_mc_sysfs.c" ], "commitId" : "3db69908831f638f0a9e975700ea52a21e72e573", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "EDAC/sysfs: Fix memory leak when creating a csrow object\u000a\u000a[ Upstream commit 585fb3d93d32dbe89e718b85009f9c322cc554cd ]\u000a\u000aIn edac_create_csrow_object(), the reference to the object is not\u000areleased when adding the device to the device hierarchy fails\u000a(device_add()). This may result in a memory leak.\u000a\u000aSigned-off-by: Pan Bian \u000aSigned-off-by: Borislav Petkov \u000aReviewed-by: Greg Kroah-Hartman \u000aCc: James Morse \u000aCc: Mauro Carvalho Chehab \u000aCc: linux-edac \u000aLink: https://lkml.kernel.org/r/1555554438-103953-1-git-send-email-bianpan2016@163.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "3db69908831f638f0a9e975700ea52a21e72e573", "msg" : "EDAC/sysfs: Fix memory leak when creating a csrow object", "paths" : [ { "editType" : "edit", "file" : "drivers/edac/edac_mc_sysfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/nvme/host/core.c" ], "commitId" : "942c09be53892d636a78f6d8a188990277ba104f", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nvme: fix possible io failures when removing multipathed ns\u000a\u000a[ Upstream commit 2181e455612a8db2761eabbf126640552a451e96 ]\u000a\u000aWhen a shared namespace is removed, we call blk_cleanup_queue()\u000awhen the device can still be accessed as the current path and this can\u000aresult in submission to a dying queue. Hence, direct_make_request()\u000acalled by our mpath device may fail (propagating the failure to userspace).\u000aInstead, we want to failover this I/O to a different path if one exists.\u000aThus, before we cleanup the request queue, we make sure that the device is\u000acleared from the current path nor it can be selected again as such.\u000a\u000aFix this by:\u000a- clear the ns from the head->list and synchronize rcu to make sure there is\u000a no concurrent path search that restores it as the current path\u000a- clear the mpath current path in order to trigger a subsequent path search\u000a and sync srcu to wait for any ongoing request submissions\u000a- safely continue to namespace removal and blk_cleanup_queue\u000a\u000aSigned-off-by: Anton Eidelman \u000aSigned-off-by: Sagi Grimberg \u000aSigned-off-by: Christoph Hellwig \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "942c09be53892d636a78f6d8a188990277ba104f", "msg" : "nvme: fix possible io failures when removing multipathed ns", "paths" : [ { "editType" : "edit", "file" : "drivers/nvme/host/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/nvme/host/pci.c" ], "commitId" : "bd3df6549b4efe854d2e3c60e00641b07aed9062", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nvme-pci: properly report state change failure in nvme_reset_work\u000a\u000a[ Upstream commit cee6c269b016ba89c62e34d6bccb103ee2c7de4f ]\u000a\u000aIf the state change to NVME_CTRL_CONNECTING fails, the dmesg is going to\u000abe like:\u000a\u000a [ 293.689160] nvme nvme0: failed to mark controller CONNECTING\u000a [ 293.689160] nvme nvme0: Removing after probe failure status: 0\u000a\u000aEven it prints the first line to indicate the situation, the second line\u000ais not proper because the status is 0 which means normally success of\u000athe previous operation.\u000a\u000aThis patch makes it indicate the proper error value when it fails.\u000a [ 25.932367] nvme nvme0: failed to mark controller CONNECTING\u000a [ 25.932369] nvme nvme0: Removing after probe failure status: -16\u000a\u000aThis situation is able to be easily reproduced by:\u000a root@target:~# rmmod nvme && modprobe nvme && rmmod nvme\u000a\u000aSigned-off-by: Minwoo Im \u000aReviewed-by: Chaitanya Kulkarni \u000aSigned-off-by: Christoph Hellwig \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "bd3df6549b4efe854d2e3c60e00641b07aed9062", "msg" : "nvme-pci: properly report state change failure in nvme_reset_work", "paths" : [ { "editType" : "edit", "file" : "drivers/nvme/host/pci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/nvme/host/pci.c" ], "commitId" : "e05c9c360bf22eee53cc2af3f23036b8af8492b7", "timestamp" : 1564125158000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nvme-pci: set the errno on ctrl state change error\u000a\u000a[ Upstream commit e71afda49335620e3d9adf56015676db33a3bd86 ]\u000a\u000aThis patch removes the confusing assignment of the variable result at\u000athe time of declaration and sets the value in error cases next to the\u000aplaces where the actual error is happening.\u000a\u000aHere we also set the result value to -ENODEV when we fail at the final\u000actrl state transition in nvme_reset_work(). Without this assignment\u000aresult will hold 0 from nvme_setup_io_queue() and on failure 0 will be\u000apassed to he nvme_remove_dead_ctrl() from final state transition.\u000a\u000aSigned-off-by: Chaitanya Kulkarni \u000aSigned-off-by: Christoph Hellwig \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:38 +0200", "id" : "e05c9c360bf22eee53cc2af3f23036b8af8492b7", "msg" : "nvme-pci: set the errno on ctrl state change error", "paths" : [ { "editType" : "edit", "file" : "drivers/nvme/host/pci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/lightnvm/pblk-core.c" ], "commitId" : "dc7cb8006f0d5a191f8b16f5911864b809175f83", "timestamp" : 1564125159000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "lightnvm: pblk: fix freeing of merged pages\u000a\u000a[ Upstream commit 510fd8ea98fcb586c01aef93d87c060a159ac30a ]\u000a\u000abio_add_pc_page() may merge pages when a bio is padded due to a flush.\u000aFix iteration over the bio to free the correct pages in case of a merge.\u000a\u000aSigned-off-by: Heiner Litz \u000aReviewed-by: Javier González \u000aSigned-off-by: Matias Bjørling \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:39 +0200", "id" : "dc7cb8006f0d5a191f8b16f5911864b809175f83", "msg" : "lightnvm: pblk: fix freeing of merged pages", "paths" : [ { "editType" : "edit", "file" : "drivers/lightnvm/pblk-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/nvme/host/pci.c" ], "commitId" : "8d81f2b8c864e607f0cbd0282e6051434b68cc03", "timestamp" : 1564125159000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nvme-pci: adjust irq max_vector using num_possible_cpus()\u000a\u000a[ Upstream commit dad77d63903e91a2e97a0c984cabe5d36e91ba60 ]\u000a\u000aIf the \"irq_queues\" are greater than num_possible_cpus(),\u000anvme_calc_irq_sets() can have irq set_size for HCTX_TYPE_DEFAULT greater\u000athan it can be afforded.\u000a2039 affd->set_size[HCTX_TYPE_DEFAULT] = nrirqs - nr_read_queues;\u000a\u000aIt might cause a WARN() from the irq_build_affinity_masks() like [1]:\u000a220 if (nr_present < numvecs)\u000a221 WARN_ON(nr_present + nr_others < numvecs);\u000a\u000aThis patch prevents it from the WARN() by adjusting the max_vector value\u000afrom the nvme_setup_irqs().\u000a\u000a[1] WARN messages when modprobe nvme write_queues=32 poll_queues=0:\u000aroot@target:~/nvme# nproc\u000a8\u000aroot@target:~/nvme# modprobe nvme write_queues=32 poll_queues=0\u000a[ 17.925326] nvme nvme0: pci function 0000:00:04.0\u000a[ 17.940601] WARNING: CPU: 3 PID: 1030 at kernel/irq/affinity.c:221 irq_create_affinity_masks+0x222/0x330\u000a[ 17.940602] Modules linked in: nvme nvme_core [last unloaded: nvme]\u000a[ 17.940605] CPU: 3 PID: 1030 Comm: kworker/u17:4 Tainted: G W 5.1.0+ #156\u000a[ 17.940605] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014\u000a[ 17.940608] Workqueue: nvme-reset-wq nvme_reset_work [nvme]\u000a[ 17.940609] RIP: 0010:irq_create_affinity_masks+0x222/0x330\u000a[ 17.940611] Code: 4c 8d 4c 24 28 4c 8d 44 24 30 e8 c9 fa ff ff 89 44 24 18 e8 c0 38 fa ff 8b 44 24 18 44 8b 54 24 1c 5a 44 01 d0 41 39 c4 76 02 <0f> 0b 48 89 df 44 01 e5 e8 f1 ce 10 00 48 8b 34 24 44 89 f0 44 01\u000a[ 17.940611] RSP: 0018:ffffc90002277c50 EFLAGS: 00010216\u000a[ 17.940612] RAX: 0000000000000008 RBX: ffff88807ca48860 RCX: 0000000000000000\u000a[ 17.940612] RDX: ffff88807bc03800 RSI: 0000000000000020 RDI: 0000000000000000\u000a[ 17.940613] RBP: 0000000000000001 R08: ffffc90002277c78 R09: ffffc90002277c70\u000a[ 17.940613] R10: 0000000000000008 R11: 0000000000000001 R12: 0000000000000020\u000a[ 17.940614] R13: 0000000000025d08 R14: 0000000000000001 R15: ffff88807bc03800\u000a[ 17.940614] FS: 0000000000000000(0000) GS:ffff88807db80000(0000) knlGS:0000000000000000\u000a[ 17.940616] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 17.940617] CR2: 00005635e583f790 CR3: 000000000240a000 CR4: 00000000000006e0\u000a[ 17.940617] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\u000a[ 17.940618] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\u000a[ 17.940618] Call Trace:\u000a[ 17.940622] __pci_enable_msix_range+0x215/0x540\u000a[ 17.940623] ? kernfs_put+0x117/0x160\u000a[ 17.940625] pci_alloc_irq_vectors_affinity+0x74/0x110\u000a[ 17.940626] nvme_reset_work+0xc30/0x1397 [nvme]\u000a[ 17.940628] ? __switch_to_asm+0x34/0x70\u000a[ 17.940628] ? __switch_to_asm+0x40/0x70\u000a[ 17.940629] ? __switch_to_asm+0x34/0x70\u000a[ 17.940630] ? __switch_to_asm+0x40/0x70\u000a[ 17.940630] ? __switch_to_asm+0x34/0x70\u000a[ 17.940631] ? __switch_to_asm+0x40/0x70\u000a[ 17.940632] ? nvme_irq_check+0x30/0x30 [nvme]\u000a[ 17.940633] process_one_work+0x20b/0x3e0\u000a[ 17.940634] worker_thread+0x1f9/0x3d0\u000a[ 17.940635] ? cancel_delayed_work+0xa0/0xa0\u000a[ 17.940636] kthread+0x117/0x120\u000a[ 17.940637] ? kthread_stop+0xf0/0xf0\u000a[ 17.940638] ret_from_fork+0x3a/0x50\u000a[ 17.940639] ---[ end trace aca8a131361cd42a ]---\u000a[ 17.942124] nvme nvme0: 7/1/0 default/read/poll queues\u000a\u000aSigned-off-by: Minwoo Im \u000aSigned-off-by: Christoph Hellwig \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:39 +0200", "id" : "8d81f2b8c864e607f0cbd0282e6051434b68cc03", "msg" : "nvme-pci: adjust irq max_vector using num_possible_cpus()", "paths" : [ { "editType" : "edit", "file" : "drivers/nvme/host/pci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/kernel/entry.S" ], "commitId" : "7e41783d1a8c678d573b07ddc5f30950f3efb5d1", "timestamp" : 1564125159000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: Do not enable IRQs for ct_user_exit\u000a\u000a[ Upstream commit 9034f6251572a4744597c51dea5ab73a55f2b938 ]\u000a\u000aFor el0_dbg and el0_error, DAIF bits get explicitly cleared before\u000acalling ct_user_exit.\u000a\u000aWhen context tracking is disabled, DAIF gets set (almost) immediately\u000aafter. When context tracking is enabled, among the first things done\u000ais disabling IRQs.\u000a\u000aWhat is actually needed is:\u000a- PSR.D = 0 so the system can be debugged (should be already the case)\u000a- PSR.A = 0 so async error can be handled during context tracking\u000a\u000aDo not clear PSR.I in those two locations.\u000a\u000aReviewed-by: Marc Zyngier \u000aAcked-by: Mark Rutland \u000aReviewed-by: James Morse \u000aCc: Will Deacon \u000aSigned-off-by: Julien Thierry \u000aSigned-off-by: Catalin Marinas \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:39 +0200", "id" : "7e41783d1a8c678d573b07ddc5f30950f3efb5d1", "msg" : "arm64: Do not enable IRQs for ct_user_exit", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/kernel/entry.S" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/xfrm/Kconfig" ], "commitId" : "a275d049f958b18840375309fcda8fe084b8e6b8", "timestamp" : 1564125159000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipsec: select crypto ciphers for xfrm_algo\u000a\u000a[ Upstream commit 597179b0ba550bd83fab1a9d57c42a9343c58514 ]\u000a\u000akernelci.org reports failed builds on arc because of what looks\u000alike an old missed 'select' statement:\u000a\u000anet/xfrm/xfrm_algo.o: In function `xfrm_probe_algs':\u000axfrm_algo.c:(.text+0x1e8): undefined reference to `crypto_has_ahash'\u000a\u000aI don't see this in randconfig builds on other architectures, but\u000ait's fairly clear we want to select the hash code for it, like we\u000ado for all its other users. As Herbert points out, CRYPTO_BLKCIPHER\u000ais also required even though it has not popped up in build tests.\u000a\u000aFixes: 17bc19702221 (\"ipsec: Use skcipher and ahash when probing algorithms\")\u000aSigned-off-by: Arnd Bergmann \u000aAcked-by: Herbert Xu \u000aSigned-off-by: Steffen Klassert \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:39 +0200", "id" : "a275d049f958b18840375309fcda8fe084b8e6b8", "msg" : "ipsec: select crypto ciphers for xfrm_algo", "paths" : [ { "editType" : "edit", "file" : "net/xfrm/Kconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netfilter/ipvs/ip_vs_core.c" ], "commitId" : "affa31e6b08244ab313d1e3d749707f5746747f2", "timestamp" : 1564125159000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipvs: defer hook registration to avoid leaks\u000a\u000a[ Upstream commit cf47a0b882a4e5f6b34c7949d7b293e9287f1972 ]\u000a\u000asyzkaller reports for memory leak when registering hooks [1]\u000a\u000aAs we moved the nf_unregister_net_hooks() call into\u000a__ip_vs_dev_cleanup(), defer the nf_register_net_hooks()\u000acall, so that hooks are allocated and freed from same\u000apernet_operations (ipvs_core_dev_ops).\u000a\u000a[1]\u000aBUG: memory leak\u000aunreferenced object 0xffff88810acd8a80 (size 96):\u000a comm \"syz-executor073\", pid 7254, jiffies 4294950560 (age 22.250s)\u000a hex dump (first 32 bytes):\u000a 02 00 00 00 00 00 00 00 50 8b bb 82 ff ff ff ff ........P.......\u000a 00 00 00 00 00 00 00 00 00 77 bb 82 ff ff ff ff .........w......\u000a backtrace:\u000a [<0000000013db61f1>] kmemleak_alloc_recursive include/linux/kmemleak.h:55 [inline]\u000a [<0000000013db61f1>] slab_post_alloc_hook mm/slab.h:439 [inline]\u000a [<0000000013db61f1>] slab_alloc_node mm/slab.c:3269 [inline]\u000a [<0000000013db61f1>] kmem_cache_alloc_node_trace+0x15b/0x2a0 mm/slab.c:3597\u000a [<000000001a27307d>] __do_kmalloc_node mm/slab.c:3619 [inline]\u000a [<000000001a27307d>] __kmalloc_node+0x38/0x50 mm/slab.c:3627\u000a [<0000000025054add>] kmalloc_node include/linux/slab.h:590 [inline]\u000a [<0000000025054add>] kvmalloc_node+0x4a/0xd0 mm/util.c:431\u000a [<0000000050d1bc00>] kvmalloc include/linux/mm.h:637 [inline]\u000a [<0000000050d1bc00>] kvzalloc include/linux/mm.h:645 [inline]\u000a [<0000000050d1bc00>] allocate_hook_entries_size+0x3b/0x60 net/netfilter/core.c:61\u000a [<00000000e8abe142>] nf_hook_entries_grow+0xae/0x270 net/netfilter/core.c:128\u000a [<000000004b94797c>] __nf_register_net_hook+0x9a/0x170 net/netfilter/core.c:337\u000a [<00000000d1545cbc>] nf_register_net_hook+0x34/0xc0 net/netfilter/core.c:464\u000a [<00000000876c9b55>] nf_register_net_hooks+0x53/0xc0 net/netfilter/core.c:480\u000a [<000000002ea868e0>] __ip_vs_init+0xe8/0x170 net/netfilter/ipvs/ip_vs_core.c:2280\u000a [<000000002eb2d451>] ops_init+0x4c/0x140 net/core/net_namespace.c:130\u000a [<000000000284ec48>] setup_net+0xde/0x230 net/core/net_namespace.c:316\u000a [<00000000a70600fa>] copy_net_ns+0xf0/0x1e0 net/core/net_namespace.c:439\u000a [<00000000ff26c15e>] create_new_namespaces+0x141/0x2a0 kernel/nsproxy.c:107\u000a [<00000000b103dc79>] copy_namespaces+0xa1/0xe0 kernel/nsproxy.c:165\u000a [<000000007cc008a2>] copy_process.part.0+0x11fd/0x2150 kernel/fork.c:2035\u000a [<00000000c344af7c>] copy_process kernel/fork.c:1800 [inline]\u000a [<00000000c344af7c>] _do_fork+0x121/0x4f0 kernel/fork.c:2369\u000a\u000aReported-by: syzbot+722da59ccb264bc19910@syzkaller.appspotmail.com\u000aFixes: 719c7d563c17 (\"ipvs: Fix use-after-free in ip_vs_in\")\u000aSigned-off-by: Julian Anastasov \u000aAcked-by: Simon Horman \u000aSigned-off-by: Pablo Neira Ayuso \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:39 +0200", "id" : "affa31e6b08244ab313d1e3d749707f5746747f2", "msg" : "ipvs: defer hook registration to avoid leaks", "paths" : [ { "editType" : "edit", "file" : "net/netfilter/ipvs/ip_vs_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/s5p-mfc/s5p_mfc_pm.c" ], "commitId" : "c98a3afe2b8d87ea35225851ac03ebee47855c91", "timestamp" : 1564125159000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: s5p-mfc: Make additional clocks optional\u000a\u000a[ Upstream commit e08efef8fe7db87206314c19b341612c719f891a ]\u000a\u000aSince the beginning the second clock ('special', 'sclk') was optional and\u000ait is not available on some variants of Exynos SoCs (i.e. Exynos5420 with\u000av7 of MFC hardware).\u000a\u000aHowever commit 1bce6fb3edf1 (\"[media] s5p-mfc: Rework clock handling\")\u000amade handling of all specified clocks mandatory. This patch restores\u000aoriginal behavior of the driver and fixes its operation on\u000aExynos5420 SoCs.\u000a\u000aFixes: 1bce6fb3edf1 (\"[media] s5p-mfc: Rework clock handling\")\u000aSigned-off-by: Marek Szyprowski \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:39 +0200", "id" : "c98a3afe2b8d87ea35225851ac03ebee47855c91", "msg" : "media: s5p-mfc: Make additional clocks optional", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/s5p-mfc/s5p_mfc_pm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/i2c/adv7511-v4l2.c", "drivers/media/i2c/adv7511.c", "drivers/media/i2c/Makefile" ], "commitId" : "10e60db506ed0ac33af2cfc1014beb117b6cfa90", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: i2c: fix warning same module names\u000a\u000a[ Upstream commit b2ce5617dad254230551feda3599f2cc68e53ad8 ]\u000a\u000aWhen building with CONFIG_VIDEO_ADV7511 and CONFIG_DRM_I2C_ADV7511\u000aenabled as loadable modules, we see the following warning:\u000a\u000a drivers/gpu/drm/bridge/adv7511/adv7511.ko\u000a drivers/media/i2c/adv7511.ko\u000a\u000aRework so that the file is named adv7511-v4l2.c.\u000a\u000aSigned-off-by: Anders Roxell \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "10e60db506ed0ac33af2cfc1014beb117b6cfa90", "msg" : "media: i2c: fix warning same module names", "paths" : [ { "editType" : "delete", "file" : "drivers/media/i2c/adv7511.c" }, { "editType" : "edit", "file" : "drivers/media/i2c/Makefile" }, { "editType" : "add", "file" : "drivers/media/i2c/adv7511-v4l2.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/time/ntp.c" ], "commitId" : "a0d5e56f6a05cb0ba3af8deb8df14af82a3072a9", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ntp: Limit TAI-UTC offset\u000a\u000a[ Upstream commit d897a4ab11dc8a9fda50d2eccc081a96a6385998 ]\u000a\u000aDon't allow the TAI-UTC offset of the system clock to be set by adjtimex()\u000ato a value larger than 100000 seconds.\u000a\u000aThis prevents an overflow in the conversion to int, prevents the CLOCK_TAI\u000aclock from getting too far ahead of the CLOCK_REALTIME clock, and it is\u000astill large enough to allow leap seconds to be inserted at the maximum rate\u000acurrently supported by the kernel (once per day) for the next ~270 years,\u000ahowever unlikely it is that someone can survive a catastrophic event which\u000aslowed down the rotation of the Earth so much.\u000a\u000aReported-by: Weikang shi \u000aSigned-off-by: Miroslav Lichvar \u000aSigned-off-by: Thomas Gleixner \u000aCc: John Stultz \u000aCc: Prarit Bhargava \u000aCc: Richard Cochran \u000aCc: Stephen Boyd \u000aLink: https://lkml.kernel.org/r/20190618154713.20929-1-mlichvar@redhat.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "a0d5e56f6a05cb0ba3af8deb8df14af82a3072a9", "msg" : "ntp: Limit TAI-UTC offset", "paths" : [ { "editType" : "edit", "file" : "kernel/time/ntp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/time/timer_list.c" ], "commitId" : "ee2e483fe7f4bf2930b619ed3b2c2ca2e8f04a4f", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "timer_list: Guard procfs specific code\u000a\u000a[ Upstream commit a9314773a91a1d3b36270085246a6715a326ff00 ]\u000a\u000aWith CONFIG_PROC_FS=n the following warning is emitted:\u000a\u000akernel/time/timer_list.c:361:36: warning: unused variable\u000a'timer_list_sops' [-Wunused-const-variable]\u000a static const struct seq_operations timer_list_sops = {\u000a\u000aAdd #ifdef guard around procfs specific code.\u000a\u000aSigned-off-by: Nathan Huckleberry \u000aSigned-off-by: Thomas Gleixner \u000aReviewed-by: Nick Desaulniers \u000aCc: john.stultz@linaro.org\u000aCc: sboyd@kernel.org\u000aCc: clang-built-linux@googlegroups.com\u000aLink: https://github.com/ClangBuiltLinux/linux/issues/534\u000aLink: https://lkml.kernel.org/r/20190614181604.112297-1-nhuck@google.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "ee2e483fe7f4bf2930b619ed3b2c2ca2e8f04a4f", "msg" : "timer_list: Guard procfs specific code", "paths" : [ { "editType" : "edit", "file" : "kernel/time/timer_list.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/i2c/mt9m111.c" ], "commitId" : "3b12115f3a38f118aae79ccd4d59e33d444f7e68", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: mt9m111: fix fw-node refactoring\u000a\u000a[ Upstream commit 8d4e29a51a954b43e06d916772fa4f50b7e5bbd6 ]\u000a\u000aIn the patch refactoring the fw-node, the mt9m111 was broken for all\u000aplatform_data based platforms, which were the first aim of this\u000adriver. Only the devicetree platform are still functional, probably\u000abecause the testing was done on these.\u000a\u000aThe result is that -EINVAL is systematically return for such platforms,\u000awhat this patch fixes.\u000a\u000a[Sakari Ailus: Rework this to resolve a merge conflict and use dev_fwnode]\u000a\u000aFixes: 98480d65c48c (\"media: mt9m111: allow to setup pixclk polarity\")\u000aSigned-off-by: Robert Jarzmik \u000aSigned-off-by: Sakari Ailus \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "3b12115f3a38f118aae79ccd4d59e33d444f7e68", "msg" : "media: mt9m111: fix fw-node refactoring", "paths" : [ { "editType" : "edit", "file" : "drivers/media/i2c/mt9m111.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/soc-core.c" ], "commitId" : "957834895a27fd6cb73883047f578201a4f1e4b4", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: soc-core: call snd_soc_unbind_card() under mutex_lock;\u000a\u000a[ Upstream commit b545542a0b866f7975254e41c595836e9bc0ff2f ]\u000a\u000acommit 34ac3c3eb8f0c07 (\"ASoC: core: lock client_mutex while removing\u000alink components\") added mutex_lock() at soc_remove_link_components().\u000a\u000aIs is called from snd_soc_unbind_card()\u000a\u000a\u0009snd_soc_unbind_card()\u000a=>\u0009\u0009soc_remove_link_components()\u000a\u0009\u0009soc_cleanup_card_resources()\u000a\u0009\u0009\u0009soc_remove_dai_links()\u000a=>\u0009\u0009\u0009\u0009soc_remove_link_components()\u000a\u000aAnd, there are 2 way to call it.\u000a\u000a(1)\u000a\u0009snd_soc_unregister_component()\u000a**\u0009\u0009mutex_lock()\u000a\u0009\u0009\u0009snd_soc_component_del_unlocked()\u000a=>\u0009\u0009\u0009\u0009snd_soc_unbind_card()\u000a**\u0009\u0009mutex_unlock()\u000a\u000a(2)\u000a\u0009snd_soc_unregister_card()\u000a=>\u0009\u0009snd_soc_unbind_card()\u000a\u000a(1) case is already using mutex_lock() when it calles\u000asnd_soc_unbind_card(), thus, we will get lockdep warning.\u000a\u000acommit 495f926c68ddb90 (\"ASoC: core: Fix deadlock in\u000asnd_soc_instantiate_card()\") tried to fixup it, but still not\u000aenough. We still have lockdep warning when we try unbind/bind.\u000a\u000aWe need mutex_lock() under snd_soc_unregister_card()\u000ainstead of snd_remove_link_components()/snd_soc_unbind_card().\u000a\u000aFixes: 34ac3c3eb8f0c07 (\"ASoC: core: lock client_mutex while removing link components\")\u000aFixes: 495f926c68ddb90 (\"ASoC: core: Fix deadlock in snd_soc_instantiate_card()\")\u000aSigned-off-by: Kuninori Morimoto \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "957834895a27fd6cb73883047f578201a4f1e4b4", "msg" : "ASoC: soc-core: call snd_soc_unbind_card() under mutex_lock;", "paths" : [ { "editType" : "edit", "file" : "sound/soc/soc-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/kernel/acpi.c" ], "commitId" : "67d73cc8f876ff97b244e0428f0d9058cde9bc54", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "acpi/arm64: ignore 5.1 FADTs that are reported as 5.0\u000a\u000a[ Upstream commit 2af22f3ec3ca452f1e79b967f634708ff01ced8a ]\u000a\u000aSome Qualcomm Snapdragon based laptops built to run Microsoft Windows\u000aare clearly ACPI 5.1 based, given that that is the first ACPI revision\u000athat supports ARM, and introduced the FADT 'arm_boot_flags' field,\u000awhich has a non-zero field on those systems.\u000a\u000aSo in these cases, infer from the ARM boot flags that the FADT must be\u000a5.1 or later, and treat it as 5.1.\u000a\u000aAcked-by: Sudeep Holla \u000aTested-by: Lee Jones \u000aReviewed-by: Graeme Gregory \u000aAcked-by: Lorenzo Pieralisi \u000aAcked-by: Hanjun Guo \u000aSigned-off-by: Ard Biesheuvel \u000aSigned-off-by: Catalin Marinas \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "67d73cc8f876ff97b244e0428f0d9058cde9bc54", "msg" : "acpi/arm64: ignore 5.1 FADTs that are reported as 5.0", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/kernel/acpi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/coda/coda-bit.c" ], "commitId" : "b6a853dd743b13f559ad153ce6083b331d4b908c", "timestamp" : 1564125160000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: coda: fix mpeg2 sequence number handling\u000a\u000a[ Upstream commit 56d159a4ec6d8da7313aac6fcbb95d8fffe689ba ]\u000a\u000aSequence number handling assumed that the BIT processor frame number\u000astarts counting at 1, but this is not true for the MPEG-2 decoder,\u000awhich starts at 0. Fix the sequence counter offset detection to handle\u000athis.\u000a\u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:40 +0200", "id" : "b6a853dd743b13f559ad153ce6083b331d4b908c", "msg" : "media: coda: fix mpeg2 sequence number handling", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/coda/coda-bit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/coda/coda-common.c" ], "commitId" : "cc1c3011f7e817ca66856abf52a93368100fd043", "timestamp" : 1564125161000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: coda: fix last buffer handling in V4L2_ENC_CMD_STOP\u000a\u000a[ Upstream commit f3775f89852d167990b0d718587774cf00d22ac2 ]\u000a\u000acoda_encoder_cmd() is racy, as the last scheduled picture run worker can\u000astill be in-flight while the ENC_CMD_STOP command is issued. Depending\u000aon the exact timing the sequence numbers might already be changed, but\u000athe last buffer might not have been put on the destination queue yet.\u000a\u000aIn this case the current implementation would prematurely wake the\u000adestination queue with last_buffer_dequeued=true, causing userspace to\u000acall streamoff before the last buffer is handled.\u000a\u000aClose this race window by synchronizing with the pic_run_worker before\u000adoing the sequence check.\u000a\u000aSigned-off-by: Marco Felsch \u000a[l.stach@pengutronix.de: switch to flush_work, reword commit message]\u000aSigned-off-by: Lucas Stach \u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:41 +0200", "id" : "cc1c3011f7e817ca66856abf52a93368100fd043", "msg" : "media: coda: fix last buffer handling in V4L2_ENC_CMD_STOP", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/coda/coda-common.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/coda/coda-bit.c" ], "commitId" : "d0e10dee00131b836970f32d17721a2a73e3eab8", "timestamp" : 1564125161000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: coda: increment sequence offset for the last returned frame\u000a\u000a[ Upstream commit b3b7d96817cdb8b6fc353867705275dce8f41ccc ]\u000a\u000aIf no more frames are decoded in bitstream end mode, and a previously\u000adecoded frame has been returned, the firmware still increments the frame\u000anumber. To avoid a sequence number mismatch after decoder restart,\u000aincrement the sequence_offset correction parameter.\u000a\u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:41 +0200", "id" : "d0e10dee00131b836970f32d17721a2a73e3eab8", "msg" : "media: coda: increment sequence offset for the last returned frame", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/coda/coda-bit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/vimc/vimc-capture.c" ], "commitId" : "e116077a17925b86b4e762f8800fe477f07e4b58", "timestamp" : 1564125161000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: vimc: cap: check v4l2_fill_pixfmt return value\u000a\u000a[ Upstream commit 77ae46e11df5c96bb4582633851f838f5d954df4 ]\u000a\u000av4l2_fill_pixfmt() returns -EINVAL if the pixelformat used as parameter is\u000ainvalid or if the user is trying to use a multiplanar format with the\u000asingleplanar API. Currently, the vimc_cap_try_fmt_vid_cap() returns such\u000avalue, but vimc_cap_s_fmt_vid_cap() is ignoring it. Fix that and returns\u000aan error value if vimc_cap_try_fmt_vid_cap() has failed.\u000a\u000aSigned-off-by: André Almeida \u000aSuggested-by: Helen Koike \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:41 +0200", "id" : "e116077a17925b86b4e762f8800fe477f07e4b58", "msg" : "media: vimc: cap: check v4l2_fill_pixfmt return value", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/vimc/vimc-capture.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/usb/hdpvr/hdpvr-video.c" ], "commitId" : "93ba4c724b8ff6195851583e3f9c5305434019db", "timestamp" : 1564125161000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: hdpvr: fix locking and a missing msleep\u000a\u000a[ Upstream commit 6bc5a4a1927556ff9adce1aa95ea408c95453225 ]\u000a\u000aThis driver has three locking issues:\u000a\u000a- The wait_event_interruptible() condition calls hdpvr_get_next_buffer(dev)\u000a which uses a mutex, which is not allowed. Rewrite with list_empty_careful()\u000a that doesn't need locking.\u000a\u000a- In hdpvr_read() the call to hdpvr_stop_streaming() didn't lock io_mutex,\u000a but it should have since stop_streaming expects that.\u000a\u000a- In hdpvr_device_release() io_mutex was locked when calling flush_work(),\u000a but there it shouldn't take that mutex since the work done by flush_work()\u000a also wants to lock that mutex.\u000a\u000aThere are also two other changes (suggested by Keith):\u000a\u000a- msecs_to_jiffies(4000); (a NOP) should have been msleep(4000).\u000a- Change v4l2_dbg to v4l2_info to always log if streaming had to be restarted.\u000a\u000aReported-by: Keith Pyle \u000aSuggested-by: Keith Pyle \u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:41 +0200", "id" : "93ba4c724b8ff6195851583e3f9c5305434019db", "msg" : "media: hdpvr: fix locking and a missing msleep", "paths" : [ { "editType" : "edit", "file" : "drivers/media/usb/hdpvr/hdpvr-video.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c" ], "commitId" : "dc654e84ab342fec88590101576d513629705b61", "timestamp" : 1564125161000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: sun8i: force select external PHY when no internal one\u000a\u000a[ Upstream commit 0fec7e72ae1391bb2d7527efb54fe6ae88acabce ]\u000a\u000aThe PHY selection bit also exists on SoCs without an internal PHY; if it's\u000aset to 1 (internal PHY, default value) then the MAC will not make use of\u000aany PHY on such SoCs.\u000a\u000aThis problem appears when adapting for H6, which has no real internal PHY\u000a(the \"internal PHY\" on H6 is not on-die, but on a co-packaged AC200 chip,\u000aconnected via RMII interface at GPIO bank A).\u000a\u000aForce the PHY selection bit to 0 when the SOC doesn't have an internal PHY,\u000ato address the problem of a wrong default value.\u000a\u000aSigned-off-by: Icenowy Zheng \u000aSigned-off-by: Ondrej Jirman \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:41 +0200", "id" : "dc654e84ab342fec88590101576d513629705b61", "msg" : "net: stmmac: sun8i: force select external PHY when no internal one", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/realtek/rtlwifi/usb.c" ], "commitId" : "e65065795a7b5ec6730056da2f324e0923760625", "timestamp" : 1564125161000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rtlwifi: rtl8192cu: fix error handle when usb probe failed\u000a\u000a[ Upstream commit 6c0ed66f1a5b84e2a812c7c2d6571a5621bf3396 ]\u000a\u000artl_usb_probe() must do error handle rtl_deinit_core() only if\u000artl_init_core() is done, otherwise goto error_out2.\u000a\u000a| usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0\u000a| rtl_usb: reg 0xf0, usbctrl_vendorreq TimeOut! status:0xffffffb9 value=0x0\u000a| rtl8192cu: Chip version 0x10\u000a| rtl_usb: reg 0xa, usbctrl_vendorreq TimeOut! status:0xffffffb9 value=0x0\u000a| rtl_usb: Too few input end points found\u000a| INFO: trying to register non-static key.\u000a| the code is fine but needs lockdep annotation.\u000a| turning off the locking correctness validator.\u000a| CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.1.0-rc4-319354-g9a33b36 #3\u000a| Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS\u000a| Google 01/01/2011\u000a| Workqueue: usb_hub_wq hub_event\u000a| Call Trace:\u000a| __dump_stack lib/dump_stack.c:77 [inline]\u000a| dump_stack+0xe8/0x16e lib/dump_stack.c:113\u000a| assign_lock_key kernel/locking/lockdep.c:786 [inline]\u000a| register_lock_class+0x11b8/0x1250 kernel/locking/lockdep.c:1095\u000a| __lock_acquire+0xfb/0x37c0 kernel/locking/lockdep.c:3582\u000a| lock_acquire+0x10d/0x2f0 kernel/locking/lockdep.c:4211\u000a| __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\u000a| _raw_spin_lock_irqsave+0x44/0x60 kernel/locking/spinlock.c:152\u000a| rtl_c2hcmd_launcher+0xd1/0x390\u000a| drivers/net/wireless/realtek/rtlwifi/base.c:2344\u000a| rtl_deinit_core+0x25/0x2d0 drivers/net/wireless/realtek/rtlwifi/base.c:574\u000a| rtl_usb_probe.cold+0x861/0xa70\u000a| drivers/net/wireless/realtek/rtlwifi/usb.c:1093\u000a| usb_probe_interface+0x31d/0x820 drivers/usb/core/driver.c:361\u000a| really_probe+0x2da/0xb10 drivers/base/dd.c:509\u000a| driver_probe_device+0x21d/0x350 drivers/base/dd.c:671\u000a| __device_attach_driver+0x1d8/0x290 drivers/base/dd.c:778\u000a| bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:454\u000a| __device_attach+0x223/0x3a0 drivers/base/dd.c:844\u000a| bus_probe_device+0x1f1/0x2a0 drivers/base/bus.c:514\u000a| device_add+0xad2/0x16e0 drivers/base/core.c:2106\u000a| usb_set_configuration+0xdf7/0x1740 drivers/usb/core/message.c:2021\u000a| generic_probe+0xa2/0xda drivers/usb/core/generic.c:210\u000a| usb_probe_device+0xc0/0x150 drivers/usb/core/driver.c:266\u000a| really_probe+0x2da/0xb10 drivers/base/dd.c:509\u000a| driver_probe_device+0x21d/0x350 drivers/base/dd.c:671\u000a| __device_attach_driver+0x1d8/0x290 drivers/base/dd.c:778\u000a| bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:454\u000a| __device_attach+0x223/0x3a0 drivers/base/dd.c:844\u000a| bus_probe_device+0x1f1/0x2a0 drivers/base/bus.c:514\u000a| device_add+0xad2/0x16e0 drivers/base/core.c:2106\u000a| usb_new_device.cold+0x537/0xccf drivers/usb/core/hub.c:2534\u000a| hub_port_connect drivers/usb/core/hub.c:5089 [inline]\u000a| hub_port_connect_change drivers/usb/core/hub.c:5204 [inline]\u000a| port_event drivers/usb/core/hub.c:5350 [inline]\u000a| hub_event+0x138e/0x3b00 drivers/usb/core/hub.c:5432\u000a| process_one_work+0x90f/0x1580 kernel/workqueue.c:2269\u000a| worker_thread+0x9b/0xe20 kernel/workqueue.c:2415\u000a| kthread+0x313/0x420 kernel/kthread.c:253\u000a| ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352\u000a\u000aReported-by: syzbot+1fcc5ef45175fc774231@syzkaller.appspotmail.com\u000aSigned-off-by: Ping-Ke Shih \u000aAcked-by: Larry Finger \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:41 +0200", "id" : "e65065795a7b5ec6730056da2f324e0923760625", "msg" : "rtlwifi: rtl8192cu: fix error handle when usb probe failed", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/realtek/rtlwifi/usb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/mediatek/mt7601u/dma.c" ], "commitId" : "ce48f658ab79c880401d2f9a72792ea915a3b5d2", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mt7601u: do not schedule rx_tasklet when the device has been disconnected\u000a\u000a[ Upstream commit 4079e8ccabc3b6d1b503f2376123cb515d14921f ]\u000a\u000aDo not schedule rx_tasklet when the usb dongle is disconnected.\u000aMoreover do not grub rx_lock in mt7601u_kill_rx since usb_poison_urb\u000acan run concurrently with urb completion and we can unlink urbs from rx\u000aring in any order.\u000aThis patch fixes the common kernel warning reported when\u000athe device is removed.\u000a\u000a[ 24.921354] usb 3-14: USB disconnect, device number 7\u000a[ 24.921593] ------------[ cut here ]------------\u000a[ 24.921594] RX urb mismatch\u000a[ 24.921675] WARNING: CPU: 4 PID: 163 at drivers/net/wireless/mediatek/mt7601u/dma.c:200 mt7601u_complete_rx+0xcb/0xd0 [mt7601u]\u000a[ 24.921769] CPU: 4 PID: 163 Comm: kworker/4:2 Tainted: G OE 4.19.31-041931-generic #201903231635\u000a[ 24.921770] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014\u000a[ 24.921782] Workqueue: usb_hub_wq hub_event\u000a[ 24.921797] RIP: 0010:mt7601u_complete_rx+0xcb/0xd0 [mt7601u]\u000a[ 24.921800] RSP: 0018:ffff9bd9cfd03d08 EFLAGS: 00010086\u000a[ 24.921802] RAX: 0000000000000000 RBX: ffff9bd9bf043540 RCX: 0000000000000006\u000a[ 24.921803] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff9bd9cfd16420\u000a[ 24.921804] RBP: ffff9bd9cfd03d28 R08: 0000000000000002 R09: 00000000000003a8\u000a[ 24.921805] R10: 0000002f485fca34 R11: 0000000000000000 R12: ffff9bd9bf043c1c\u000a[ 24.921806] R13: ffff9bd9c62fa3c0 R14: 0000000000000082 R15: 0000000000000000\u000a[ 24.921807] FS: 0000000000000000(0000) GS:ffff9bd9cfd00000(0000) knlGS:0000000000000000\u000a[ 24.921808] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 24.921808] CR2: 00007fb2648b0000 CR3: 0000000142c0a004 CR4: 00000000001606e0\u000a[ 24.921809] Call Trace:\u000a[ 24.921812] \u000a[ 24.921819] __usb_hcd_giveback_urb+0x8b/0x140\u000a[ 24.921821] usb_hcd_giveback_urb+0xca/0xe0\u000a[ 24.921828] xhci_giveback_urb_in_irq.isra.42+0x82/0xf0\u000a[ 24.921834] handle_cmd_completion+0xe02/0x10d0\u000a[ 24.921837] xhci_irq+0x274/0x4a0\u000a[ 24.921838] xhci_msi_irq+0x11/0x20\u000a[ 24.921851] __handle_irq_event_percpu+0x44/0x190\u000a[ 24.921856] handle_irq_event_percpu+0x32/0x80\u000a[ 24.921861] handle_irq_event+0x3b/0x5a\u000a[ 24.921867] handle_edge_irq+0x80/0x190\u000a[ 24.921874] handle_irq+0x20/0x30\u000a[ 24.921889] do_IRQ+0x4e/0xe0\u000a[ 24.921891] common_interrupt+0xf/0xf\u000a[ 24.921892] \u000a[ 24.921900] RIP: 0010:usb_hcd_flush_endpoint+0x78/0x180\u000a[ 24.921354] usb 3-14: USB disconnect, device number 7\u000a\u000aSigned-off-by: Lorenzo Bianconi \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "ce48f658ab79c880401d2f9a72792ea915a3b5d2", "msg" : "mt7601u: do not schedule rx_tasklet when the device has been disconnected", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/mediatek/mt7601u/dma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/cpu/mkcapflags.sh" ], "commitId" : "79e5cd366fe761f05980de9b2486175102806765", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/build: Add 'set -e' to mkcapflags.sh to delete broken capflags.c\u000a\u000a[ Upstream commit bc53d3d777f81385c1bb08b07bd1c06450ecc2c1 ]\u000a\u000aWithout 'set -e', shell scripts continue running even after any\u000aerror occurs. The missed 'set -e' is a typical bug in shell scripting.\u000a\u000aFor example, when a disk space shortage occurs while this script is\u000arunning, it actually ends up with generating a truncated capflags.c.\u000a\u000aYet, mkcapflags.sh continues running and exits with 0. So, the build\u000asystem assumes it has succeeded.\u000a\u000aIt will not be re-generated in the next invocation of Make since its\u000atimestamp is newer than that of any of the source files.\u000a\u000aAdd 'set -e' so that any error in this script is caught and propagated\u000ato the build system.\u000a\u000aSince 9c2af1c7377a (\"kbuild: add .DELETE_ON_ERROR special target\"),\u000amake automatically deletes the target on any failure. So, the broken\u000acapflags.c will be deleted automatically.\u000a\u000aSigned-off-by: Masahiro Yamada \u000aSigned-off-by: Thomas Gleixner \u000aCc: \"H. Peter Anvin\" \u000aCc: Borislav Petkov \u000aLink: https://lkml.kernel.org/r/20190625072622.17679-1-yamada.masahiro@socionext.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "79e5cd366fe761f05980de9b2486175102806765", "msg" : "x86/build: Add 'set -e' to mkcapflags.sh to delete broken capflags.c", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/cpu/mkcapflags.sh" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/mediatek/mt7601u/dma.c", "drivers/net/wireless/mediatek/mt7601u/tx.c" ], "commitId" : "5d099deddaebf2f87d5b151459de2b7c4200e649", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mt7601u: fix possible memory leak when the device is disconnected\u000a\u000a[ Upstream commit 23377c200b2eb48a60d0f228b2a2e75ed6ee6060 ]\u000a\u000aWhen the device is disconnected while passing traffic it is possible\u000ato receive out of order urbs causing a memory leak since the skb linked\u000ato the current tx urb is not removed. Fix the issue deallocating the skb\u000acleaning up the tx ring. Moreover this patch fixes the following kernel\u000awarning\u000a\u000a[ 57.480771] usb 1-1: USB disconnect, device number 2\u000a[ 57.483451] ------------[ cut here ]------------\u000a[ 57.483462] TX urb mismatch\u000a[ 57.483481] WARNING: CPU: 1 PID: 32 at drivers/net/wireless/mediatek/mt7601u/dma.c:245 mt7601u_complete_tx+0x165/00\u000a[ 57.483483] Modules linked in:\u000a[ 57.483496] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted 5.2.0-rc1+ #72\u000a[ 57.483498] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.12.0-2.fc30 04/01/2014\u000a[ 57.483502] Workqueue: usb_hub_wq hub_event\u000a[ 57.483507] RIP: 0010:mt7601u_complete_tx+0x165/0x1e0\u000a[ 57.483510] Code: 8b b5 10 04 00 00 8b 8d 14 04 00 00 eb 8b 80 3d b1 cb e1 00 00 75 9e 48 c7 c7 a4 ea 05 82 c6 05 f\u000a[ 57.483513] RSP: 0000:ffffc900000a0d28 EFLAGS: 00010092\u000a[ 57.483516] RAX: 000000000000000f RBX: ffff88802c0a62c0 RCX: ffffc900000a0c2c\u000a[ 57.483518] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff810a8371\u000a[ 57.483520] RBP: ffff88803ced6858 R08: 0000000000000000 R09: 0000000000000001\u000a[ 57.483540] R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000046\u000a[ 57.483542] R13: ffff88802c0a6c88 R14: ffff88803baab540 R15: ffff88803a0cc078\u000a[ 57.483548] FS: 0000000000000000(0000) GS:ffff88803eb00000(0000) knlGS:0000000000000000\u000a[ 57.483550] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 57.483552] CR2: 000055e7f6780100 CR3: 0000000028c86000 CR4: 00000000000006a0\u000a[ 57.483554] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\u000a[ 57.483556] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\u000a[ 57.483559] Call Trace:\u000a[ 57.483561] \u000a[ 57.483565] __usb_hcd_giveback_urb+0x77/0xe0\u000a[ 57.483570] xhci_giveback_urb_in_irq.isra.0+0x8b/0x140\u000a[ 57.483574] handle_cmd_completion+0xf5b/0x12c0\u000a[ 57.483577] xhci_irq+0x1f6/0x1810\u000a[ 57.483581] ? lockdep_hardirqs_on+0x9e/0x180\u000a[ 57.483584] ? _raw_spin_unlock_irq+0x24/0x30\u000a[ 57.483588] __handle_irq_event_percpu+0x3a/0x260\u000a[ 57.483592] handle_irq_event_percpu+0x1c/0x60\u000a[ 57.483595] handle_irq_event+0x2f/0x4c\u000a[ 57.483599] handle_edge_irq+0x7e/0x1a0\u000a[ 57.483603] handle_irq+0x17/0x20\u000a[ 57.483607] do_IRQ+0x54/0x110\u000a[ 57.483610] common_interrupt+0xf/0xf\u000a[ 57.483612] \u000a\u000aAcked-by: Jakub Kicinski \u000aSigned-off-by: Lorenzo Bianconi \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "5d099deddaebf2f87d5b151459de2b7c4200e649", "msg" : "mt7601u: fix possible memory leak when the device is disconnected", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/mediatek/mt7601u/dma.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/mediatek/mt7601u/tx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netfilter/ipvs/ip_vs_ctl.c", "include/net/ip_vs.h", "net/netfilter/ipvs/ip_vs_sync.c" ], "commitId" : "477c2749b1f63cc320a9cf4496483a00256cb4d3", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipvs: fix tinfo memory leak in start_sync_thread\u000a\u000a[ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ]\u000a\u000asyzkaller reports for memory leak in start_sync_thread [1]\u000a\u000aAs Eric points out, kthread may start and stop before the\u000athreadfn function is called, so there is no chance the\u000adata (tinfo in our case) to be released in thread.\u000a\u000aFix this by releasing tinfo in the controlling code instead.\u000a\u000a[1]\u000aBUG: memory leak\u000aunreferenced object 0xffff8881206bf700 (size 32):\u000a comm \"syz-executor761\", pid 7268, jiffies 4294943441 (age 20.470s)\u000a hex dump (first 32 bytes):\u000a 00 40 7c 09 81 88 ff ff 80 45 b8 21 81 88 ff ff .@|......E.!....\u000a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\u000a backtrace:\u000a [<0000000057619e23>] kmemleak_alloc_recursive include/linux/kmemleak.h:55 [inline]\u000a [<0000000057619e23>] slab_post_alloc_hook mm/slab.h:439 [inline]\u000a [<0000000057619e23>] slab_alloc mm/slab.c:3326 [inline]\u000a [<0000000057619e23>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553\u000a [<0000000086ce5479>] kmalloc include/linux/slab.h:547 [inline]\u000a [<0000000086ce5479>] start_sync_thread+0x5d2/0xe10 net/netfilter/ipvs/ip_vs_sync.c:1862\u000a [<000000001a9229cc>] do_ip_vs_set_ctl+0x4c5/0x780 net/netfilter/ipvs/ip_vs_ctl.c:2402\u000a [<00000000ece457c8>] nf_sockopt net/netfilter/nf_sockopt.c:106 [inline]\u000a [<00000000ece457c8>] nf_setsockopt+0x4c/0x80 net/netfilter/nf_sockopt.c:115\u000a [<00000000942f62d4>] ip_setsockopt net/ipv4/ip_sockglue.c:1258 [inline]\u000a [<00000000942f62d4>] ip_setsockopt+0x9b/0xb0 net/ipv4/ip_sockglue.c:1238\u000a [<00000000a56a8ffd>] udp_setsockopt+0x4e/0x90 net/ipv4/udp.c:2616\u000a [<00000000fa895401>] sock_common_setsockopt+0x38/0x50 net/core/sock.c:3130\u000a [<0000000095eef4cf>] __sys_setsockopt+0x98/0x120 net/socket.c:2078\u000a [<000000009747cf88>] __do_sys_setsockopt net/socket.c:2089 [inline]\u000a [<000000009747cf88>] __se_sys_setsockopt net/socket.c:2086 [inline]\u000a [<000000009747cf88>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2086\u000a [<00000000ded8ba80>] do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301\u000a [<00000000893b4ac8>] entry_SYSCALL_64_after_hwframe+0x44/0xa9\u000a\u000aReported-by: syzbot+7e2e50c8adfccd2e5041@syzkaller.appspotmail.com\u000aSuggested-by: Eric Biggers \u000aFixes: 998e7a76804b (\"ipvs: Use kthread_run() instead of doing a double-fork via kernel_thread()\")\u000aSigned-off-by: Julian Anastasov \u000aAcked-by: Simon Horman \u000aSigned-off-by: Pablo Neira Ayuso \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "477c2749b1f63cc320a9cf4496483a00256cb4d3", "msg" : "ipvs: fix tinfo memory leak in start_sync_thread", "paths" : [ { "editType" : "edit", "file" : "net/netfilter/ipvs/ip_vs_ctl.c" }, { "editType" : "edit", "file" : "net/netfilter/ipvs/ip_vs_sync.c" }, { "editType" : "edit", "file" : "include/net/ip_vs.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/sdio.c" ], "commitId" : "4e59c7c62ca7d9c884fa932f3438407211c19766", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: add missing error handling\u000a\u000a[ Upstream commit 4b553f3ca4cbde67399aa3a756c37eb92145b8a1 ]\u000a\u000aIn function ath10k_sdio_mbox_rx_alloc() [sdio.c],\u000aath10k_sdio_mbox_alloc_rx_pkt() is called without handling the error cases.\u000aThis will make the driver think the allocation for skb is successful and\u000atry to access the skb. If we enable failslab, system will easily crash with\u000aNULL pointer dereferencing.\u000a\u000aCall trace of CONFIG_FAILSLAB:\u000aath10k_sdio_irq_handler+0x570/0xa88 [ath10k_sdio]\u000aprocess_sdio_pending_irqs+0x4c/0x174\u000asdio_run_irqs+0x3c/0x64\u000asdio_irq_work+0x1c/0x28\u000a\u000aFixes: d96db25d2025 (\"ath10k: add initial SDIO support\")\u000aSigned-off-by: Claire Chang \u000aReviewed-by: Brian Norris \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "4e59c7c62ca7d9c884fa932f3438407211c19766", "msg" : "ath10k: add missing error handling", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/sdio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/pci.c" ], "commitId" : "080c204b29ba7954d56875d9999f9990a8af2a4d", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: fix fw crash by moving chip reset after napi disabled\u000a\u000a[ Upstream commit 08d80e4cd27ba19f9bee9e5f788f9a9fc440a22f ]\u000a\u000aOn SMP platform, when continuously running wifi up/down, the napi\u000apoll can be scheduled during chip reset, which will call\u000aath10k_pci_has_fw_crashed() to check the fw status. But in the reset\u000aperiod, the value from FW_INDICATOR_ADDRESS register will return\u000a0xdeadbeef, which also be treated as fw crash. Fix the issue by\u000amoving chip reset after napi disabled.\u000a\u000aath10k_pci 0000:01:00.0: firmware crashed! (guid 73b30611-5b1e-4bdd-90b4-64c81eb947b6)\u000aath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe\u000aath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1\u000aath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 4: -16\u000aath10k_pci 0000:01:00.0: failed to read firmware dump area: -16\u000aath10k_pci 0000:01:00.0: Copy Engine register dump:\u000aath10k_pci 0000:01:00.0: [00]: 0x0004a000 0 0 0 0\u000aath10k_pci 0000:01:00.0: [01]: 0x0004a400 0 0 0 0\u000aath10k_pci 0000:01:00.0: [02]: 0x0004a800 0 0 0 0\u000aath10k_pci 0000:01:00.0: [03]: 0x0004ac00 0 0 0 0\u000aath10k_pci 0000:01:00.0: [04]: 0x0004b000 0 0 0 0\u000aath10k_pci 0000:01:00.0: [05]: 0x0004b400 0 0 0 0\u000aath10k_pci 0000:01:00.0: [06]: 0x0004b800 0 0 0 0\u000aath10k_pci 0000:01:00.0: [07]: 0x0004bc00 1 0 1 0\u000aath10k_pci 0000:01:00.0: [08]: 0x0004c000 0 0 0 0\u000aath10k_pci 0000:01:00.0: [09]: 0x0004c400 0 0 0 0\u000aath10k_pci 0000:01:00.0: [10]: 0x0004c800 0 0 0 0\u000aath10k_pci 0000:01:00.0: [11]: 0x0004cc00 0 0 0 0\u000a\u000aTested HW: QCA9984,QCA9887,WCN3990\u000a\u000aSigned-off-by: Miaoqing Pan \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "080c204b29ba7954d56875d9999f9990a8af2a4d", "msg" : "ath10k: fix fw crash by moving chip reset after napi disabled", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/pci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/hw.c" ], "commitId" : "81124baa72858c08ffe8a5e3d9fc5790e247ad83", "timestamp" : 1564125162000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: fix PCIE device wake up failed\u000a\u000a[ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ]\u000a\u000aObserved PCIE device wake up failed after ~120 iterations of\u000asoft-reboot test. The error message is\u000a\"ath10k_pci 0000:01:00.0: failed to wake up device : -110\"\u000a\u000aThe call trace as below:\u000aath10k_pci_probe -> ath10k_pci_force_wake -> ath10k_pci_wake_wait ->\u000aath10k_pci_is_awake\u000a\u000aOnce trigger the device to wake up, we will continuously check the RTC\u000astate until it returns RTC_STATE_V_ON or timeout.\u000a\u000aBut for QCA99x0 chips, we use wrong value for RTC_STATE_V_ON.\u000aOccasionally, we get 0x7 on the fist read, we thought as a failure\u000acase, but actually is the right value, also verified with the spec.\u000aSo fix the issue by changing RTC_STATE_V_ON from 0x5 to 0x7, passed\u000a~2000 iterations.\u000a\u000aTested HW: QCA9984\u000a\u000aSigned-off-by: Miaoqing Pan \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:42 +0200", "id" : "81124baa72858c08ffe8a5e3d9fc5790e247ad83", "msg" : "ath10k: fix PCIE device wake up failed", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/hw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/perf.h", "tools/perf/util/header.c" ], "commitId" : "ad1f4986d43982be9bc412d1363739eaf1d84fab", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf tools: Increase MAX_NR_CPUS and MAX_CACHES\u000a\u000a[ Upstream commit 9f94c7f947e919c343b30f080285af53d0fa9902 ]\u000a\u000aAttempting to profile 1024 or more CPUs with perf causes two errors:\u000a\u000a perf record -a\u000a [ perf record: Woken up X times to write data ]\u000a way too many cpu caches..\u000a [ perf record: Captured and wrote X MB perf.data (X samples) ]\u000a\u000a perf report -C 1024\u000a Error: failed to set cpu bitmap\u000a Requested CPU 1024 too large. Consider raising MAX_NR_CPUS\u000a\u000a Increasing MAX_NR_CPUS from 1024 to 2048 and redefining MAX_CACHES as\u000a MAX_NR_CPUS * 4 returns normal functionality to perf:\u000a\u000a perf record -a\u000a [ perf record: Woken up X times to write data ]\u000a [ perf record: Captured and wrote X MB perf.data (X samples) ]\u000a\u000a perf report -C 1024\u000a ...\u000a\u000aSigned-off-by: Kyle Meyer \u000aCc: Alexander Shishkin \u000aCc: Jiri Olsa \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aLink: http://lkml.kernel.org/r/20190620193630.154025-1-meyerk@stormcage.eag.rdlabs.hpecorp.net\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "ad1f4986d43982be9bc412d1363739eaf1d84fab", "msg" : "perf tools: Increase MAX_NR_CPUS and MAX_CACHES", "paths" : [ { "editType" : "edit", "file" : "tools/perf/perf.h" }, { "editType" : "edit", "file" : "tools/perf/util/header.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/codecs/hdac_hdmi.c" ], "commitId" : "0e47a8349e65ddf32f8b15058582d8e27eec44f3", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: Intel: hdac_hdmi: Set ops to NULL on remove\u000a\u000a[ Upstream commit 0f6ff78540bd1b4df1e0f17806b0ce2e1dff0d78 ]\u000a\u000aWhen we unload Skylake driver we may end up calling\u000ahdac_component_master_unbind(), it uses acomp->audio_ops, which we set\u000ain hdmi_codec_probe(), so we need to set it to NULL in hdmi_codec_remove(),\u000aotherwise we will dereference no longer existing pointer.\u000a\u000aSigned-off-by: Amadeusz Sławiński \u000aReviewed-by: Pierre-Louis Bossart \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "0e47a8349e65ddf32f8b15058582d8e27eec44f3", "msg" : "ASoC: Intel: hdac_hdmi: Set ops to NULL on remove", "paths" : [ { "editType" : "edit", "file" : "sound/soc/codecs/hdac_hdmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/clocksource/timer-tegra20.c" ], "commitId" : "9e94e997b04a497cca915b4781b664651ef30db2", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "clocksource/drivers/tegra: Release all IRQ's on request_irq() error\u000a\u000a[ Upstream commit 7a3916706e858ad0bc3b5629c68168e1449de26a ]\u000a\u000aRelease all requested IRQ's on the request error to properly clean up\u000aallocated resources.\u000a\u000aSigned-off-by: Dmitry Osipenko \u000aAcked-By: Peter De Schrijver \u000aSigned-off-by: Daniel Lezcano \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "9e94e997b04a497cca915b4781b664651ef30db2", "msg" : "clocksource/drivers/tegra: Release all IRQ's on request_irq() error", "paths" : [ { "editType" : "edit", "file" : "drivers/clocksource/timer-tegra20.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/ata/libata-eh.c" ], "commitId" : "c6edf12f810c570543328093ed253a4bd6b52c3f", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "libata: don't request sense data on !ZAC ATA devices\u000a\u000a[ Upstream commit ca156e006add67e4beea7896be395160735e09b0 ]\u000a\u000aZAC support added sense data requesting on error for both ZAC and ATA\u000adevices. This seems to cause erratic error handling behaviors on some\u000aSSDs where the device reports sense data availability and then\u000adelivers the wrong content making EH take the wrong actions. The\u000afailure mode was sporadic on a LITE-ON ssd and couldn't be reliably\u000areproduced.\u000a\u000aThere is no value in requesting sense data from non-ZAC ATA devices\u000awhile there's a significant risk of introducing EH misbehaviors which\u000aare difficult to reproduce and fix. Let's do the sense data dancing\u000aonly for ZAC devices.\u000a\u000aReviewed-by: Hannes Reinecke \u000aTested-by: Masato Suzuki \u000aReviewed-by: Damien Le Moal \u000aSigned-off-by: Tejun Heo \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "c6edf12f810c570543328093ed253a4bd6b52c3f", "msg" : "libata: don't request sense data on !ZAC ATA devices", "paths" : [ { "editType" : "edit", "file" : "drivers/ata/libata-eh.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/clocksource/timer-tegra20.c" ], "commitId" : "34316acedbec50584544d776463cb55ee3af16c9", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "clocksource/drivers/tegra: Restore base address before cleanup\u000a\u000a[ Upstream commit fc9babc2574691d3bbf0428f007b22261fed55c6 ]\u000a\u000aWe're adjusting the timer's base for each per-CPU timer to point to the\u000aactual start of the timer since device-tree defines a compound registers\u000arange that includes all of the timers. In this case the original base\u000aneed to be restore before calling iounmap to unmap the proper address.\u000a\u000aSigned-off-by: Dmitry Osipenko \u000aAcked-by: Jon Hunter \u000aAcked-by: Thierry Reding \u000aSigned-off-by: Daniel Lezcano \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "34316acedbec50584544d776463cb55ee3af16c9", "msg" : "clocksource/drivers/tegra: Restore base address before cleanup", "paths" : [ { "editType" : "edit", "file" : "drivers/clocksource/timer-tegra20.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/cpuhotplug.h", "drivers/clocksource/exynos_mct.c" ], "commitId" : "f7542baeca92ca2b4127eb525e8d8e1266f9a9ee", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "clocksource/drivers/exynos_mct: Increase priority over ARM arch timer\u000a\u000a[ Upstream commit 6282edb72bed5324352522d732080d4c1b9dfed6 ]\u000a\u000aExynos SoCs based on CA7/CA15 have 2 timer interfaces: custom Exynos MCT\u000a(Multi Core Timer) and standard ARM Architected Timers.\u000a\u000aThere are use cases, where both timer interfaces are used simultanously.\u000aOne of such examples is using Exynos MCT for the main system timer and\u000aARM Architected Timers for the KVM and virtualized guests (KVM requires\u000aarch timers).\u000a\u000aExynos Multi-Core Timer driver (exynos_mct) must be however started\u000abefore ARM Architected Timers (arch_timer), because they both share some\u000acommon hardware blocks (global system counter) and turning on MCT is\u000aneeded to get ARM Architected Timer working properly.\u000a\u000aTo ensure selecting Exynos MCT as the main system timer, increase MCT\u000atimer rating. To ensure proper starting order of both timers during\u000asuspend/resume cycle, increase MCT hotplug priority over ARM Archictected\u000aTimers.\u000a\u000aSigned-off-by: Marek Szyprowski \u000aReviewed-by: Krzysztof Kozlowski \u000aReviewed-by: Chanwoo Choi \u000aSigned-off-by: Daniel Lezcano \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "f7542baeca92ca2b4127eb525e8d8e1266f9a9ee", "msg" : "clocksource/drivers/exynos_mct: Increase priority over ARM arch timer", "paths" : [ { "editType" : "edit", "file" : "include/linux/cpuhotplug.h" }, { "editType" : "edit", "file" : "drivers/clocksource/exynos_mct.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netfilter/nf_conntrack_netlink.c" ], "commitId" : "c0e3f909e3cf86dcb83524db052c055634aa0ea8", "timestamp" : 1564125163000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "netfilter: ctnetlink: Fix regression in conntrack entry deletion\u000a\u000a[ Upstream commit e7600865db32b69deb0109b8254244dca592adcf ]\u000a\u000aCommit f8e608982022 (\"netfilter: ctnetlink: Resolve conntrack\u000aL3-protocol flush regression\") introduced a regression in which deletion\u000aof conntrack entries would fail because the L3 protocol information\u000ais replaced by AF_UNSPEC. As a result the search for the entry to be\u000adeleted would turn up empty due to the tuple used to perform the search\u000ais now different from the tuple used to initially set up the entry.\u000a\u000aFor flushing the conntrack table we do however want to keep the option\u000afor nfgenmsg->version to have a non-zero value to allow for newer\u000auser-space tools to request treatment under the new behavior. With that\u000ait is possible to independently flush tables for a defined L3 protocol.\u000aThis was introduced with the enhancements in in commit 59c08c69c278\u000a(\"netfilter: ctnetlink: Support L3 protocol-filter on flush\").\u000a\u000aOlder user-space tools will retain the behavior of flushing all tables\u000aregardless of defined L3 protocol.\u000a\u000aFixes: f8e608982022 (\"netfilter: ctnetlink: Resolve conntrack L3-protocol flush regression\")\u000aSuggested-by: Pablo Neira Ayuso \u000aSigned-off-by: Felix Kaechele \u000aSigned-off-by: Pablo Neira Ayuso \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:43 +0200", "id" : "c0e3f909e3cf86dcb83524db052c055634aa0ea8", "msg" : "netfilter: ctnetlink: Fix regression in conntrack entry deletion", "paths" : [ { "editType" : "edit", "file" : "net/netfilter/nf_conntrack_netlink.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/xdp/xsk_queue.h" ], "commitId" : "eeb491bda927160676c2f213f34ddcc5a3dc2ae6", "timestamp" : 1564125164000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xsk: Properly terminate assignment in xskq_produce_flush_desc\u000a\u000a[ Upstream commit f7019b7b0ad14bde732b8953161994edfc384953 ]\u000a\u000aClang warns:\u000a\u000aIn file included from net/xdp/xsk_queue.c:10:\u000anet/xdp/xsk_queue.h:292:2: warning: expression result unused\u000a[-Wunused-value]\u000a WRITE_ONCE(q->ring->producer, q->prod_tail);\u000a ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\u000ainclude/linux/compiler.h:284:6: note: expanded from macro 'WRITE_ONCE'\u000a __u.__val; \\\u000a ~~~ ^~~~~\u000a1 warning generated.\u000a\u000aThe q->prod_tail assignment has a comma at the end, not a semi-colon.\u000aFix that so clang no longer warns and everything works as expected.\u000a\u000aFixes: c497176cb2e4 (\"xsk: add Rx receive functions and poll support\")\u000aLink: https://github.com/ClangBuiltLinux/linux/issues/544\u000aSigned-off-by: Nathan Chancellor \u000aAcked-by: Nick Desaulniers \u000aAcked-by: Jonathan Lemon \u000aAcked-by: Björn Töpel \u000aAcked-by: Song Liu \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:44 +0200", "id" : "eeb491bda927160676c2f213f34ddcc5a3dc2ae6", "msg" : "xsk: Properly terminate assignment in xskq_produce_flush_desc", "paths" : [ { "editType" : "edit", "file" : "net/xdp/xsk_queue.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "lib/reed_solomon/decode_rs.c" ], "commitId" : "27cb2288aa24af2a9660b3ec4bc02ff877595649", "timestamp" : 1564125164000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rslib: Fix decoding of shortened codes\u000a\u000a[ Upstream commit 2034a42d1747fc1e1eeef2c6f1789c4d0762cb9c ]\u000a\u000aThe decoding of shortenend codes is broken. It only works as expected if\u000athere are no erasures.\u000a\u000aWhen decoding with erasures, Lambda (the error and erasure locator\u000apolynomial) is initialized from the given erasure positions. The pad\u000aparameter is not accounted for by the initialisation code, and hence\u000aLambda is initialized from incorrect erasure positions.\u000a\u000aThe fix is to adjust the erasure positions by the supplied pad.\u000a\u000aSigned-off-by: Ferdinand Blomqvist \u000aSigned-off-by: Thomas Gleixner \u000aLink: https://lkml.kernel.org/r/20190620141039.9874-3-ferdinand.blomqvist@gmail.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:44 +0200", "id" : "27cb2288aa24af2a9660b3ec4bc02ff877595649", "msg" : "rslib: Fix decoding of shortened codes", "paths" : [ { "editType" : "edit", "file" : "lib/reed_solomon/decode_rs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/bpf/core.c" ], "commitId" : "663979279ba51f542064260ba70375ac530c216b", "timestamp" : 1564125164000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: fix BPF_ALU32 | BPF_ARSH on BE arches\u000a\u000a[ Upstream commit 75672dda27bd00109a84cd975c17949ad9c45663 ]\u000a\u000aYauheni reported the following code do not work correctly on BE arches:\u000a\u000a ALU_ARSH_X:\u000a DST = (u64) (u32) ((*(s32 *) &DST) >> SRC);\u000a CONT;\u000a ALU_ARSH_K:\u000a DST = (u64) (u32) ((*(s32 *) &DST) >> IMM);\u000a CONT;\u000a\u000aand are causing failure of test_verifier test 'arsh32 on imm 2' on BE\u000aarches.\u000a\u000aThe code is taking address and interpreting memory directly, so is not\u000aendianness neutral. We should instead perform standard C type casting on\u000athe variable. A u64 to s32 conversion will drop the high 32-bit and reserve\u000athe low 32-bit as signed integer, this is all we want.\u000a\u000aFixes: 2dc6b100f928 (\"bpf: interpreter support BPF_ALU | BPF_ARSH\")\u000aReported-by: Yauheni Kaliuta \u000aReviewed-by: Jakub Kicinski \u000aReviewed-by: Quentin Monnet \u000aSigned-off-by: Jiong Wang \u000aAcked-by: Song Liu \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:44 +0200", "id" : "663979279ba51f542064260ba70375ac530c216b", "msg" : "bpf: fix BPF_ALU32 | BPF_ARSH on BE arches", "paths" : [ { "editType" : "edit", "file" : "kernel/bpf/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "lib/reed_solomon/decode_rs.c" ], "commitId" : "8c1afd1c374ce0576745950d876c64496d733db9", "timestamp" : 1564125164000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rslib: Fix handling of of caller provided syndrome\u000a\u000a[ Upstream commit ef4d6a8556b637ad27c8c2a2cff1dda3da38e9a9 ]\u000a\u000aCheck if the syndrome provided by the caller is zero, and act\u000aaccordingly.\u000a\u000aSigned-off-by: Ferdinand Blomqvist \u000aSigned-off-by: Thomas Gleixner \u000aLink: https://lkml.kernel.org/r/20190620141039.9874-6-ferdinand.blomqvist@gmail.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:44 +0200", "id" : "8c1afd1c374ce0576745950d876c64496d733db9", "msg" : "rslib: Fix handling of of caller provided syndrome", "paths" : [ { "editType" : "edit", "file" : "lib/reed_solomon/decode_rs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpiolib.c", "drivers/regulator/s5m8767.c", "drivers/regulator/da9211-regulator.c", "drivers/regulator/tps65090-regulator.c", "drivers/regulator/s2mps11.c" ], "commitId" : "c0cb5eaba454f3ec727b0a1a3a10cf8848ee346c", "timestamp" : 1564125164000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpio: Fix return value mismatch of function gpiod_get_from_of_node()\u000a\u000a[ Upstream commit 025bf37725f1929542361eef2245df30badf242e ]\u000a\u000aIn case the requested gpio property is not found in the device tree, some\u000acallers of gpiod_get_from_of_node() expect a return value of NULL, others\u000aexpect -ENOENT.\u000aIn particular devm_fwnode_get_index_gpiod_from_child() expects -ENOENT.\u000aCurrently it gets a NULL, which breaks the loop that tries all\u000agpio_suffixes. The result is that a gpio property is not found, even\u000athough it is there.\u000a\u000aThis patch changes gpiod_get_from_of_node() to return -ENOENT instead\u000aof NULL when the requested gpio property is not found in the device\u000atree. Additionally it modifies all calling functions to properly\u000aevaluate the return value.\u000a\u000aAnother approach would be to leave the return value of\u000agpiod_get_from_of_node() as is and fix the bug in\u000adevm_fwnode_get_index_gpiod_from_child(). Other callers would still need\u000ato be reworked. The effort would be the same as with the chosen solution.\u000a\u000aSigned-off-by: Georg Waibel \u000aReviewed-by: Krzysztof Kozlowski \u000aReviewed-by: Linus Walleij \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:44 +0200", "id" : "c0cb5eaba454f3ec727b0a1a3a10cf8848ee346c", "msg" : "gpio: Fix return value mismatch of function gpiod_get_from_of_node()", "paths" : [ { "editType" : "edit", "file" : "drivers/regulator/tps65090-regulator.c" }, { "editType" : "edit", "file" : "drivers/regulator/s5m8767.c" }, { "editType" : "edit", "file" : "drivers/gpio/gpiolib.c" }, { "editType" : "edit", "file" : "drivers/regulator/s2mps11.c" }, { "editType" : "edit", "file" : "drivers/regulator/da9211-regulator.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlx5/core/eswitch.c" ], "commitId" : "e00660b6e50510f6490b33ac8120799624e738db", "timestamp" : 1564125164000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/mlx5: Get vport ACL namespace by vport index\u000a\u000a[ Upstream commit f53297d67800feb5fafd94abd926c889aefee690 ]\u000a\u000aThe ingress and egress ACL root namespaces are created per vport and\u000astored into arrays. However, the vport number is not the same as the\u000aindex. Passing the array index, instead of vport number, to get the\u000acorrect ingress and egress acl namespace.\u000a\u000aFixes: 9b93ab981e3b (\"net/mlx5: Separate ingress/egress namespaces for each vport\")\u000aSigned-off-by: Jianbo Liu \u000aReviewed-by: Oz Shlomo \u000aReviewed-by: Eli Britstein \u000aReviewed-by: Roi Dayan \u000aReviewed-by: Mark Bloch \u000aSigned-off-by: Saeed Mahameed \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:44 +0200", "id" : "e00660b6e50510f6490b33ac8120799624e738db", "msg" : "net/mlx5: Get vport ACL namespace by vport index", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/eswitch.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/ixgbe/ixgbe_phy.h", "drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c" ], "commitId" : "53b3ba901e35ff14ffeac902cb1b9ec31958667b", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ixgbe: Check DDM existence in transceiver before access\u000a\u000a[ Upstream commit 655c91414579d7bb115a4f7898ee726fc18e0984 ]\u000a\u000aSome transceivers may comply with SFF-8472 but not implement the Digital\u000aDiagnostic Monitoring (DDM) interface described in it. The existence of\u000asuch area is specified by bit 6 of byte 92, set to 1 if implemented.\u000a\u000aCurrently, due to not checking this bit ixgbe fails trying to read SFP\u000amodule's eeprom with the follow message:\u000a\u000aethtool -m enP51p1s0f0\u000aCannot get Module EEPROM data: Input/output error\u000a\u000aBecause it fails to read the additional 256 bytes in which it was assumed\u000ato exist the DDM data.\u000a\u000aThis issue was noticed using a Mellanox Passive DAC PN 01FT738. The eeprom\u000adata was confirmed by Mellanox as correct and present in other Passive\u000aDACs in from other manufacturers.\u000a\u000aSigned-off-by: \"Mauro S. M. Rodrigues\" \u000aReviewed-by: Jesse Brandeburg \u000aTested-by: Andrew Bowers \u000aSigned-off-by: Jeff Kirsher \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "53b3ba901e35ff14ffeac902cb1b9ec31958667b", "msg" : "ixgbe: Check DDM existence in transceiver before access", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c" }, { "editType" : "edit", "file" : "drivers/net/ethernet/intel/ixgbe/ixgbe_phy.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/serpent_generic.c" ], "commitId" : "34bfba9d15fdcf827a7a0664599650c81a855db4", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: serpent - mark __serpent_setkey_sbox noinline\u000a\u000a[ Upstream commit 473971187d6727609951858c63bf12b0307ef015 ]\u000a\u000aThe same bug that gcc hit in the past is apparently now showing\u000aup with clang, which decides to inline __serpent_setkey_sbox:\u000a\u000acrypto/serpent_generic.c:268:5: error: stack frame size of 2112 bytes in function '__serpent_setkey' [-Werror,-Wframe-larger-than=]\u000a\u000aMarking it 'noinline' reduces the stack usage from 2112 bytes to\u000a192 and 96 bytes, respectively, and seems to generate more\u000auseful object code.\u000a\u000aFixes: c871c10e4ea7 (\"crypto: serpent - improve __serpent_setkey with UBSAN\")\u000aSigned-off-by: Arnd Bergmann \u000aReviewed-by: Eric Biggers \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "34bfba9d15fdcf827a7a0664599650c81a855db4", "msg" : "crypto: serpent - mark __serpent_setkey_sbox noinline", "paths" : [ { "editType" : "edit", "file" : "crypto/serpent_generic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/asymmetric_keys/Kconfig" ], "commitId" : "58093426f1c1fc7adf74e271b3b3272472344a7c", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: asymmetric_keys - select CRYPTO_HASH where needed\u000a\u000a[ Upstream commit 90acc0653d2bee203174e66d519fbaaa513502de ]\u000a\u000aBuild testing with some core crypto options disabled revealed\u000aa few modules that are missing CRYPTO_HASH:\u000a\u000acrypto/asymmetric_keys/x509_public_key.o: In function `x509_get_sig_params':\u000ax509_public_key.c:(.text+0x4c7): undefined reference to `crypto_alloc_shash'\u000ax509_public_key.c:(.text+0x5e5): undefined reference to `crypto_shash_digest'\u000acrypto/asymmetric_keys/pkcs7_verify.o: In function `pkcs7_digest.isra.0':\u000apkcs7_verify.c:(.text+0xab): undefined reference to `crypto_alloc_shash'\u000apkcs7_verify.c:(.text+0x1b2): undefined reference to `crypto_shash_digest'\u000apkcs7_verify.c:(.text+0x3c1): undefined reference to `crypto_shash_update'\u000apkcs7_verify.c:(.text+0x411): undefined reference to `crypto_shash_finup'\u000a\u000aThis normally doesn't show up in randconfig tests because there is\u000aa large number of other options that select CRYPTO_HASH.\u000a\u000aSigned-off-by: Arnd Bergmann \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "58093426f1c1fc7adf74e271b3b3272472344a7c", "msg" : "crypto: asymmetric_keys - select CRYPTO_HASH where needed", "paths" : [ { "editType" : "edit", "file" : "crypto/asymmetric_keys/Kconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath9k/recv.c" ], "commitId" : "9ef7f897f17e41bc8f0501b29a9b7cc541546d21", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath9k: correctly handle short radar pulses\u000a\u000a[ Upstream commit df5c4150501ee7e86383be88f6490d970adcf157 ]\u000a\u000aIn commit 3c0efb745a17 (\"ath9k: discard undersized packets\")\u000athe lower bound of RX packets was set to 10 (min ACK size) to\u000afilter those that would otherwise be treated as invalid at\u000amac80211.\u000a\u000aAlas, short radar pulses are reported as PHY_ERROR frames\u000awith length set to 3. Therefore their detection stopped\u000aworking after that commit.\u000a\u000aNOTE: ath9k drivers built thereafter will not pass DFS\u000acertification.\u000a\u000aThis extends the criteria for short packets to explicitly\u000ahandle PHY_ERROR frames.\u000a\u000aFixes: 3c0efb745a17 (\"ath9k: discard undersized packets\")\u000aSigned-off-by: Zefir Kurtisi \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "9ef7f897f17e41bc8f0501b29a9b7cc541546d21", "msg" : "ath9k: correctly handle short radar pulses", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath9k/recv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/wil6210/wmi.c" ], "commitId" : "12058bfa8ca6adb2217d5bdd9201d2b4c1af6951", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "wil6210: drop old event after wmi_call timeout\u000a\u000a[ Upstream commit 1a276003111c0404f6bfeffe924c5a21f482428b ]\u000a\u000aThis change fixes a rare race condition of handling WMI events after\u000awmi_call expires.\u000a\u000awmi_recv_cmd immediately handles an event when reply_buf is defined and\u000aa wmi_call is waiting for the event.\u000aHowever, in case the wmi_call has already timed-out, there will be no\u000awaiting/running wmi_call and the event will be queued in WMI queue and\u000awill be handled later in wmi_event_handle.\u000aMeanwhile, a new similar wmi_call for the same command and event may\u000abe issued. In this case, when handling the queued event we got WARN_ON\u000aprinted.\u000a\u000aFixing this case as a valid timeout and drop the unexpected event.\u000a\u000aSigned-off-by: Ahmad Masri \u000aSigned-off-by: Maya Erez \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "12058bfa8ca6adb2217d5bdd9201d2b4c1af6951", "msg" : "wil6210: drop old event after wmi_call timeout", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/wil6210/wmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/edac/edac_mc_sysfs.c", "drivers/edac/edac_module.h" ], "commitId" : "6a512abeddc344ac6d689c9fa3ffaf72ec65841f", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "EDAC: Fix global-out-of-bounds write when setting edac_mc_poll_msec\u000a\u000a[ Upstream commit d8655e7630dafa88bc37f101640e39c736399771 ]\u000a\u000aCommit 9da21b1509d8 (\"EDAC: Poll timeout cannot be zero, p2\") assumes\u000aedac_mc_poll_msec to be unsigned long, but the type of the variable still\u000aremained as int. Setting edac_mc_poll_msec can trigger out-of-bounds\u000awrite.\u000a\u000aReproducer:\u000a\u000a # echo 1001 > /sys/module/edac_core/parameters/edac_mc_poll_msec\u000a\u000aKASAN report:\u000a\u000a BUG: KASAN: global-out-of-bounds in edac_set_poll_msec+0x140/0x150\u000a Write of size 8 at addr ffffffffb91b2d00 by task bash/1996\u000a\u000a CPU: 1 PID: 1996 Comm: bash Not tainted 5.2.0-rc6+ #23\u000a Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-2.fc30 04/01/2014\u000a Call Trace:\u000a dump_stack+0xca/0x13e\u000a print_address_description.cold+0x5/0x246\u000a __kasan_report.cold+0x75/0x9a\u000a ? edac_set_poll_msec+0x140/0x150\u000a kasan_report+0xe/0x20\u000a edac_set_poll_msec+0x140/0x150\u000a ? dimmdev_location_show+0x30/0x30\u000a ? vfs_lock_file+0xe0/0xe0\u000a ? _raw_spin_lock+0x87/0xe0\u000a param_attr_store+0x1b5/0x310\u000a ? param_array_set+0x4f0/0x4f0\u000a module_attr_store+0x58/0x80\u000a ? module_attr_show+0x80/0x80\u000a sysfs_kf_write+0x13d/0x1a0\u000a kernfs_fop_write+0x2bc/0x460\u000a ? sysfs_kf_bin_read+0x270/0x270\u000a ? kernfs_notify+0x1f0/0x1f0\u000a __vfs_write+0x81/0x100\u000a vfs_write+0x1e1/0x560\u000a ksys_write+0x126/0x250\u000a ? __ia32_sys_read+0xb0/0xb0\u000a ? do_syscall_64+0x1f/0x390\u000a do_syscall_64+0xc1/0x390\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a RIP: 0033:0x7fa7caa5e970\u000a Code: 73 01 c3 48 8b 0d 28 d5 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 99 2d 2c 00 00 75 10 b8 01 00 00 00 04\u000a RSP: 002b:00007fff6acfdfe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\u000a RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fa7caa5e970\u000a RDX: 0000000000000005 RSI: 0000000000e95c08 RDI: 0000000000000001\u000a RBP: 0000000000e95c08 R08: 00007fa7cad1e760 R09: 00007fa7cb36a700\u000a R10: 0000000000000073 R11: 0000000000000246 R12: 0000000000000005\u000a R13: 0000000000000001 R14: 00007fa7cad1d600 R15: 0000000000000005\u000a\u000a The buggy address belongs to the variable:\u000a edac_mc_poll_msec+0x0/0x40\u000a\u000a Memory state around the buggy address:\u000a ffffffffb91b2c00: 00 00 00 00 fa fa fa fa 00 00 00 00 fa fa fa fa\u000a ffffffffb91b2c80: 00 00 00 00 fa fa fa fa 00 00 00 00 fa fa fa fa\u000a >ffffffffb91b2d00: 04 fa fa fa fa fa fa fa 04 fa fa fa fa fa fa fa\u000a ^\u000a ffffffffb91b2d80: 04 fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00\u000a ffffffffb91b2e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\u000a\u000aFix it by changing the type of edac_mc_poll_msec to unsigned int.\u000aThe reason why this patch adopts unsigned int rather than unsigned long\u000ais msecs_to_jiffies() assumes arg to be unsigned int. We can avoid\u000ainteger conversion bugs and unsigned int will be large enough for\u000aedac_mc_poll_msec.\u000a\u000aReviewed-by: James Morse \u000aFixes: 9da21b1509d8 (\"EDAC: Poll timeout cannot be zero, p2\")\u000aSigned-off-by: Eiichi Tsukata \u000aSigned-off-by: Tony Luck \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "6a512abeddc344ac6d689c9fa3ffaf72ec65841f", "msg" : "EDAC: Fix global-out-of-bounds write when setting edac_mc_poll_msec", "paths" : [ { "editType" : "edit", "file" : "drivers/edac/edac_mc_sysfs.c" }, { "editType" : "edit", "file" : "drivers/edac/edac_module.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/alloc.c" ], "commitId" : "2e99386f735640d475c07fea556b0eb9cacc277e", "timestamp" : 1564125165000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: check CACHE_SET_IO_DISABLE in allocator code\u000a\u000a[ Upstream commit e775339e1ae1205b47d94881db124c11385e597c ]\u000a\u000aIf CACHE_SET_IO_DISABLE of a cache set flag is set by too many I/O\u000aerrors, currently allocator routines can still continue allocate\u000aspace which may introduce inconsistent metadata state.\u000a\u000aThis patch checkes CACHE_SET_IO_DISABLE bit in following allocator\u000aroutines,\u000a- bch_bucket_alloc()\u000a- __bch_bucket_alloc_set()\u000aOnce CACHE_SET_IO_DISABLE is set on cache set, the allocator routines\u000amay reject allocation request earlier to avoid potential inconsistent\u000ametadata.\u000a\u000aSigned-off-by: Coly Li \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:45 +0200", "id" : "2e99386f735640d475c07fea556b0eb9cacc277e", "msg" : "bcache: check CACHE_SET_IO_DISABLE in allocator code", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/alloc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/journal.c" ], "commitId" : "7afcee1058a4a30972a19c4e37faafe435361133", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: check CACHE_SET_IO_DISABLE bit in bch_journal()\u000a\u000a[ Upstream commit 383ff2183ad16a8842d1fbd9dd3e1cbd66813e64 ]\u000a\u000aWhen too many I/O errors happen on cache set and CACHE_SET_IO_DISABLE\u000abit is set, bch_journal() may continue to work because the journaling\u000abkey might be still in write set yet. The caller of bch_journal() may\u000abelieve the journal still work but the truth is in-memory journal write\u000aset won't be written into cache device any more. This behavior may\u000aintroduce potential inconsistent metadata status.\u000a\u000aThis patch checks CACHE_SET_IO_DISABLE bit at the head of bch_journal(),\u000aif the bit is set, bch_journal() returns NULL immediately to notice\u000acaller to know journal does not work.\u000a\u000aSigned-off-by: Coly Li \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "7afcee1058a4a30972a19c4e37faafe435361133", "msg" : "bcache: check CACHE_SET_IO_DISABLE bit in bch_journal()", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/journal.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/super.c" ], "commitId" : "02d4c4bae0c4e710dc3485cca79801c5c9654c8d", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: acquire bch_register_lock later in cached_dev_free()\u000a\u000a[ Upstream commit 80265d8dfd77792e133793cef44a21323aac2908 ]\u000a\u000aWhen enable lockdep engine, a lockdep warning can be observed when\u000areboot or shutdown system,\u000a\u000a[ 3142.764557][ T1] bcache: bcache_reboot() Stopping all devices:\u000a[ 3142.776265][ T2649]\u000a[ 3142.777159][ T2649] ======================================================\u000a[ 3142.780039][ T2649] WARNING: possible circular locking dependency detected\u000a[ 3142.782869][ T2649] 5.2.0-rc4-lp151.20-default+ #1 Tainted: G W\u000a[ 3142.785684][ T2649] ------------------------------------------------------\u000a[ 3142.788479][ T2649] kworker/3:67/2649 is trying to acquire lock:\u000a[ 3142.790738][ T2649] 00000000aaf02291 ((wq_completion)bcache_writeback_wq){+.+.}, at: flush_workqueue+0x87/0x4c0\u000a[ 3142.794678][ T2649]\u000a[ 3142.794678][ T2649] but task is already holding lock:\u000a[ 3142.797402][ T2649] 000000004fcf89c5 (&bch_register_lock){+.+.}, at: cached_dev_free+0x17/0x120 [bcache]\u000a[ 3142.801462][ T2649]\u000a[ 3142.801462][ T2649] which lock already depends on the new lock.\u000a[ 3142.801462][ T2649]\u000a[ 3142.805277][ T2649]\u000a[ 3142.805277][ T2649] the existing dependency chain (in reverse order) is:\u000a[ 3142.808902][ T2649]\u000a[ 3142.808902][ T2649] -> #2 (&bch_register_lock){+.+.}:\u000a[ 3142.812396][ T2649] __mutex_lock+0x7a/0x9d0\u000a[ 3142.814184][ T2649] cached_dev_free+0x17/0x120 [bcache]\u000a[ 3142.816415][ T2649] process_one_work+0x2a4/0x640\u000a[ 3142.818413][ T2649] worker_thread+0x39/0x3f0\u000a[ 3142.820276][ T2649] kthread+0x125/0x140\u000a[ 3142.822061][ T2649] ret_from_fork+0x3a/0x50\u000a[ 3142.823965][ T2649]\u000a[ 3142.823965][ T2649] -> #1 ((work_completion)(&cl->work)#2){+.+.}:\u000a[ 3142.827244][ T2649] process_one_work+0x277/0x640\u000a[ 3142.829160][ T2649] worker_thread+0x39/0x3f0\u000a[ 3142.830958][ T2649] kthread+0x125/0x140\u000a[ 3142.832674][ T2649] ret_from_fork+0x3a/0x50\u000a[ 3142.834915][ T2649]\u000a[ 3142.834915][ T2649] -> #0 ((wq_completion)bcache_writeback_wq){+.+.}:\u000a[ 3142.838121][ T2649] lock_acquire+0xb4/0x1c0\u000a[ 3142.840025][ T2649] flush_workqueue+0xae/0x4c0\u000a[ 3142.842035][ T2649] drain_workqueue+0xa9/0x180\u000a[ 3142.844042][ T2649] destroy_workqueue+0x17/0x250\u000a[ 3142.846142][ T2649] cached_dev_free+0x52/0x120 [bcache]\u000a[ 3142.848530][ T2649] process_one_work+0x2a4/0x640\u000a[ 3142.850663][ T2649] worker_thread+0x39/0x3f0\u000a[ 3142.852464][ T2649] kthread+0x125/0x140\u000a[ 3142.854106][ T2649] ret_from_fork+0x3a/0x50\u000a[ 3142.855880][ T2649]\u000a[ 3142.855880][ T2649] other info that might help us debug this:\u000a[ 3142.855880][ T2649]\u000a[ 3142.859663][ T2649] Chain exists of:\u000a[ 3142.859663][ T2649] (wq_completion)bcache_writeback_wq --> (work_completion)(&cl->work)#2 --> &bch_register_lock\u000a[ 3142.859663][ T2649]\u000a[ 3142.865424][ T2649] Possible unsafe locking scenario:\u000a[ 3142.865424][ T2649]\u000a[ 3142.868022][ T2649] CPU0 CPU1\u000a[ 3142.869885][ T2649] ---- ----\u000a[ 3142.871751][ T2649] lock(&bch_register_lock);\u000a[ 3142.873379][ T2649] lock((work_completion)(&cl->work)#2);\u000a[ 3142.876399][ T2649] lock(&bch_register_lock);\u000a[ 3142.879727][ T2649] lock((wq_completion)bcache_writeback_wq);\u000a[ 3142.882064][ T2649]\u000a[ 3142.882064][ T2649] *** DEADLOCK ***\u000a[ 3142.882064][ T2649]\u000a[ 3142.885060][ T2649] 3 locks held by kworker/3:67/2649:\u000a[ 3142.887245][ T2649] #0: 00000000e774cdd0 ((wq_completion)events){+.+.}, at: process_one_work+0x21e/0x640\u000a[ 3142.890815][ T2649] #1: 00000000f7df89da ((work_completion)(&cl->work)#2){+.+.}, at: process_one_work+0x21e/0x640\u000a[ 3142.894884][ T2649] #2: 000000004fcf89c5 (&bch_register_lock){+.+.}, at: cached_dev_free+0x17/0x120 [bcache]\u000a[ 3142.898797][ T2649]\u000a[ 3142.898797][ T2649] stack backtrace:\u000a[ 3142.900961][ T2649] CPU: 3 PID: 2649 Comm: kworker/3:67 Tainted: G W 5.2.0-rc4-lp151.20-default+ #1\u000a[ 3142.904789][ T2649] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/13/2018\u000a[ 3142.909168][ T2649] Workqueue: events cached_dev_free [bcache]\u000a[ 3142.911422][ T2649] Call Trace:\u000a[ 3142.912656][ T2649] dump_stack+0x85/0xcb\u000a[ 3142.914181][ T2649] print_circular_bug+0x19a/0x1f0\u000a[ 3142.916193][ T2649] __lock_acquire+0x16cd/0x1850\u000a[ 3142.917936][ T2649] ? __lock_acquire+0x6a8/0x1850\u000a[ 3142.919704][ T2649] ? lock_acquire+0xb4/0x1c0\u000a[ 3142.921335][ T2649] ? find_held_lock+0x34/0xa0\u000a[ 3142.923052][ T2649] lock_acquire+0xb4/0x1c0\u000a[ 3142.924635][ T2649] ? flush_workqueue+0x87/0x4c0\u000a[ 3142.926375][ T2649] flush_workqueue+0xae/0x4c0\u000a[ 3142.928047][ T2649] ? flush_workqueue+0x87/0x4c0\u000a[ 3142.929824][ T2649] ? drain_workqueue+0xa9/0x180\u000a[ 3142.931686][ T2649] drain_workqueue+0xa9/0x180\u000a[ 3142.933534][ T2649] destroy_workqueue+0x17/0x250\u000a[ 3142.935787][ T2649] cached_dev_free+0x52/0x120 [bcache]\u000a[ 3142.937795][ T2649] process_one_work+0x2a4/0x640\u000a[ 3142.939803][ T2649] worker_thread+0x39/0x3f0\u000a[ 3142.941487][ T2649] ? process_one_work+0x640/0x640\u000a[ 3142.943389][ T2649] kthread+0x125/0x140\u000a[ 3142.944894][ T2649] ? kthread_create_worker_on_cpu+0x70/0x70\u000a[ 3142.947744][ T2649] ret_from_fork+0x3a/0x50\u000a[ 3142.970358][ T2649] bcache: bcache_device_free() bcache0 stopped\u000a\u000aHere is how the deadlock happens.\u000a1) bcache_reboot() calls bcache_device_stop(), then inside\u000a bcache_device_stop() BCACHE_DEV_CLOSING bit is set on d->flags.\u000a Then closure_queue(&d->cl) is called to invoke cached_dev_flush().\u000a2) In cached_dev_flush(), cached_dev_free() is called by continu_at().\u000a3) In cached_dev_free(), when stopping the writeback kthread of the\u000a cached device by kthread_stop(), dc->writeback_thread will be waken\u000a up to quite the kthread while-loop, then cached_dev_put() is called\u000a in bch_writeback_thread().\u000a4) Calling cached_dev_put() in writeback kthread may drop dc->count to\u000a 0, then dc->detach kworker is scheduled, which is initialized as\u000a cached_dev_detach_finish().\u000a5) Inside cached_dev_detach_finish(), the last line of code is to call\u000a closure_put(&dc->disk.cl), which drops the last reference counter of\u000a closrure dc->disk.cl, then the callback cached_dev_flush() gets\u000a called.\u000aNow cached_dev_flush() is called for second time in the code path, the\u000afirst time is in step 2). And again bch_register_lock will be acquired\u000aagain, and a A-A lock (lockdep terminology) is happening.\u000a\u000aThe root cause of the above A-A lock is in cached_dev_free(), mutex\u000abch_register_lock is held before stopping writeback kthread and other\u000akworkers. Fortunately now we have variable 'bcache_is_reboot', which may\u000aprevent device registration or unregistration during reboot/shutdown\u000atime, so it is unncessary to hold bch_register_lock such early now.\u000a\u000aThis is how this patch fixes the reboot/shutdown time A-A lock issue:\u000aAfter moving mutex_lock(&bch_register_lock) to a later location where\u000abefore atomic_read(&dc->running) in cached_dev_free(), such A-A lock\u000aproblem can be solved without any reboot time registration race.\u000a\u000aSigned-off-by: Coly Li \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "02d4c4bae0c4e710dc3485cca79801c5c9654c8d", "msg" : "bcache: acquire bch_register_lock later in cached_dev_free()", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/super.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/super.c" ], "commitId" : "2d1169fe13ace760454eac013f2adf0c420d5e23", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: check c->gc_thread by IS_ERR_OR_NULL in cache_set_flush()\u000a\u000a[ Upstream commit b387e9b58679c60f5b1e4313939bd4878204fc37 ]\u000a\u000aWhen system memory is in heavy pressure, bch_gc_thread_start() from\u000arun_cache_set() may fail due to out of memory. In such condition,\u000ac->gc_thread is assigned to -ENOMEM, not NULL pointer. Then in following\u000afailure code path bch_cache_set_error(), when cache_set_flush() gets\u000acalled, the code piece to stop c->gc_thread is broken,\u000a if (!IS_ERR_OR_NULL(c->gc_thread))\u000a kthread_stop(c->gc_thread);\u000a\u000aAnd KASAN catches such NULL pointer deference problem, with the warning\u000ainformation:\u000a\u000a[ 561.207881] ==================================================================\u000a[ 561.207900] BUG: KASAN: null-ptr-deref in kthread_stop+0x3b/0x440\u000a[ 561.207904] Write of size 4 at addr 000000000000001c by task kworker/15:1/313\u000a\u000a[ 561.207913] CPU: 15 PID: 313 Comm: kworker/15:1 Tainted: G W 5.0.0-vanilla+ #3\u000a[ 561.207916] Hardware name: Lenovo ThinkSystem SR650 -[7X05CTO1WW]-/-[7X05CTO1WW]-, BIOS -[IVE136T-2.10]- 03/22/2019\u000a[ 561.207935] Workqueue: events cache_set_flush [bcache]\u000a[ 561.207940] Call Trace:\u000a[ 561.207948] dump_stack+0x9a/0xeb\u000a[ 561.207955] ? kthread_stop+0x3b/0x440\u000a[ 561.207960] ? kthread_stop+0x3b/0x440\u000a[ 561.207965] kasan_report+0x176/0x192\u000a[ 561.207973] ? kthread_stop+0x3b/0x440\u000a[ 561.207981] kthread_stop+0x3b/0x440\u000a[ 561.207995] cache_set_flush+0xd4/0x6d0 [bcache]\u000a[ 561.208008] process_one_work+0x856/0x1620\u000a[ 561.208015] ? find_held_lock+0x39/0x1d0\u000a[ 561.208028] ? drain_workqueue+0x380/0x380\u000a[ 561.208048] worker_thread+0x87/0xb80\u000a[ 561.208058] ? __kthread_parkme+0xb6/0x180\u000a[ 561.208067] ? process_one_work+0x1620/0x1620\u000a[ 561.208072] kthread+0x326/0x3e0\u000a[ 561.208079] ? kthread_create_worker_on_cpu+0xc0/0xc0\u000a[ 561.208090] ret_from_fork+0x3a/0x50\u000a[ 561.208110] ==================================================================\u000a[ 561.208113] Disabling lock debugging due to kernel taint\u000a[ 561.208115] irq event stamp: 11800231\u000a[ 561.208126] hardirqs last enabled at (11800231): [] do_syscall_64+0x18/0x410\u000a[ 561.208127] BUG: unable to handle kernel NULL pointer dereference at 000000000000001c\u000a[ 561.208129] #PF error: [WRITE]\u000a[ 561.312253] hardirqs last disabled at (11800230): [] trace_hardirqs_off_thunk+0x1a/0x1c\u000a[ 561.312259] softirqs last enabled at (11799832): [] __do_softirq+0x5c7/0x8c3\u000a[ 561.405975] PGD 0 P4D 0\u000a[ 561.442494] softirqs last disabled at (11799821): [] irq_exit+0x1ac/0x1e0\u000a[ 561.791359] Oops: 0002 [#1] SMP KASAN NOPTI\u000a[ 561.791362] CPU: 15 PID: 313 Comm: kworker/15:1 Tainted: G B W 5.0.0-vanilla+ #3\u000a[ 561.791363] Hardware name: Lenovo ThinkSystem SR650 -[7X05CTO1WW]-/-[7X05CTO1WW]-, BIOS -[IVE136T-2.10]- 03/22/2019\u000a[ 561.791371] Workqueue: events cache_set_flush [bcache]\u000a[ 561.791374] RIP: 0010:kthread_stop+0x3b/0x440\u000a[ 561.791376] Code: 00 00 65 8b 05 26 d5 e0 7c 89 c0 48 0f a3 05 ec aa df 02 0f 82 dc 02 00 00 4c 8d 63 20 be 04 00 00 00 4c 89 e7 e8 65 c5 53 00 ff 43 20 48 8d 7b 24 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48\u000a[ 561.791377] RSP: 0018:ffff88872fc8fd10 EFLAGS: 00010286\u000a[ 561.838895] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 561.838916] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 561.838934] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 561.838948] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 561.838966] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 561.838979] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 561.838996] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 563.067028] RAX: 0000000000000000 RBX: fffffffffffffffc RCX: ffffffff832dd314\u000a[ 563.067030] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000297\u000a[ 563.067032] RBP: ffff88872fc8fe88 R08: fffffbfff0b8213d R09: fffffbfff0b8213d\u000a[ 563.067034] R10: 0000000000000001 R11: fffffbfff0b8213c R12: 000000000000001c\u000a[ 563.408618] R13: ffff88dc61cc0f68 R14: ffff888102b94900 R15: ffff88dc61cc0f68\u000a[ 563.408620] FS: 0000000000000000(0000) GS:ffff888f7dc00000(0000) knlGS:0000000000000000\u000a[ 563.408622] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 563.408623] CR2: 000000000000001c CR3: 0000000f48a1a004 CR4: 00000000007606e0\u000a[ 563.408625] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\u000a[ 563.408627] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\u000a[ 563.904795] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 563.915796] PKRU: 55555554\u000a[ 563.915797] Call Trace:\u000a[ 563.915807] cache_set_flush+0xd4/0x6d0 [bcache]\u000a[ 563.915812] process_one_work+0x856/0x1620\u000a[ 564.001226] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 564.033563] ? find_held_lock+0x39/0x1d0\u000a[ 564.033567] ? drain_workqueue+0x380/0x380\u000a[ 564.033574] worker_thread+0x87/0xb80\u000a[ 564.062823] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 564.118042] ? __kthread_parkme+0xb6/0x180\u000a[ 564.118046] ? process_one_work+0x1620/0x1620\u000a[ 564.118048] kthread+0x326/0x3e0\u000a[ 564.118050] ? kthread_create_worker_on_cpu+0xc0/0xc0\u000a[ 564.167066] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 564.252441] ret_from_fork+0x3a/0x50\u000a[ 564.252447] Modules linked in: msr rpcrdma sunrpc rdma_ucm ib_iser ib_umad rdma_cm ib_ipoib i40iw configfs iw_cm ib_cm libiscsi scsi_transport_iscsi mlx4_ib ib_uverbs mlx4_en ib_core nls_iso8859_1 nls_cp437 vfat fat intel_rapl skx_edac x86_pkg_temp_thermal coretemp iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ses raid0 aesni_intel cdc_ether enclosure usbnet ipmi_ssif joydev aes_x86_64 i40e scsi_transport_sas mii bcache md_mod crypto_simd mei_me ioatdma crc64 ptp cryptd pcspkr i2c_i801 mlx4_core glue_helper pps_core mei lpc_ich dca wmi ipmi_si ipmi_devintf nd_pmem dax_pmem nd_btt ipmi_msghandler device_dax pcc_cpufreq button hid_generic usbhid mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect xhci_pci sysimgblt fb_sys_fops xhci_hcd ttm megaraid_sas drm usbcore nfit libnvdimm sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs\u000a[ 564.299390] bcache: bch_count_io_errors() nvme0n1: IO error on writing btree.\u000a[ 564.348360] CR2: 000000000000001c\u000a[ 564.348362] ---[ end trace b7f0e5cc7b2103b0 ]---\u000a\u000aTherefore, it is not enough to only check whether c->gc_thread is NULL,\u000awe should use IS_ERR_OR_NULL() to check both NULL pointer and error\u000avalue.\u000a\u000aThis patch changes the above buggy code piece in this way,\u000a if (!IS_ERR_OR_NULL(c->gc_thread))\u000a kthread_stop(c->gc_thread);\u000a\u000aSigned-off-by: Coly Li \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "2d1169fe13ace760454eac013f2adf0c420d5e23", "msg" : "bcache: check c->gc_thread by IS_ERR_OR_NULL in cache_set_flush()", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/super.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/super.c", "drivers/md/bcache/writeback.c" ], "commitId" : "5f5eb1716a27d75b5b8fc58854f31c60f559a0ca", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: fix potential deadlock in cached_def_free()\u000a\u000a[ Upstream commit 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e ]\u000a\u000aWhen enable lockdep and reboot system with a writeback mode bcache\u000adevice, the following potential deadlock warning is reported by lockdep\u000aengine.\u000a\u000a[ 101.536569][ T401] kworker/2:2/401 is trying to acquire lock:\u000a[ 101.538575][ T401] 00000000bbf6e6c7 ((wq_completion)bcache_writeback_wq){+.+.}, at: flush_workqueue+0x87/0x4c0\u000a[ 101.542054][ T401]\u000a[ 101.542054][ T401] but task is already holding lock:\u000a[ 101.544587][ T401] 00000000f5f305b3 ((work_completion)(&cl->work)#2){+.+.}, at: process_one_work+0x21e/0x640\u000a[ 101.548386][ T401]\u000a[ 101.548386][ T401] which lock already depends on the new lock.\u000a[ 101.548386][ T401]\u000a[ 101.551874][ T401]\u000a[ 101.551874][ T401] the existing dependency chain (in reverse order) is:\u000a[ 101.555000][ T401]\u000a[ 101.555000][ T401] -> #1 ((work_completion)(&cl->work)#2){+.+.}:\u000a[ 101.557860][ T401] process_one_work+0x277/0x640\u000a[ 101.559661][ T401] worker_thread+0x39/0x3f0\u000a[ 101.561340][ T401] kthread+0x125/0x140\u000a[ 101.562963][ T401] ret_from_fork+0x3a/0x50\u000a[ 101.564718][ T401]\u000a[ 101.564718][ T401] -> #0 ((wq_completion)bcache_writeback_wq){+.+.}:\u000a[ 101.567701][ T401] lock_acquire+0xb4/0x1c0\u000a[ 101.569651][ T401] flush_workqueue+0xae/0x4c0\u000a[ 101.571494][ T401] drain_workqueue+0xa9/0x180\u000a[ 101.573234][ T401] destroy_workqueue+0x17/0x250\u000a[ 101.575109][ T401] cached_dev_free+0x44/0x120 [bcache]\u000a[ 101.577304][ T401] process_one_work+0x2a4/0x640\u000a[ 101.579357][ T401] worker_thread+0x39/0x3f0\u000a[ 101.581055][ T401] kthread+0x125/0x140\u000a[ 101.582709][ T401] ret_from_fork+0x3a/0x50\u000a[ 101.584592][ T401]\u000a[ 101.584592][ T401] other info that might help us debug this:\u000a[ 101.584592][ T401]\u000a[ 101.588355][ T401] Possible unsafe locking scenario:\u000a[ 101.588355][ T401]\u000a[ 101.590974][ T401] CPU0 CPU1\u000a[ 101.592889][ T401] ---- ----\u000a[ 101.594743][ T401] lock((work_completion)(&cl->work)#2);\u000a[ 101.596785][ T401] lock((wq_completion)bcache_writeback_wq);\u000a[ 101.600072][ T401] lock((work_completion)(&cl->work)#2);\u000a[ 101.602971][ T401] lock((wq_completion)bcache_writeback_wq);\u000a[ 101.605255][ T401]\u000a[ 101.605255][ T401] *** DEADLOCK ***\u000a[ 101.605255][ T401]\u000a[ 101.608310][ T401] 2 locks held by kworker/2:2/401:\u000a[ 101.610208][ T401] #0: 00000000cf2c7d17 ((wq_completion)events){+.+.}, at: process_one_work+0x21e/0x640\u000a[ 101.613709][ T401] #1: 00000000f5f305b3 ((work_completion)(&cl->work)#2){+.+.}, at: process_one_work+0x21e/0x640\u000a[ 101.617480][ T401]\u000a[ 101.617480][ T401] stack backtrace:\u000a[ 101.619539][ T401] CPU: 2 PID: 401 Comm: kworker/2:2 Tainted: G W 5.2.0-rc4-lp151.20-default+ #1\u000a[ 101.623225][ T401] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/13/2018\u000a[ 101.627210][ T401] Workqueue: events cached_dev_free [bcache]\u000a[ 101.629239][ T401] Call Trace:\u000a[ 101.630360][ T401] dump_stack+0x85/0xcb\u000a[ 101.631777][ T401] print_circular_bug+0x19a/0x1f0\u000a[ 101.633485][ T401] __lock_acquire+0x16cd/0x1850\u000a[ 101.635184][ T401] ? __lock_acquire+0x6a8/0x1850\u000a[ 101.636863][ T401] ? lock_acquire+0xb4/0x1c0\u000a[ 101.638421][ T401] ? find_held_lock+0x34/0xa0\u000a[ 101.640015][ T401] lock_acquire+0xb4/0x1c0\u000a[ 101.641513][ T401] ? flush_workqueue+0x87/0x4c0\u000a[ 101.643248][ T401] flush_workqueue+0xae/0x4c0\u000a[ 101.644832][ T401] ? flush_workqueue+0x87/0x4c0\u000a[ 101.646476][ T401] ? drain_workqueue+0xa9/0x180\u000a[ 101.648303][ T401] drain_workqueue+0xa9/0x180\u000a[ 101.649867][ T401] destroy_workqueue+0x17/0x250\u000a[ 101.651503][ T401] cached_dev_free+0x44/0x120 [bcache]\u000a[ 101.653328][ T401] process_one_work+0x2a4/0x640\u000a[ 101.655029][ T401] worker_thread+0x39/0x3f0\u000a[ 101.656693][ T401] ? process_one_work+0x640/0x640\u000a[ 101.658501][ T401] kthread+0x125/0x140\u000a[ 101.660012][ T401] ? kthread_create_worker_on_cpu+0x70/0x70\u000a[ 101.661985][ T401] ret_from_fork+0x3a/0x50\u000a[ 101.691318][ T401] bcache: bcache_device_free() bcache0 stopped\u000a\u000aHere is how the above potential deadlock may happen in reboot/shutdown\u000acode path,\u000a1) bcache_reboot() is called firstly in the reboot/shutdown code path,\u000a then in bcache_reboot(), bcache_device_stop() is called.\u000a2) bcache_device_stop() sets BCACHE_DEV_CLOSING on d->falgs, then call\u000a closure_queue(&d->cl) to invoke cached_dev_flush(). And in turn\u000a cached_dev_flush() calls cached_dev_free() via closure_at()\u000a3) In cached_dev_free(), after stopped writebach kthread\u000a dc->writeback_thread, the kwork dc->writeback_write_wq is stopping by\u000a destroy_workqueue().\u000a4) Inside destroy_workqueue(), drain_workqueue() is called. Inside\u000a drain_workqueue(), flush_workqueue() is called. Then wq->lockdep_map\u000a is acquired by lock_map_acquire() in flush_workqueue(). After the\u000a lock acquired the rest part of flush_workqueue() just wait for the\u000a workqueue to complete.\u000a5) Now we look back at writeback thread routine bch_writeback_thread(),\u000a in the main while-loop, write_dirty() is called via continue_at() in\u000a read_dirty_submit(), which is called via continue_at() in while-loop\u000a level called function read_dirty(). Inside write_dirty() it may be\u000a re-called on workqueeu dc->writeback_write_wq via continue_at().\u000a It means when the writeback kthread is stopped in cached_dev_free()\u000a there might be still one kworker queued on dc->writeback_write_wq\u000a to execute write_dirty() again.\u000a6) Now this kworker is scheduled on dc->writeback_write_wq to run by\u000a process_one_work() (which is called by worker_thread()). Before\u000a calling the kwork routine, wq->lockdep_map is acquired.\u000a7) But wq->lockdep_map is acquired already in step 4), so a A-A lock\u000a (lockdep terminology) scenario happens.\u000a\u000aIndeed on multiple cores syatem, the above deadlock is very rare to\u000ahappen, just as the code comments in process_one_work() says,\u000a2263 * AFAICT there is no possible deadlock scenario between the\u000a2264 * flush_work() and complete() primitives (except for\u000a\u0009 single-threaded\u000a2265 * workqueues), so hiding them isn't a problem.\u000a\u000aBut it is still good to fix such lockdep warning, even no one running\u000abcache on single core system.\u000a\u000aThe fix is simple. This patch solves the above potential deadlock by,\u000a- Do not destroy workqueue dc->writeback_write_wq in cached_dev_free().\u000a- Flush and destroy dc->writeback_write_wq in writebach kthread routine\u000a bch_writeback_thread(), where after quit the thread main while-loop\u000a and before cached_dev_put() is called.\u000a\u000aBy this fix, dc->writeback_write_wq will be stopped and destroy before\u000athe writeback kthread stopped, so the chance for a A-A locking on\u000awq->lockdep_map is disappeared, such A-A deadlock won't happen\u000aany more.\u000a\u000aSigned-off-by: Coly Li \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "5f5eb1716a27d75b5b8fc58854f31c60f559a0ca", "msg" : "bcache: fix potential deadlock in cached_def_free()", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/super.c" }, { "editType" : "edit", "file" : "drivers/md/bcache/writeback.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c" ], "commitId" : "a83680691e3e7c97d11cdfe342b20e227276c4ce", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: fix a -Wformat-nonliteral compile warning\u000a\u000a[ Upstream commit 18d219b783da61a6cc77581f55fc4af2fa16bc36 ]\u000a\u000aWhen setting -Wformat=2, there is a compiler warning like this:\u000a\u000ahclge_main.c:xxx:x: warning: format not a string literal and no\u000aformat arguments [-Wformat-nonliteral]\u000astrs[i].desc);\u000a^~~~\u000a\u000aThis patch adds missing format parameter \"%s\" to snprintf() to\u000afix it.\u000a\u000aFixes: 46a3df9f9718 (\"Add HNS3 Acceleration Engine & Compatibility Layer Support\")\u000aSigned-off-by: Yonglong Liu \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "a83680691e3e7c97d11cdfe342b20e227276c4ce", "msg" : "net: hns3: fix a -Wformat-nonliteral compile warning", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c" ], "commitId" : "56591adf10e9c2d121541b7ebc0452462896c812", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: add some error checking in hclge_tm module\u000a\u000a[ Upstream commit 04f25edb48c441fc278ecc154c270f16966cbb90 ]\u000a\u000aWhen hdev->tx_sch_mode is HCLGE_FLAG_VNET_BASE_SCH_MODE, the\u000ahclge_tm_schd_mode_vnet_base_cfg calls hclge_tm_pri_schd_mode_cfg\u000awith vport->vport_id as pri_id, which is used as index for\u000ahdev->tm_info.tc_info, it will cause out of bound access issue\u000aif vport_id is equal to or larger than HNAE3_MAX_TC.\u000a\u000aAlso hardware only support maximum speed of HCLGE_ETHER_MAX_RATE.\u000a\u000aSo this patch adds two checks for above cases.\u000a\u000aFixes: 848440544b41 (\"net: hns3: Add support of TX Scheduler & Shaper to HNS3 driver\")\u000aSigned-off-by: Yunsheng Lin \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "56591adf10e9c2d121541b7ebc0452462896c812", "msg" : "net: hns3: add some error checking in hclge_tm module", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/qmi.c" ], "commitId" : "60dd7a80867ad7c8850fc37201cee91de69a19cf", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: Fix memory leak in qmi\u000a\u000a[ Upstream commit c709df58832c5f575f0255bea4b09ad477fc62ea ]\u000a\u000aCurrently the memory allocated for qmi handle is\u000anot being freed during de-init which leads to memory leak.\u000a\u000aFree the allocated qmi memory in qmi deinit\u000ato avoid memory leak.\u000a\u000aTested HW: WCN3990\u000aTested FW: WLAN.HL.3.1-01040-QCAHLSWMTPLZ-1\u000a\u000aFixes: fda6fee0001e (\"ath10k: add QMI message handshake for wcn3990 client\")\u000aSigned-off-by: Dundi Raviteja \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "60dd7a80867ad7c8850fc37201cee91de69a19cf", "msg" : "ath10k: Fix memory leak in qmi", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/qmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ath/ath10k/sdio.c" ], "commitId" : "d77aa90484840f2c04df3156a1d86f1c8de9a2ad", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ath10k: destroy sdio workqueue while remove sdio module\u000a\u000a[ Upstream commit 3ed39f8e747a7aafeec07bb244f2c3a1bdca5730 ]\u000a\u000aThe workqueue need to flush and destory while remove sdio module,\u000aotherwise it will have thread which is not destory after remove\u000asdio modules.\u000a\u000aTested with QCA6174 SDIO with firmware\u000aWLAN.RMH.4.4.1-00007-QCARMSWP-1.\u000a\u000aSigned-off-by: Wen Gong \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "d77aa90484840f2c04df3156a1d86f1c8de9a2ad", "msg" : "ath10k: destroy sdio workqueue while remove sdio module", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ath/ath10k/sdio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/marvell/mvpp2/mvpp2_prs.c" ], "commitId" : "aa6a8b84220c8225b2b7883be803ecfbf3af2e77", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: mvpp2: prs: Don't override the sign bit in SRAM parser shift\u000a\u000a[ Upstream commit 8ec3ede559956f8ad58db7b57d25ac724bab69e9 ]\u000a\u000aThe Header Parser allows identifying various fields in the packet\u000aheaders, used for various kind of filtering and classification\u000asteps.\u000a\u000aThis is a re-entrant process, where the offset in the packet header\u000adepends on the previous lookup results. This offset is represented in\u000athe SRAM results of the TCAM, as a shift to be operated.\u000a\u000aThis shift can be negative in some cases, such as in IPv6 parsing.\u000a\u000aThis commit prevents overriding the sign bit when setting the shift\u000avalue, which could cause instabilities when parsing IPv6 flows.\u000a\u000aFixes: 3f518509dedc (\"ethernet: Add new driver for Marvell Armada 375 network unit\")\u000aSuggested-by: Alan Winkowski \u000aSigned-off-by: Maxime Chevallier \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "aa6a8b84220c8225b2b7883be803ecfbf3af2e77", "msg" : "net: mvpp2: prs: Don't override the sign bit in SRAM parser shift", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/marvell/mvpp2/mvpp2_prs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/igb/igb_main.c" ], "commitId" : "d7924e6fc36f2fe4b0d47f20c2699ff538f1f696", "timestamp" : 1564125166000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "igb: clear out skb->tstamp after reading the txtime\u000a\u000a[ Upstream commit 1e08511d5d01884a3c9070afd52a47799312074a ]\u000a\u000aIf a packet which is utilizing the launchtime feature (via SO_TXTIME socket\u000aoption) also requests the hardware transmit timestamp, the hardware\u000atimestamp is not delivered to the userspace. This is because the value in\u000askb->tstamp is mistaken as the software timestamp.\u000a\u000aApplications, like ptp4l, request a hardware timestamp by setting the\u000aSOF_TIMESTAMPING_TX_HARDWARE socket option. Whenever a new timestamp is\u000adetected by the driver (this work is done in igb_ptp_tx_work() which calls\u000aigb_ptp_tx_hwtstamps() in igb_ptp.c[1]), it will queue the timestamp in the\u000aERR_QUEUE for the userspace to read. When the userspace is ready, it will\u000aissue a recvmsg() call to collect this timestamp. The problem is in this\u000arecvmsg() call. If the skb->tstamp is not cleared out, it will be\u000ainterpreted as a software timestamp and the hardware tx timestamp will not\u000abe successfully sent to the userspace. Look at skb_is_swtx_tstamp() and the\u000acallee function __sock_recv_timestamp() in net/socket.c for more details.\u000a\u000aSigned-off-by: Vedang Patel \u000aTested-by: Aaron Brown \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:46 +0200", "id" : "d7924e6fc36f2fe4b0d47f20c2699ff538f1f696", "msg" : "igb: clear out skb->tstamp after reading the txtime", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/igb/igb_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mdio.c", "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c" ], "commitId" : "724dffdf48228adaad80226d2c8721f72324e741", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: add Asym Pause support to fix autoneg problem\u000a\u000a[ Upstream commit bc3781edcea017aa1a29abd953b776cdba298ce2 ]\u000a\u000aLocal device and link partner config auto-negotiation on both,\u000alocal device config pause frame use as: rx on/tx off,\u000alink partner config pause frame use as: rx off/tx on.\u000a\u000aWe except the result is:\u000aLocal device:\u000aAutonegotiate: on\u000aRX: on\u000aTX: off\u000aRX negotiated: on\u000aTX negotiated: off\u000a\u000aLink partner:\u000aAutonegotiate: on\u000aRX: off\u000aTX: on\u000aRX negotiated: off\u000aTX negotiated: on\u000a\u000aBut actually, the result of Local device and link partner is both:\u000aAutonegotiate: on\u000aRX: off\u000aTX: off\u000aRX negotiated: off\u000aTX negotiated: off\u000a\u000aThe root cause is that the supported flag is has only Pause,\u000areference to the function genphy_config_advert():\u000astatic int genphy_config_advert(struct phy_device *phydev)\u000a{\u000a\u0009...\u000a\u0009linkmode_and(phydev->advertising, phydev->advertising,\u000a\u0009\u0009 phydev->supported);\u000a\u0009...\u000a}\u000aThe pause frame use of link partner is rx off/tx on, so its\u000aadvertising only set the bit Asym_Pause, and the supported is\u000aonly set the bit Pause, so the result of linkmode_and(), is\u000arx off/tx off.\u000a\u000aThis patch adds Asym_Pause to the supported flag to fix it.\u000a\u000aSigned-off-by: Yonglong Liu \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "724dffdf48228adaad80226d2c8721f72324e741", "msg" : "net: hns3: add Asym Pause support to fix autoneg problem", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c" }, { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mdio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c" ], "commitId" : "f2c23ab20f6e3350bcb24979a310435a0458b65e", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ixgbe: Avoid NULL pointer dereference with VF on non-IPsec hw\u000a\u000a[ Upstream commit 92924064106e410cdc015f1dbfc0499309f9f5b1 ]\u000a\u000aAn ipsec structure will not be allocated if the hardware does not support\u000aoffload. Fixes the following Oops:\u000a\u000a[ 191.045452] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\u000a[ 191.054232] Mem abort info:\u000a[ 191.057014] ESR = 0x96000004\u000a[ 191.060057] Exception class = DABT (current EL), IL = 32 bits\u000a[ 191.065963] SET = 0, FnV = 0\u000a[ 191.069004] EA = 0, S1PTW = 0\u000a[ 191.072132] Data abort info:\u000a[ 191.074999] ISV = 0, ISS = 0x00000004\u000a[ 191.078822] CM = 0, WnR = 0\u000a[ 191.081780] user pgtable: 4k pages, 48-bit VAs, pgdp = 0000000043d9e467\u000a[ 191.088382] [0000000000000000] pgd=0000000000000000\u000a[ 191.093252] Internal error: Oops: 96000004 [#1] SMP\u000a[ 191.098119] Modules linked in: vhost_net vhost tap vfio_pci vfio_virqfd vfio_iommu_type1 vfio xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter devlink ebtables ip6table_filter ip6_tables iptable_filter bpfilter ipmi_ssif nls_iso8859_1 input_leds joydev ipmi_si hns_roce_hw_v2 ipmi_devintf hns_roce ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 ses enclosure btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear ixgbevf hibmc_drm ttm\u000a[ 191.168607] drm_kms_helper aes_ce_blk aes_ce_cipher syscopyarea crct10dif_ce sysfillrect ghash_ce qla2xxx sysimgblt sha2_ce sha256_arm64 hisi_sas_v3_hw fb_sys_fops sha1_ce uas nvme_fc mpt3sas ixgbe drm hisi_sas_main nvme_fabrics usb_storage hclge scsi_transport_fc ahci libsas hnae3 raid_class libahci xfrm_algo scsi_transport_sas mdio aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64\u000a[ 191.202952] CPU: 94 PID: 0 Comm: swapper/94 Not tainted 4.19.0-rc1+ #11\u000a[ 191.209553] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019\u000a[ 191.218064] pstate: 20400089 (nzCv daIf +PAN -UAO)\u000a[ 191.222873] pc : ixgbe_ipsec_vf_clear+0x60/0xd0 [ixgbe]\u000a[ 191.228093] lr : ixgbe_msg_task+0x2d0/0x1088 [ixgbe]\u000a[ 191.233044] sp : ffff000009b3bcd0\u000a[ 191.236346] x29: ffff000009b3bcd0 x28: 0000000000000000\u000a[ 191.241647] x27: ffff000009628000 x26: 0000000000000000\u000a[ 191.246946] x25: ffff803f652d7600 x24: 0000000000000004\u000a[ 191.252246] x23: ffff803f6a718900 x22: 0000000000000000\u000a[ 191.257546] x21: 0000000000000000 x20: 0000000000000000\u000a[ 191.262845] x19: 0000000000000000 x18: 0000000000000000\u000a[ 191.268144] x17: 0000000000000000 x16: 0000000000000000\u000a[ 191.273443] x15: 0000000000000000 x14: 0000000100000026\u000a[ 191.278742] x13: 0000000100000025 x12: ffff8a5f7fbe0df0\u000a[ 191.284042] x11: 000000010000000b x10: 0000000000000040\u000a[ 191.289341] x9 : 0000000000001100 x8 : ffff803f6a824fd8\u000a[ 191.294640] x7 : ffff803f6a825098 x6 : 0000000000000001\u000a[ 191.299939] x5 : ffff000000f0ffc0 x4 : 0000000000000000\u000a[ 191.305238] x3 : ffff000028c00000 x2 : ffff803f652d7600\u000a[ 191.310538] x1 : 0000000000000000 x0 : ffff000000f205f0\u000a[ 191.315838] Process swapper/94 (pid: 0, stack limit = 0x00000000addfed5a)\u000a[ 191.322613] Call trace:\u000a[ 191.325055] ixgbe_ipsec_vf_clear+0x60/0xd0 [ixgbe]\u000a[ 191.329927] ixgbe_msg_task+0x2d0/0x1088 [ixgbe]\u000a[ 191.334536] ixgbe_msix_other+0x274/0x330 [ixgbe]\u000a[ 191.339233] __handle_irq_event_percpu+0x78/0x270\u000a[ 191.343924] handle_irq_event_percpu+0x40/0x98\u000a[ 191.348355] handle_irq_event+0x50/0xa8\u000a[ 191.352180] handle_fasteoi_irq+0xbc/0x148\u000a[ 191.356263] generic_handle_irq+0x34/0x50\u000a[ 191.360259] __handle_domain_irq+0x68/0xc0\u000a[ 191.364343] gic_handle_irq+0x84/0x180\u000a[ 191.368079] el1_irq+0xe8/0x180\u000a[ 191.371208] arch_cpu_idle+0x30/0x1a8\u000a[ 191.374860] do_idle+0x1dc/0x2a0\u000a[ 191.378077] cpu_startup_entry+0x2c/0x30\u000a[ 191.381988] secondary_start_kernel+0x150/0x1e0\u000a[ 191.386506] Code: 6b15003f 54000320 f1404a9f 54000060 (79400260)\u000a\u000aFixes: eda0333ac2930 (\"ixgbe: add VF IPsec management\")\u000aSigned-off-by: Dann Frazier \u000aAcked-by: Shannon Nelson \u000aTested-by: Andrew Bowers \u000aSigned-off-by: Jeff Kirsher \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "f2c23ab20f6e3350bcb24979a310435a0458b65e", "msg" : "ixgbe: Avoid NULL pointer dereference with VF on non-IPsec hw", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/mvm/tx.c" ], "commitId" : "c3674310c2a5dc929f4ea9e0580968582c1ca767", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: mvm: Drop large non sta frames\u000a\u000a[ Upstream commit ac70499ee97231a418dc1a4d6c9dc102e8f64631 ]\u000a\u000aIn some buggy scenarios we could possible attempt to transmit frames larger\u000athan maximum MSDU size. Since our devices don't know how to handle this,\u000ait may result in asserts, hangs etc.\u000aThis can happen, for example, when we receive a large multicast frame\u000aand try to transmit it back to the air in AP mode.\u000aSince in a legal scenario this should never happen, drop such frames and\u000awarn about it.\u000a\u000aSigned-off-by: Andrei Otcheretianski \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "c3674310c2a5dc929f4ea9e0580968582c1ca767", "msg" : "iwlwifi: mvm: Drop large non sta frames", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/tx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/include/uapi/linux/bpf.h", "include/uapi/linux/bpf.h" ], "commitId" : "91adaf0eb7bd981ca7c6d7b37823d69bd87bf3af", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf: fix uapi bpf_prog_info fields alignment\u000a\u000a[ Upstream commit 0472301a28f6cf53a6bc5783e48a2d0bbff4682f ]\u000a\u000aMerge commit 1c8c5a9d38f60 (\"Merge\u000agit://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next\") undid the\u000afix from commit 36f9814a494 (\"bpf: fix uapi hole for 32 bit compat\u000aapplications\") by taking the gpl_compatible 1-bit field definition from\u000acommit b85fab0e67b162 (\"bpf: Add gpl_compatible flag to struct\u000abpf_prog_info\") as is. That breaks architectures with 16-bit alignment\u000alike m68k. Add 31-bit pad after gpl_compatible to restore alignment of\u000afollowing fields.\u000a\u000aThanks to Dmitry V. Levin his analysis of this bug history.\u000a\u000aSigned-off-by: Baruch Siach \u000aAcked-by: Song Liu \u000aCc: Jiri Olsa \u000aCc: Daniel Borkmann \u000aCc: Geert Uytterhoeven \u000aCc: Linus Torvalds \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "91adaf0eb7bd981ca7c6d7b37823d69bd87bf3af", "msg" : "bpf: fix uapi bpf_prog_info fields alignment", "paths" : [ { "editType" : "edit", "file" : "tools/include/uapi/linux/bpf.h" }, { "editType" : "edit", "file" : "include/uapi/linux/bpf.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netfilter/utils.c", "net/netfilter/nf_nat_proto.c", "net/netfilter/nf_conntrack_proto_icmp.c" ], "commitId" : "7bc8dfa08807e0ab31fb870e4ed0d3355b7acdca", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "netfilter: Fix remainder of pseudo-header protocol 0\u000a\u000a[ Upstream commit 5d1549847c76b1ffcf8e388ef4d0f229bdd1d7e8 ]\u000a\u000aSince v5.1-rc1, some types of packets do not get unreachable reply with the\u000afollowing iptables setting. Fox example,\u000a\u000a$ iptables -A INPUT -p icmp --icmp-type 8 -j REJECT\u000a$ ping 127.0.0.1 -c 1\u000aPING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.\u000a— 127.0.0.1 ping statistics —\u000a1 packets transmitted, 0 received, 100% packet loss, time 0ms\u000a\u000aWe should have got the following reply from command line, but we did not.\u000aFrom 127.0.0.1 icmp_seq=1 Destination Port Unreachable\u000a\u000aYi Zhao reported it and narrowed it down to:\u000a7fc38225363d (\"netfilter: reject: skip csum verification for protocols that don't support it\"),\u000a\u000aThis is because nf_ip_checksum still expects pseudo-header protocol type 0 for\u000apackets that are of neither TCP or UDP, and thus ICMP packets are mistakenly\u000atreated as TCP/UDP.\u000a\u000aThis patch corrects the conditions in nf_ip_checksum and all other places that\u000astill call it with protocol 0.\u000a\u000aFixes: 7fc38225363d (\"netfilter: reject: skip csum verification for protocols that don't support it\")\u000aReported-by: Yi Zhao \u000aSigned-off-by: He Zhe \u000aSigned-off-by: Pablo Neira Ayuso \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "7bc8dfa08807e0ab31fb870e4ed0d3355b7acdca", "msg" : "netfilter: Fix remainder of pseudo-header protocol 0", "paths" : [ { "editType" : "edit", "file" : "net/netfilter/utils.c" }, { "editType" : "edit", "file" : "net/netfilter/nf_nat_proto.c" }, { "editType" : "edit", "file" : "net/netfilter/nf_conntrack_proto_icmp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/fw/dbg.c", "drivers/net/wireless/intel/iwlwifi/fw/dbg.h" ], "commitId" : "8d4c01b36e0ac45bf6a03443027d0752abef8339", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: dbg: fix debug monitor stop and restart delays\u000a\u000a[ Upstream commit fc838c775f35e272e5cc7ef43853f0b55babbe37 ]\u000a\u000aThe driver should delay only in recording stop flow between writing to\u000aDBGC_IN_SAMPLE register and DBGC_OUT_CTRL register. Any other delay is\u000anot needed.\u000a\u000aChange the following:\u000a1. Remove any unnecessary delays in the flow\u000a2. Increase the delay in the stop recording flow since 100 micro is\u000a not enough\u000a3. Use usleep_range instead of delay since the driver is allowed to\u000a sleep in this flow.\u000a\u000aSigned-off-by: Shahar S Matityahu \u000aFixes: 5cfe79c8d92a (\"iwlwifi: fw: stop and start debugging using host command\")\u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "8d4c01b36e0ac45bf6a03443027d0752abef8339", "msg" : "iwlwifi: dbg: fix debug monitor stop and restart delays", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/fw/dbg.h" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/fw/dbg.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/broadcom/bnxt/bnxt.c" ], "commitId" : "51a21893890373b6daad0a139a55ea642959db3d", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bnxt_en: Disable bus master during PCI shutdown and driver unload.\u000a\u000a[ Upstream commit c20dc142dd7b2884b8570eeab323bcd4a84294fa ]\u000a\u000aSome chips with older firmware can continue to perform DMA read from\u000acontext memory even after the memory has been freed. In the PCI shutdown\u000amethod, we need to call pci_disable_device() to shutdown DMA to prevent\u000athis DMA before we put the device into D3hot. DMA memory request in\u000aD3hot state will generate PCI fatal error. Similarly, in the driver\u000aremove method, the context memory should only be freed after DMA has\u000abeen shutdown for correctness.\u000a\u000aFixes: 98f04cf0f1fc (\"bnxt_en: Check context memory requirements from firmware.\")\u000aSigned-off-by: Michael Chan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "51a21893890373b6daad0a139a55ea642959db3d", "msg" : "bnxt_en: Disable bus master during PCI shutdown and driver unload.", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnxt/bnxt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/broadcom/bnxt/bnxt.c" ], "commitId" : "dcbc804c94d678cb8acd6c06dc8410a67cbc52d4", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bnxt_en: Fix statistics context reservation logic for RDMA driver.\u000a\u000a[ Upstream commit d77b1ad8e87dc5a6cd0d9158b097a4817946ca3b ]\u000a\u000aThe current logic assumes that the RDMA driver uses one statistics\u000acontext adjacent to the ones used by the network driver. This\u000aassumption is not true and the statistics context used by the\u000aRDMA driver is tied to its MSIX base vector. This wrong assumption\u000acan cause RDMA driver failure after changing ethtool rings on the\u000anetwork side. Fix the statistics reservation logic accordingly.\u000a\u000aFixes: 780baad44f0f (\"bnxt_en: Reserve 1 stat_ctx for RDMA driver.\")\u000aSigned-off-by: Michael Chan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "dcbc804c94d678cb8acd6c06dc8410a67cbc52d4", "msg" : "bnxt_en: Fix statistics context reservation logic for RDMA driver.", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnxt/bnxt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/hda/hdac_controller.c" ], "commitId" : "7a6030b1ad4f7b9a7c9f23d0b9ae952dd954633a", "timestamp" : 1564125167000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda: Fix a headphone detection issue when using SOF\u000a\u000a[ Upstream commit 7c2b3629d09ddec810dc4c1d3a6657c32def8f71 ]\u000a\u000aTo save power, the hda hdmi driver in ASoC invokes snd_hdac_ext_bus_link_put\u000ato disable CORB/RIRB buffers DMA if there is no user of bus and invokes\u000asnd_hdac_ext_bus_link_get to set up CORB/RIRB buffers when it is used.\u000aUnsolicited responses is disabled in snd_hdac_bus_stop_cmd_io called by\u000asnd_hdac_ext_bus_link_put , but it is not enabled in snd_hdac_bus_init_cmd_io\u000acalled by snd_hdac_ext_bus_link_get. So for put-get sequence, Unsolicited\u000aresponses is disabled and headphone can't be detected by hda codecs.\u000a\u000aNow unsolicited responses is only enabled in snd_hdac_bus_reset_link\u000awhich resets controller. The function is only called for setup of\u000acontroller. This patch enables Unsolicited responses after RIRB is\u000ainitialized in snd_hdac_bus_init_cmd_io which works together with\u000asnd_hdac_bus_reset_link to set up controller.\u000a\u000aTested legacy hda driver and SOF driver on intel whiskeylake.\u000a\u000aReviewed-by: Takashi Iwai \u000aSigned-off-by: Rander Wang \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:47 +0200", "id" : "7a6030b1ad4f7b9a7c9f23d0b9ae952dd954633a", "msg" : "ALSA: hda: Fix a headphone detection issue when using SOF", "paths" : [ { "editType" : "edit", "file" : "sound/hda/hdac_controller.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/stat-shadow.c" ], "commitId" : "6f800cb1d52f817e62ccaea7dedb5533b5b06a30", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf stat: Make metric event lookup more robust\u000a\u000a[ Upstream commit 145c407c808352acd625be793396fd4f33c794f8 ]\u000a\u000aAfter setting up metric groups through the event parser, the metricgroup\u000acode looks them up again in the event list.\u000a\u000aMake sure we only look up events that haven't been used by some other\u000ametric. The data structures currently cannot handle more than one metric\u000aper event. This avoids problems with multiple events partially\u000aoverlapping.\u000a\u000aSigned-off-by: Andi Kleen \u000aAcked-by: Jiri Olsa \u000aCc: Kan Liang \u000aLink: http://lkml.kernel.org/r/20190624193711.35241-2-andi@firstfloor.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "6f800cb1d52f817e62ccaea7dedb5533b5b06a30", "msg" : "perf stat: Make metric event lookup more robust", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/stat-shadow.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/stat-shadow.c" ], "commitId" : "beba77a8d1aa8b6e218cbb58554e031e77de4e3b", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf stat: Fix metrics with --no-merge\u000a\u000a[ Upstream commit e3a9427323a53ceee540276a74af7706f350d052 ]\u000a\u000aSince Fixes: 8c5421c016a4 (\"perf pmu: Display pmu name when printing\u000aunmerged events in stat\") using --no-merge adds the PMU name to the\u000aevsel name.\u000a\u000aThis breaks the metric value lookup because the parser doesn't know\u000aabout this.\u000a\u000aRemove the extra postfixes for the metric evaluation.\u000a\u000aSigned-off-by: Andi Kleen \u000aAcked-by: Jiri Olsa \u000aCc: Agustin Vega-Frias \u000aCc: Kan Liang \u000aFixes: 8c5421c016a4 (\"perf pmu: Display pmu name when printing unmerged events in stat\")\u000aLink: http://lkml.kernel.org/r/20190624193711.35241-5-andi@firstfloor.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "beba77a8d1aa8b6e218cbb58554e031e77de4e3b", "msg" : "perf stat: Fix metrics with --no-merge", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/stat-shadow.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/stat-display.c" ], "commitId" : "db8ce0dbe8fc5ccce78e346db56afbab02e2fbc9", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf stat: Don't merge events in the same PMU\u000a\u000a[ Upstream commit 6c5f4e5cb35b4694dc035d91092d23f596ecd06a ]\u000a\u000aEvent merging is mainly to collapse similar events in lots of different\u000aduplicated PMUs.\u000a\u000aIt can break metric displaying. It's possible for two metrics to have\u000athe same event, and when the two events happen in a row the second\u000awouldn't be displayed. This would also not show the second metric.\u000a\u000aTo avoid this don't merge events in the same PMU. This makes sense, if\u000awe have multiple events in the same PMU there is likely some reason for\u000ait (e.g. using multiple groups) and we better not merge them.\u000a\u000aWhile in theory it would be possible to construct metrics that have\u000aevents with the same name in different PMU no current metrics have this\u000aproblem.\u000a\u000aThis is the fix for perf stat -M UPI,IPC (needs also another bug fix to\u000acompletely work)\u000a\u000aSigned-off-by: Andi Kleen \u000aAcked-by: Jiri Olsa \u000aCc: Kan Liang \u000aFixes: 430daf2dc7af (\"perf stat: Collapse identically named events\")\u000aLink: http://lkml.kernel.org/r/20190624193711.35241-3-andi@firstfloor.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "db8ce0dbe8fc5ccce78e346db56afbab02e2fbc9", "msg" : "perf stat: Don't merge events in the same PMU", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/stat-display.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/util/metricgroup.c" ], "commitId" : "e128d8564667d2b46a8e1598b8f6cb26a8c45771", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf stat: Fix group lookup for metric group\u000a\u000a[ Upstream commit 2f87f33f4226523df9c9cc28f9874ea02fcc3d3f ]\u000a\u000aThe metric group code tries to find a group it added earlier in the\u000aevlist. Fix the lookup to handle groups with partially overlaps\u000acorrectly. When a sub string match fails and we reset the match, we have\u000ato compare the first element again.\u000a\u000aI also renamed the find_evsel function to find_evsel_group to make its\u000apurpose clearer.\u000a\u000aWith the earlier changes this fixes:\u000a\u000aBefore:\u000a\u000a % perf stat -M UPI,IPC sleep 1\u000a ...\u000a 1,032,922 uops_retired.retire_slots # 1.1 UPI\u000a 1,896,096 inst_retired.any\u000a 1,896,096 inst_retired.any\u000a 1,177,254 cpu_clk_unhalted.thread\u000a\u000aAfter:\u000a\u000a % perf stat -M UPI,IPC sleep 1\u000a ...\u000a 1,013,193 uops_retired.retire_slots # 1.1 UPI\u000a 932,033 inst_retired.any\u000a 932,033 inst_retired.any # 0.9 IPC\u000a 1,091,245 cpu_clk_unhalted.thread\u000a\u000aSigned-off-by: Andi Kleen \u000aAcked-by: Jiri Olsa \u000aCc: Kan Liang \u000aFixes: b18f3e365019 (\"perf stat: Support JSON metrics in perf stat\")\u000aLink: http://lkml.kernel.org/r/20190624193711.35241-4-andi@firstfloor.org\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "e128d8564667d2b46a8e1598b8f6cb26a8c45771", "msg" : "perf stat: Fix group lookup for metric group", "paths" : [ { "editType" : "edit", "file" : "tools/perf/util/metricgroup.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/vxlan.c" ], "commitId" : "5a439255b9e1bfe60264f26bc584ae7f0a0566a6", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "vxlan: do not destroy fdb if register_netdevice() is failed\u000a\u000a[ Upstream commit 7c31e54aeee517d1318dfc0bde9fa7de75893dc6 ]\u000a\u000a__vxlan_dev_create() destroys FDB using specific pointer which indicates\u000aa fdb when error occurs.\u000aBut that pointer should not be used when register_netdevice() fails because\u000aregister_netdevice() internally destroys fdb when error occurs.\u000a\u000aThis patch makes vxlan_fdb_create() to do not link fdb entry to vxlan dev\u000ainternally.\u000aInstead, a new function vxlan_fdb_insert() is added to link fdb to vxlan\u000adev.\u000a\u000avxlan_fdb_insert() is called after calling register_netdevice().\u000aThis routine can avoid situation that ->ndo_uninit() destroys fdb entry\u000ain error path of register_netdevice().\u000aHence, error path of __vxlan_dev_create() routine can have an opportunity\u000ato destroy default fdb entry by hand.\u000a\u000aTest command\u000a ip link add bonding_masters type vxlan id 0 group 239.1.1.1 \\\u000a\u0009 dev enp0s9 dstport 4789\u000a\u000aSplat looks like:\u000a[ 213.392816] kasan: GPF could be caused by NULL-ptr deref or user memory access\u000a[ 213.401257] general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI\u000a[ 213.402178] CPU: 0 PID: 1414 Comm: ip Not tainted 5.2.0-rc5+ #256\u000a[ 213.402178] RIP: 0010:vxlan_fdb_destroy+0x120/0x220 [vxlan]\u000a[ 213.402178] Code: df 48 8b 2b 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 06 01 00 00 4c 8b 63 08 48 b8 00 00 00 00 00 fc d\u000a[ 213.402178] RSP: 0018:ffff88810cb9f0a0 EFLAGS: 00010202\u000a[ 213.402178] RAX: dffffc0000000000 RBX: ffff888101d4a8c8 RCX: 0000000000000000\u000a[ 213.402178] RDX: 1bd5a00000000040 RSI: ffff888101d4a8c8 RDI: ffff888101d4a8d0\u000a[ 213.402178] RBP: 0000000000000000 R08: fffffbfff22b72d9 R09: 0000000000000000\u000a[ 213.402178] R10: 00000000ffffffef R11: 0000000000000000 R12: dead000000000200\u000a[ 213.402178] R13: ffff88810cb9f1f8 R14: ffff88810efccda0 R15: ffff88810efccda0\u000a[ 213.402178] FS: 00007f7f6621a0c0(0000) GS:ffff88811b000000(0000) knlGS:0000000000000000\u000a[ 213.402178] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 213.402178] CR2: 000055746f0807d0 CR3: 00000001123e0000 CR4: 00000000001006f0\u000a[ 213.402178] Call Trace:\u000a[ 213.402178] __vxlan_dev_create+0x3a9/0x7d0 [vxlan]\u000a[ 213.402178] ? vxlan_changelink+0x740/0x740 [vxlan]\u000a[ 213.402178] ? rcu_read_unlock+0x60/0x60 [vxlan]\u000a[ 213.402178] ? __kasan_kmalloc.constprop.3+0xa0/0xd0\u000a[ 213.402178] vxlan_newlink+0x8d/0xc0 [vxlan]\u000a[ 213.402178] ? __vxlan_dev_create+0x7d0/0x7d0 [vxlan]\u000a[ 213.554119] ? __netlink_ns_capable+0xc3/0xf0\u000a[ 213.554119] __rtnl_newlink+0xb75/0x1180\u000a[ 213.554119] ? rtnl_link_unregister+0x230/0x230\u000a[ ... ]\u000a\u000aFixes: 0241b836732f (\"vxlan: fix default fdb entry netlink notify ordering during netdev create\")\u000aSuggested-by: Roopa Prabhu \u000aSigned-off-by: Taehee Yoo \u000aAcked-by: Roopa Prabhu \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "5a439255b9e1bfe60264f26bc584ae7f0a0566a6", "msg" : "vxlan: do not destroy fdb if register_netdevice() is failed", "paths" : [ { "editType" : "edit", "file" : "drivers/net/vxlan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c", "drivers/net/ethernet/broadcom/bnx2x/bnx2x_ethtool.c", "drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c", "drivers/net/ethernet/broadcom/bnx2x/bnx2x_stats.h" ], "commitId" : "74d03f7e9017e6c0301817094f0437e6ff710ae5", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bnx2x: Prevent ptp_task to be rescheduled indefinitely\u000a\u000a[ Upstream commit 3c91f25c2f72ba6001775a5932857c1d2131c531 ]\u000a\u000aCurrently bnx2x ptp worker tries to read a register with timestamp\u000ainformation in case of TX packet timestamping and in case it fails,\u000athe routine reschedules itself indefinitely. This was reported as a\u000akworker always at 100% of CPU usage, which was narrowed down to be\u000abnx2x ptp_task.\u000a\u000aBy following the ioctl handler, we could narrow down the problem to\u000aan NTP tool (chrony) requesting HW timestamping from bnx2x NIC with\u000aRX filter zeroed; this isn't reproducible for example with ptp4l\u000a(from linuxptp) since this tool requests a supported RX filter.\u000aIt seems NIC FW timestamp mechanism cannot work well with\u000aRX_FILTER_NONE - driver's PTP filter init routine skips a register\u000awrite to the adapter if there's not a supported filter request.\u000a\u000aThis patch addresses the problem of bnx2x ptp thread's everlasting\u000areschedule by retrying the register read 10 times; between the read\u000aattempts the thread sleeps for an increasing amount of time starting\u000ain 1ms to give FW some time to perform the timestamping. If it still\u000afails after all retries, we bail out in order to prevent an unbound\u000aresource consumption from bnx2x.\u000a\u000aThe patch also adds an ethtool statistic for accounting the skipped\u000aTX timestamp packets and it reduces the priority of timestamping\u000aerror messages to prevent log flooding. The code was tested using\u000aboth linuxptp and chrony.\u000a\u000aReported-and-tested-by: Przemyslaw Hausman \u000aSuggested-by: Sudarsana Reddy Kalluru \u000aSigned-off-by: Guilherme G. Piccoli \u000aAcked-by: Sudarsana Reddy Kalluru \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "74d03f7e9017e6c0301817094f0437e6ff710ae5", "msg" : "bnx2x: Prevent ptp_task to be rescheduled indefinitely", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_stats.h" }, { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_ethtool.c" }, { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c" }, { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/usb/asix_devices.c" ], "commitId" : "b12cc046f0a275a3339f3dced1aeb37bf9f9557d", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: usb: asix: init MAC address buffers\u000a\u000a[ Upstream commit 78226f6eaac80bf30256a33a4926c194ceefdf36 ]\u000a\u000aThis is for fixing bug KMSAN: uninit-value in ax88772_bind\u000a\u000aTested by\u000ahttps://groups.google.com/d/msg/syzkaller-bugs/aFQurGotng4/eB_HlNhhCwAJ\u000a\u000aReported-by: syzbot+8a3fc6674bbc3978ed4e@syzkaller.appspotmail.com\u000a\u000asyzbot found the following crash on:\u000a\u000aHEAD commit: f75e4cfe kmsan: use kmsan_handle_urb() in urb.c\u000agit tree: kmsan\u000aconsole output: https://syzkaller.appspot.com/x/log.txt?x=136d720ea00000\u000akernel config:\u000ahttps://syzkaller.appspot.com/x/.config?x=602468164ccdc30a\u000adashboard link:\u000ahttps://syzkaller.appspot.com/bug?extid=8a3fc6674bbc3978ed4e\u000acompiler: clang version 9.0.0 (/home/glider/llvm/clang\u000a06d00afa61eef8f7f501ebdb4e8612ea43ec2d78)\u000asyz repro:\u000ahttps://syzkaller.appspot.com/x/repro.syz?x=12788316a00000\u000aC reproducer: https://syzkaller.appspot.com/x/repro.c?x=120359aaa00000\u000a\u000a==================================================================\u000aBUG: KMSAN: uninit-value in is_valid_ether_addr\u000ainclude/linux/etherdevice.h:200 [inline]\u000aBUG: KMSAN: uninit-value in asix_set_netdev_dev_addr\u000adrivers/net/usb/asix_devices.c:73 [inline]\u000aBUG: KMSAN: uninit-value in ax88772_bind+0x93d/0x11e0\u000adrivers/net/usb/asix_devices.c:724\u000aCPU: 0 PID: 3348 Comm: kworker/0:2 Not tainted 5.1.0+ #1\u000aHardware name: Google Google Compute Engine/Google Compute Engine, BIOS\u000aGoogle 01/01/2011\u000aWorkqueue: usb_hub_wq hub_event\u000aCall Trace:\u000a __dump_stack lib/dump_stack.c:77 [inline]\u000a dump_stack+0x191/0x1f0 lib/dump_stack.c:113\u000a kmsan_report+0x130/0x2a0 mm/kmsan/kmsan.c:622\u000a __msan_warning+0x75/0xe0 mm/kmsan/kmsan_instr.c:310\u000a is_valid_ether_addr include/linux/etherdevice.h:200 [inline]\u000a asix_set_netdev_dev_addr drivers/net/usb/asix_devices.c:73 [inline]\u000a ax88772_bind+0x93d/0x11e0 drivers/net/usb/asix_devices.c:724\u000a usbnet_probe+0x10f5/0x3940 drivers/net/usb/usbnet.c:1728\u000a usb_probe_interface+0xd66/0x1320 drivers/usb/core/driver.c:361\u000a really_probe+0xdae/0x1d80 drivers/base/dd.c:513\u000a driver_probe_device+0x1b3/0x4f0 drivers/base/dd.c:671\u000a __device_attach_driver+0x5b8/0x790 drivers/base/dd.c:778\u000a bus_for_each_drv+0x28e/0x3b0 drivers/base/bus.c:454\u000a __device_attach+0x454/0x730 drivers/base/dd.c:844\u000a device_initial_probe+0x4a/0x60 drivers/base/dd.c:891\u000a bus_probe_device+0x137/0x390 drivers/base/bus.c:514\u000a device_add+0x288d/0x30e0 drivers/base/core.c:2106\u000a usb_set_configuration+0x30dc/0x3750 drivers/usb/core/message.c:2027\u000a generic_probe+0xe7/0x280 drivers/usb/core/generic.c:210\u000a usb_probe_device+0x14c/0x200 drivers/usb/core/driver.c:266\u000a really_probe+0xdae/0x1d80 drivers/base/dd.c:513\u000a driver_probe_device+0x1b3/0x4f0 drivers/base/dd.c:671\u000a __device_attach_driver+0x5b8/0x790 drivers/base/dd.c:778\u000a bus_for_each_drv+0x28e/0x3b0 drivers/base/bus.c:454\u000a __device_attach+0x454/0x730 drivers/base/dd.c:844\u000a device_initial_probe+0x4a/0x60 drivers/base/dd.c:891\u000a bus_probe_device+0x137/0x390 drivers/base/bus.c:514\u000a device_add+0x288d/0x30e0 drivers/base/core.c:2106\u000a usb_new_device+0x23e5/0x2ff0 drivers/usb/core/hub.c:2534\u000a hub_port_connect drivers/usb/core/hub.c:5089 [inline]\u000a hub_port_connect_change drivers/usb/core/hub.c:5204 [inline]\u000a port_event drivers/usb/core/hub.c:5350 [inline]\u000a hub_event+0x48d1/0x7290 drivers/usb/core/hub.c:5432\u000a process_one_work+0x1572/0x1f00 kernel/workqueue.c:2269\u000a process_scheduled_works kernel/workqueue.c:2331 [inline]\u000a worker_thread+0x189c/0x2460 kernel/workqueue.c:2417\u000a kthread+0x4b5/0x4f0 kernel/kthread.c:254\u000a ret_from_fork+0x35/0x40 arch/x86/entry/entry_64.S:355\u000a\u000aSigned-off-by: Phong Tran \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "b12cc046f0a275a3339f3dced1aeb37bf9f9557d", "msg" : "net: usb: asix: init MAC address buffers", "paths" : [ { "editType" : "edit", "file" : "drivers/net/usb/asix_devices.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/trace/events/rxrpc.h" ], "commitId" : "8cf52280813678f0359744f14376eb7518ad3a6c", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rxrpc: Fix oops in tracepoint\u000a\u000a[ Upstream commit 99f0eae653b2db64917d0b58099eb51e300b311d ]\u000a\u000aIf the rxrpc_eproto tracepoint is enabled, an oops will be cause by the\u000atrace line that rxrpc_extract_header() tries to emit when a protocol error\u000aoccurs (typically because the packet is short) because the call argument is\u000aNULL.\u000a\u000aFix this by using ?: to assume 0 as the debug_id if call is NULL.\u000a\u000aThis can then be induced by:\u000a\u000a\u0009echo -e '\\0\\0\\0\\0\\0\\0\\0\\0' | ncat -4u --send-only 20001\u000a\u000awhere addr has the following program running on it:\u000a\u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009int main(void)\u000a\u0009{\u000a\u0009\u0009struct sockaddr_rxrpc srx;\u000a\u0009\u0009int fd;\u000a\u0009\u0009memset(&srx, 0, sizeof(srx));\u000a\u0009\u0009srx.srx_family\u0009\u0009\u0009= AF_RXRPC;\u000a\u0009\u0009srx.srx_service\u0009\u0009\u0009= 0;\u000a\u0009\u0009srx.transport_type\u0009\u0009= AF_INET;\u000a\u0009\u0009srx.transport_len\u0009\u0009= sizeof(srx.transport.sin);\u000a\u0009\u0009srx.transport.sin.sin_family\u0009= AF_INET;\u000a\u0009\u0009srx.transport.sin.sin_port\u0009= htons(0x4e21);\u000a\u0009\u0009fd = socket(AF_RXRPC, SOCK_DGRAM, AF_INET6);\u000a\u0009\u0009bind(fd, (struct sockaddr *)&srx, sizeof(srx));\u000a\u0009\u0009sleep(20);\u000a\u0009\u0009return 0;\u000a\u0009}\u000a\u000aIt results in the following oops.\u000a\u000a\u0009BUG: kernel NULL pointer dereference, address: 0000000000000340\u000a\u0009#PF: supervisor read access in kernel mode\u000a\u0009#PF: error_code(0x0000) - not-present page\u000a\u0009...\u000a\u0009RIP: 0010:trace_event_raw_event_rxrpc_rx_eproto+0x47/0xac\u000a\u0009...\u000a\u0009Call Trace:\u000a\u0009 \u000a\u0009 rxrpc_extract_header+0x86/0x171\u000a\u0009 ? rcu_read_lock_sched_held+0x5d/0x63\u000a\u0009 ? rxrpc_new_skb+0xd4/0x109\u000a\u0009 rxrpc_input_packet+0xef/0x14fc\u000a\u0009 ? rxrpc_input_data+0x986/0x986\u000a\u0009 udp_queue_rcv_one_skb+0xbf/0x3d0\u000a\u0009 udp_unicast_rcv_skb.isra.8+0x64/0x71\u000a\u0009 ip_protocol_deliver_rcu+0xe4/0x1b4\u000a\u0009 ip_local_deliver+0xf0/0x154\u000a\u0009 __netif_receive_skb_one_core+0x50/0x6c\u000a\u0009 netif_receive_skb_internal+0x26b/0x2e9\u000a\u0009 napi_gro_receive+0xf8/0x1da\u000a\u0009 rtl8169_poll+0x303/0x4c4\u000a\u0009 net_rx_action+0x10e/0x333\u000a\u0009 __do_softirq+0x1a5/0x38f\u000a\u0009 irq_exit+0x54/0xc4\u000a\u0009 do_IRQ+0xda/0xf8\u000a\u0009 common_interrupt+0xf/0xf\u000a\u0009 \u000a\u0009 ...\u000a\u0009 ? cpuidle_enter_state+0x23c/0x34d\u000a\u0009 cpuidle_enter+0x2a/0x36\u000a\u0009 do_idle+0x163/0x1ea\u000a\u0009 cpu_startup_entry+0x1d/0x1f\u000a\u0009 start_secondary+0x157/0x172\u000a\u0009 secondary_startup_64+0xa4/0xb0\u000a\u000aFixes: a25e21f0bcd2 (\"rxrpc, afs: Use debug_ids rather than pointers in traces\")\u000aSigned-off-by: David Howells \u000aReviewed-by: Marc Dionne \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "8cf52280813678f0359744f14376eb7518ad3a6c", "msg" : "rxrpc: Fix oops in tracepoint", "paths" : [ { "editType" : "edit", "file" : "include/trace/events/rxrpc.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/lib/bpf/xsk.c" ], "commitId" : "925df79853ded6efc59f942927dd934ad9fb4129", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "libbpf: fix GCC8 warning for strncpy\u000a\u000a[ Upstream commit cdfc7f888c2a355b01308e97c6df108f1c2b64e8 ]\u000a\u000aGCC8 started emitting warning about using strncpy with number of bytes\u000aexactly equal destination size, which is generally unsafe, as can lead\u000ato non-zero terminated string being copied. Use IFNAMSIZ - 1 as number\u000aof bytes to ensure name is always zero-terminated.\u000a\u000aSigned-off-by: Andrii Nakryiko \u000aCc: Magnus Karlsson \u000aAcked-by: Yonghong Song \u000aAcked-by: Magnus Karlsson \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "925df79853ded6efc59f942927dd934ad9fb4129", "msg" : "libbpf: fix GCC8 warning for strncpy", "paths" : [ { "editType" : "edit", "file" : "tools/lib/bpf/xsk.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/lib/bpf/libbpf.c" ], "commitId" : "b8bf2e82c0b913887530a96c63dc66a3647141a4", "timestamp" : 1564125168000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bpf, libbpf, smatch: Fix potential NULL pointer dereference\u000a\u000a[ Upstream commit 33bae185f74d49a0d7b1bfaafb8e959efce0f243 ]\u000a\u000aBased on the following report from Smatch, fix the potential NULL\u000apointer dereference check:\u000a\u000a tools/lib/bpf/libbpf.c:3493\u000a bpf_prog_load_xattr() warn: variable dereferenced before check 'attr'\u000a (see line 3483)\u000a\u000a 3479 int bpf_prog_load_xattr(const struct bpf_prog_load_attr *attr,\u000a 3480 struct bpf_object **pobj, int *prog_fd)\u000a 3481 {\u000a 3482 struct bpf_object_open_attr open_attr = {\u000a 3483 .file = attr->file,\u000a 3484 .prog_type = attr->prog_type,\u000a ^^^^^^\u000a 3485 };\u000a\u000aAt the head of function, it directly access 'attr' without checking\u000aif it's NULL pointer. This patch moves the values assignment after\u000avalidating 'attr' and 'attr->file'.\u000a\u000aSigned-off-by: Leo Yan \u000aAcked-by: Yonghong Song \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:48 +0200", "id" : "b8bf2e82c0b913887530a96c63dc66a3647141a4", "msg" : "bpf, libbpf, smatch: Fix potential NULL pointer dereference", "paths" : [ { "editType" : "edit", "file" : "tools/lib/bpf/libbpf.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/testing/selftests/bpf/progs/test_lwt_seg6local.c" ], "commitId" : "f9cae71207944073060748d14df8915fb721a349", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "selftests: bpf: fix inlines in test_lwt_seg6local\u000a\u000a[ Upstream commit 11aca65ec4db09527d3e9b6b41a0615b7da4386b ]\u000a\u000aSelftests are reporting this failure in test_lwt_seg6local.sh:\u000a\u000a+ ip netns exec ns2 ip -6 route add fb00::6 encap bpf in obj test_lwt_seg6local.o sec encap_srh dev veth2\u000aError fetching program/map!\u000aFailed to parse eBPF program: Operation not permitted\u000a\u000aThe problem is __attribute__((always_inline)) alone is not enough to prevent\u000aclang from inserting those functions in .text. In that case, .text is not\u000amarked as relocateable.\u000a\u000aSee the output of objdump -h test_lwt_seg6local.o:\u000a\u000aIdx Name Size VMA LMA File off Algn\u000a 0 .text 00003530 0000000000000000 0000000000000000 00000040 2**3\u000a CONTENTS, ALLOC, LOAD, READONLY, CODE\u000a\u000aThis causes the iproute bpf loader to fail in bpf_fetch_prog_sec:\u000abpf_has_call_data returns true but bpf_fetch_prog_relo fails as there's no\u000arelocateable .text section in the file.\u000a\u000aTo fix this, convert to 'static __always_inline'.\u000a\u000av2: Use 'static __always_inline' instead of 'static inline\u000a __attribute__((always_inline))'\u000a\u000aFixes: c99a84eac026 (\"selftests/bpf: test for seg6local End.BPF action\")\u000aSigned-off-by: Jiri Benc \u000aAcked-by: Yonghong Song \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "f9cae71207944073060748d14df8915fb721a349", "msg" : "selftests: bpf: fix inlines in test_lwt_seg6local", "paths" : [ { "editType" : "edit", "file" : "tools/testing/selftests/bpf/progs/test_lwt_seg6local.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/bonding/bond_main.c" ], "commitId" : "6ddf081387cba861b48bcaa1fe931dfa796a2bc8", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bonding: validate ip header before check IPPROTO_IGMP\u000a\u000a[ Upstream commit 9d1bc24b52fb8c5d859f9a47084bf1179470e04c ]\u000a\u000abond_xmit_roundrobin() checks for IGMP packets but it parses\u000athe IP header even before checking skb->protocol.\u000a\u000aWe should validate the IP header with pskb_may_pull() before\u000ausing iph->protocol.\u000a\u000aReported-and-tested-by: syzbot+e5be16aa39ad6e755391@syzkaller.appspotmail.com\u000aFixes: a2fd940f4cff (\"bonding: fix broken multicast with round-robin mode\")\u000aCc: Jay Vosburgh \u000aCc: Veaceslav Falico \u000aCc: Andy Gospodarek \u000aSigned-off-by: Cong Wang \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "6ddf081387cba861b48bcaa1fe931dfa796a2bc8", "msg" : "bonding: validate ip header before check IPPROTO_IGMP", "paths" : [ { "editType" : "edit", "file" : "drivers/net/bonding/bond_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpiolib.c" ], "commitId" : "cbd7d2d8a7fe8a1c6e7f51437d7d24db8a3c91bb", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpiolib: Fix references to gpiod_[gs]et_*value_cansleep() variants\u000a\u000a[ Upstream commit 3285170f28a850638794cdfe712eb6d93e51e706 ]\u000a\u000aCommit 372e722ea4dd4ca1 (\"gpiolib: use descriptors internally\") renamed\u000athe functions to use a \"gpiod\" prefix, and commit 79a9becda8940deb\u000a(\"gpiolib: export descriptor-based GPIO interface\") introduced the \"raw\"\u000avariants, but both changes forgot to update the comments.\u000a\u000aReadd a similar reference to gpiod_set_value(), which was accidentally\u000aremoved by commit 1e77fc82110ac36f (\"gpio: Add missing open drain/source\u000ahandling to gpiod_set_value_cansleep()\").\u000a\u000aSigned-off-by: Geert Uytterhoeven \u000aLink: https://lore.kernel.org/r/20190701142738.25219-1-geert+renesas@glider.be\u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "cbd7d2d8a7fe8a1c6e7f51437d7d24db8a3c91bb", "msg" : "gpiolib: Fix references to gpiod_[gs]et_*value_cansleep() variants", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpiolib.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/generic/audio-graph-card.c" ], "commitId" : "b2e77a926e590fc551e9e66d5e9f091c8f8eda0a", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: audio-graph-card: fix use-after-free in graph_for_each_link\u000a\u000a[ Upstream commit 1bcc1fd64e4dd903f4d868a9e053986e3b102713 ]\u000a\u000aAfter calling of_node_put() on the codec_ep and codec_port variables,\u000athey are still being used, which may result in use-after-free.\u000aWe fix this issue by calling of_node_put() after the last usage.\u000a\u000aFixes: fce9b90c1ab7 (\"ASoC: audio-graph-card: cleanup DAI link loop method - step2\")\u000aSigned-off-by: Wen Yang \u000aCc: Liam Girdwood \u000aCc: Mark Brown \u000aCc: Jaroslav Kysela \u000aCc: Takashi Iwai \u000aCc: Kuninori Morimoto \u000aCc: alsa-devel@alsa-project.org\u000aCc: linux-kernel@vger.kernel.org\u000aLink: https://lore.kernel.org/r/1562229530-8121-1-git-send-email-wen.yang99@zte.com.cn\u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "b2e77a926e590fc551e9e66d5e9f091c8f8eda0a", "msg" : "ASoC: audio-graph-card: fix use-after-free in graph_for_each_link", "paths" : [ { "editType" : "edit", "file" : "sound/soc/generic/audio-graph-card.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/bpf/bpftool/jit_disasm.c" ], "commitId" : "7213304057eff2576fc1762ce277d371e18d5352", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tools: bpftool: Fix json dump crash on powerpc\u000a\u000a[ Upstream commit aa52bcbe0e72fac36b1862db08b9c09c4caefae3 ]\u000a\u000aMichael reported crash with by bpf program in json mode on powerpc:\u000a\u000a # bpftool prog -p dump jited id 14\u000a [{\u000a \"name\": \"0xd00000000a9aa760\",\u000a \"insns\": [{\u000a \"pc\": \"0x0\",\u000a \"operation\": \"nop\",\u000a \"operands\": [null\u000a ]\u000a },{\u000a \"pc\": \"0x4\",\u000a \"operation\": \"nop\",\u000a \"operands\": [null\u000a ]\u000a },{\u000a \"pc\": \"0x8\",\u000a \"operation\": \"mflr\",\u000a Segmentation fault (core dumped)\u000a\u000aThe code is assuming char pointers in format, which is not always\u000atrue at least for powerpc. Fixing this by dumping the whole string\u000ainto buffer based on its format.\u000a\u000aPlease note that libopcodes code does not check return values from\u000afprintf callback, but as per Jakub suggestion returning -1 on allocation\u000afailure so we do the best effort to propagate the error.\u000a\u000aFixes: 107f041212c1 (\"tools: bpftool: add JSON output for `bpftool prog dump jited *` command\")\u000aReported-by: Michael Petlan \u000aSigned-off-by: Jiri Olsa \u000aReviewed-by: Quentin Monnet \u000aReviewed-by: Jakub Kicinski \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "7213304057eff2576fc1762ce277d371e18d5352", "msg" : "tools: bpftool: Fix json dump crash on powerpc", "paths" : [ { "editType" : "edit", "file" : "tools/bpf/bpftool/jit_disasm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c" ], "commitId" : "67e4a729f6c049db2a9d1158d53d3a7fc4af8083", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: enable broadcast promisc mode when initializing VF\u000a\u000a[ Upstream commit 2d5066fc175ea77a733d84df9ef414b34f311641 ]\u000a\u000aFor revision 0x20, the broadcast promisc is enabled by firmware,\u000ait's unnecessary to enable it when initializing VF.\u000a\u000aFor revision 0x21, it's necessary to enable broadcast promisc mode\u000awhen initializing or re-initializing VF, otherwise, it will be\u000aunable to send and receive promisc packets.\u000a\u000aFixes: f01f5559cac8 (\"net: hns3: don't allow vf to enable promisc mode\")\u000aSigned-off-by: Jian Shen \u000aSigned-off-by: Peng Li \u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "67e4a729f6c049db2a9d1158d53d3a7fc4af8083", "msg" : "net: hns3: enable broadcast promisc mode when initializing VF", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/bluetooth/hci_bcsp.c" ], "commitId" : "a1803984ef797ded1e576915f7ed82b63fc22f3d", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: hci_bcsp: Fix memory leak in rx_skb\u000a\u000a[ Upstream commit 4ce9146e0370fcd573f0372d9b4e5a211112567c ]\u000a\u000aSyzkaller found that it is possible to provoke a memory leak by\u000anever freeing rx_skb in struct bcsp_struct.\u000a\u000aFix by freeing in bcsp_close()\u000a\u000aSigned-off-by: Tomas Bortoli \u000aReported-by: syzbot+98162c885993b72f19c4@syzkaller.appspotmail.com\u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "a1803984ef797ded1e576915f7ed82b63fc22f3d", "msg" : "Bluetooth: hci_bcsp: Fix memory leak in rx_skb", "paths" : [ { "editType" : "edit", "file" : "drivers/bluetooth/hci_bcsp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/bluetooth/btusb.c" ], "commitId" : "7302488e55fa079c9e14f689f4c41b8312e3ac77", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: Add new 13d3:3491 QCA_ROME device\u000a\u000a[ Upstream commit 44d34af2e4cfd0c5357182f8b43f3e0a1fe30a2e ]\u000a\u000aWithout the QCA ROME setup routine this adapter fails to establish a SCO\u000aconnection.\u000a\u000aT: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=01 Dev#= 2 Spd=12 MxCh= 0\u000aD: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1\u000aP: Vendor=13d3 ProdID=3491 Rev=00.01\u000aC: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA\u000aI: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\u000aI: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\u000a\u000aSigned-off-by: João Paulo Rechi Vita \u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "7302488e55fa079c9e14f689f4c41b8312e3ac77", "msg" : "Bluetooth: Add new 13d3:3491 QCA_ROME device", "paths" : [ { "editType" : "edit", "file" : "drivers/bluetooth/btusb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/bluetooth/btusb.c" ], "commitId" : "39f0228a402a6d9d49de13aa9548765978519cab", "timestamp" : 1564125169000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: Add new 13d3:3501 QCA_ROME device\u000a\u000a[ Upstream commit 881cec4f6b4da78e54b73c046a60f39315964c7d ]\u000a\u000aWithout the QCA ROME setup routine this adapter fails to establish a SCO\u000aconnection.\u000a\u000aT: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 2 Spd=12 MxCh= 0\u000aD: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1\u000aP: Vendor=13d3 ProdID=3501 Rev=00.01\u000aC: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA\u000aI: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\u000aI: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\u000a\u000aSigned-off-by: João Paulo Rechi Vita \u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:49 +0200", "id" : "39f0228a402a6d9d49de13aa9548765978519cab", "msg" : "Bluetooth: Add new 13d3:3501 QCA_ROME device", "paths" : [ { "editType" : "edit", "file" : "drivers/bluetooth/btusb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bluetooth/6lowpan.c" ], "commitId" : "0eb799964db313c8b13a39a0c291da91c416daf3", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: 6lowpan: search for destination address in all peers\u000a\u000a[ Upstream commit b188b03270b7f8568fc714101ce82fbf5e811c5a ]\u000a\u000aHandle overlooked case where the target address is assigned to a peer\u000aand neither route nor gateway exist.\u000a\u000aFor one peer, no checks are performed to see if it is meant to receive\u000apackets for a given address.\u000a\u000aAs soon as there is a second peer however, checks are performed\u000ato deal with routes and gateways for handling complex setups with\u000amultiple hops to a target address.\u000aThis logic assumed that no route and no gateway imply that the\u000adestination address can not be reached, which is false in case of a\u000adirect peer.\u000a\u000aAcked-by: Jukka Rissanen \u000aTested-by: Michael Scott \u000aSigned-off-by: Josua Mayer \u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "0eb799964db313c8b13a39a0c291da91c416daf3", "msg" : "Bluetooth: 6lowpan: search for destination address in all peers", "paths" : [ { "editType" : "edit", "file" : "net/bluetooth/6lowpan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/irq/chip.c", "kernel/irq/irqdesc.c" ], "commitId" : "f260fc0c82267caec5d4bf8c53ae377b8454a6f6", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "genirq: Update irq stats from NMI handlers\u000a\u000a[ Upstream commit c09cb1293523dd786ae54a12fd88001542cba2f6 ]\u000a\u000aThe NMI handlers handle_percpu_devid_fasteoi_nmi() and handle_fasteoi_nmi()\u000ado not update the interrupt counts. Due to that the NMI interrupt count\u000adoes not show up correctly in /proc/interrupts.\u000a\u000aAdd the statistics and treat the NMI handlers in the same way as per cpu\u000ainterrupts and prevent them from updating irq_desc::tot_count as this might\u000abe corrupted due to concurrency.\u000a\u000a[ tglx: Massaged changelog ]\u000a\u000aFixes: 2dcf1fbcad35 (\"genirq: Provide NMI handlers\")\u000aSigned-off-by: Shijith Thotton \u000aSigned-off-by: Thomas Gleixner \u000aLink: https://lkml.kernel.org/r/1562313336-11888-1-git-send-email-sthotton@marvell.com\u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "f260fc0c82267caec5d4bf8c53ae377b8454a6f6", "msg" : "genirq: Update irq stats from NMI handlers", "paths" : [ { "editType" : "edit", "file" : "kernel/irq/chip.c" }, { "editType" : "edit", "file" : "kernel/irq/irqdesc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/tests/shell/record+probe_libc_inet_pton.sh" ], "commitId" : "4b81211d48ba1a3610f19ba34c159fa7ff819a3a", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf tests: Fix record+probe_libc_inet_pton.sh for powerpc64\u000a\u000a[ Upstream commit bff5a556c149804de29347a88a884d25e4e4e3a2 ]\u000a\u000a'probe libc's inet_pton & backtrace it with ping' testcase sometimes\u000afails on powerpc because distro ping binary does not have symbol\u000ainformation and thus it prints \"[unknown]\" function name in the\u000abacktrace.\u000a\u000aAccept \"[unknown]\" as valid function name for powerpc as well.\u000a\u000a # perf test -v \"probe libc's inet_pton & backtrace it with ping\"\u000a\u000aBefore:\u000a\u000a 59: probe libc's inet_pton & backtrace it with ping :\u000a --- start ---\u000a test child forked, pid 79695\u000a ping 79718 [077] 96483.787025: probe_libc:inet_pton: (7fff83a754c8)\u000a 7fff83a754c8 __GI___inet_pton+0x8 (/usr/lib64/power9/libc-2.28.so)\u000a 7fff83a2b7a0 gaih_inet.constprop.7+0x1020\u000a (/usr/lib64/power9/libc-2.28.so)\u000a 7fff83a2c170 getaddrinfo+0x160 (/usr/lib64/power9/libc-2.28.so)\u000a 1171830f4 [unknown] (/usr/bin/ping)\u000a FAIL: expected backtrace entry\u000a \".*\\+0x[[:xdigit:]]+[[:space:]]\\(.*/bin/ping.*\\)$\"\u000a got \"1171830f4 [unknown] (/usr/bin/ping)\"\u000a test child finished with -1\u000a ---- end ----\u000a probe libc's inet_pton & backtrace it with ping: FAILED!\u000a\u000aAfter:\u000a\u000a 59: probe libc's inet_pton & backtrace it with ping :\u000a --- start ---\u000a test child forked, pid 79085\u000a ping 79108 [045] 96400.214177: probe_libc:inet_pton: (7fffbb9654c8)\u000a 7fffbb9654c8 __GI___inet_pton+0x8 (/usr/lib64/power9/libc-2.28.so)\u000a 7fffbb91b7a0 gaih_inet.constprop.7+0x1020\u000a (/usr/lib64/power9/libc-2.28.so)\u000a 7fffbb91c170 getaddrinfo+0x160 (/usr/lib64/power9/libc-2.28.so)\u000a 132e830f4 [unknown] (/usr/bin/ping)\u000a test child finished with 0\u000a ---- end ----\u000a probe libc's inet_pton & backtrace it with ping: Ok\u000a\u000aSigned-off-by: Seeteena Thoufeek \u000aReviewed-by: Kim Phillips \u000aCc: Alexander Shishkin \u000aCc: Hendrik Brueckner \u000aCc: Jiri Olsa \u000aCc: Michael Petlan \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aCc: Sandipan Das \u000aFixes: 1632936480a5 (\"perf tests: Fix record+probe_libc_inet_pton.sh without ping's debuginfo\")\u000aLink: http://lkml.kernel.org/r/1561630614-3216-1-git-send-email-s1seetee@linux.vnet.ibm.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "4b81211d48ba1a3610f19ba34c159fa7ff819a3a", "msg" : "perf tests: Fix record+probe_libc_inet_pton.sh for powerpc64", "paths" : [ { "editType" : "edit", "file" : "tools/perf/tests/shell/record+probe_libc_inet_pton.sh" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bluetooth/l2cap_core.c" ], "commitId" : "9e8d3c92c59eabee227f9fd89715139a14e16dd8", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: Check state in l2cap_disconnect_rsp\u000a\u000a[ Upstream commit 28261da8a26f4915aa257d12d506c6ba179d961f ]\u000a\u000aBecause of both sides doing L2CAP disconnection at the same time, it\u000awas possible to receive L2CAP Disconnection Response with CID that was\u000aalready freed. That caused problems if CID was already reused and L2CAP\u000aConnection Request with same CID was sent out. Before this patch kernel\u000adeleted channel context regardless of the state of the channel.\u000a\u000aExample where leftover Disconnection Response (frame #402) causes local\u000adevice to delete L2CAP channel which was not yet connected. This in\u000aturn confuses remote device's stack because same CID is re-used without\u000aproperly disconnecting.\u000a\u000aBtmon capture before patch:\u000a** snip **\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 8 #394 [hci1] 10.748949\u000a Channel: 65 len 4 [PSM 3 mode 0] {chan 2}\u000a RFCOMM: Disconnect (DISC) (0x43)\u000a Address: 0x03 cr 1 dlci 0x00\u000a Control: 0x53 poll/final 1\u000a Length: 0\u000a FCS: 0xfd\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 8 #395 [hci1] 10.749062\u000a Channel: 65 len 4 [PSM 3 mode 0] {chan 2}\u000a RFCOMM: Unnumbered Ack (UA) (0x63)\u000a Address: 0x03 cr 1 dlci 0x00\u000a Control: 0x73 poll/final 1\u000a Length: 0\u000a FCS: 0xd7\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 12 #396 [hci1] 10.749073\u000a L2CAP: Disconnection Request (0x06) ident 17 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a> HCI Event: Number of Completed Packets (0x13) plen 5 #397 [hci1] 10.752391\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> HCI Event: Number of Completed Packets (0x13) plen 5 #398 [hci1] 10.753394\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 12 #399 [hci1] 10.756499\u000a L2CAP: Disconnection Request (0x06) ident 26 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 12 #400 [hci1] 10.756548\u000a L2CAP: Disconnection Response (0x07) ident 26 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 12 #401 [hci1] 10.757459\u000a L2CAP: Connection Request (0x02) ident 18 len 4\u000a PSM: 1 (0x0001)\u000a Source CID: 65\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 12 #402 [hci1] 10.759148\u000a L2CAP: Disconnection Response (0x07) ident 17 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a= bluetoothd: 00:1E:AB:4C:56:54: error updating services: Input/o.. 10.759447\u000a> HCI Event: Number of Completed Packets (0x13) plen 5 #403 [hci1] 10.759386\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 12 #404 [hci1] 10.760397\u000a L2CAP: Connection Request (0x02) ident 27 len 4\u000a PSM: 3 (0x0003)\u000a Source CID: 65\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 16 #405 [hci1] 10.760441\u000a L2CAP: Connection Response (0x03) ident 27 len 8\u000a Destination CID: 65\u000a Source CID: 65\u000a Result: Connection successful (0x0000)\u000a Status: No further information available (0x0000)\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 27 #406 [hci1] 10.760449\u000a L2CAP: Configure Request (0x04) ident 19 len 19\u000a Destination CID: 65\u000a Flags: 0x0000\u000a Option: Maximum Transmission Unit (0x01) [mandatory]\u000a MTU: 1013\u000a Option: Retransmission and Flow Control (0x04) [mandatory]\u000a Mode: Basic (0x00)\u000a TX window size: 0\u000a Max transmit: 0\u000a Retransmission timeout: 0\u000a Monitor timeout: 0\u000a Maximum PDU size: 0\u000a> HCI Event: Number of Completed Packets (0x13) plen 5 #407 [hci1] 10.761399\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 16 #408 [hci1] 10.762942\u000a L2CAP: Connection Response (0x03) ident 18 len 8\u000a Destination CID: 66\u000a Source CID: 65\u000a Result: Connection successful (0x0000)\u000a Status: No further information available (0x0000)\u000a*snip*\u000a\u000aSimilar case after the patch:\u000a*snip*\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 8 #22702 [hci0] 1664.411056\u000a Channel: 65 len 4 [PSM 3 mode 0] {chan 3}\u000a RFCOMM: Disconnect (DISC) (0x43)\u000a Address: 0x03 cr 1 dlci 0x00\u000a Control: 0x53 poll/final 1\u000a Length: 0\u000a FCS: 0xfd\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 8 #22703 [hci0] 1664.411136\u000a Channel: 65 len 4 [PSM 3 mode 0] {chan 3}\u000a RFCOMM: Unnumbered Ack (UA) (0x63)\u000a Address: 0x03 cr 1 dlci 0x00\u000a Control: 0x73 poll/final 1\u000a Length: 0\u000a FCS: 0xd7\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 12 #22704 [hci0] 1664.411143\u000a L2CAP: Disconnection Request (0x06) ident 11 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a> HCI Event: Number of Completed Pac.. (0x13) plen 5 #22705 [hci0] 1664.414009\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> HCI Event: Number of Completed Pac.. (0x13) plen 5 #22706 [hci0] 1664.415007\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 12 #22707 [hci0] 1664.418674\u000a L2CAP: Disconnection Request (0x06) ident 17 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 12 #22708 [hci0] 1664.418762\u000a L2CAP: Disconnection Response (0x07) ident 17 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 12 #22709 [hci0] 1664.421073\u000a L2CAP: Connection Request (0x02) ident 12 len 4\u000a PSM: 1 (0x0001)\u000a Source CID: 65\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 12 #22710 [hci0] 1664.421371\u000a L2CAP: Disconnection Response (0x07) ident 11 len 4\u000a Destination CID: 65\u000a Source CID: 65\u000a> HCI Event: Number of Completed Pac.. (0x13) plen 5 #22711 [hci0] 1664.424082\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> HCI Event: Number of Completed Pac.. (0x13) plen 5 #22712 [hci0] 1664.425040\u000a Num handles: 1\u000a Handle: 43\u000a Count: 1\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 12 #22713 [hci0] 1664.426103\u000a L2CAP: Connection Request (0x02) ident 18 len 4\u000a PSM: 3 (0x0003)\u000a Source CID: 65\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 16 #22714 [hci0] 1664.426186\u000a L2CAP: Connection Response (0x03) ident 18 len 8\u000a Destination CID: 66\u000a Source CID: 65\u000a Result: Connection successful (0x0000)\u000a Status: No further information available (0x0000)\u000a< ACL Data TX: Handle 43 flags 0x00 dlen 27 #22715 [hci0] 1664.426196\u000a L2CAP: Configure Request (0x04) ident 13 len 19\u000a Destination CID: 65\u000a Flags: 0x0000\u000a Option: Maximum Transmission Unit (0x01) [mandatory]\u000a MTU: 1013\u000a Option: Retransmission and Flow Control (0x04) [mandatory]\u000a Mode: Basic (0x00)\u000a TX window size: 0\u000a Max transmit: 0\u000a Retransmission timeout: 0\u000a Monitor timeout: 0\u000a Maximum PDU size: 0\u000a> ACL Data RX: Handle 43 flags 0x02 dlen 16 #22716 [hci0] 1664.428804\u000a L2CAP: Connection Response (0x03) ident 12 len 8\u000a Destination CID: 66\u000a Source CID: 65\u000a Result: Connection successful (0x0000)\u000a Status: No further information available (0x0000)\u000a*snip*\u000a\u000aFix is to check that channel is in state BT_DISCONN before deleting the\u000achannel.\u000a\u000aThis bug was found while fuzzing Bluez's OBEX implementation using\u000aSynopsys Defensics.\u000a\u000aReported-by: Matti Kamunen \u000aReported-by: Ari Timonen \u000aSigned-off-by: Matias Karhumaa \u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "9e8d3c92c59eabee227f9fd89715139a14e16dd8", "msg" : "Bluetooth: Check state in l2cap_disconnect_rsp", "paths" : [ { "editType" : "edit", "file" : "net/bluetooth/l2cap_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bluetooth/hidp/sock.c", "net/bluetooth/hidp/core.c" ], "commitId" : "11f91596e0c385ae61ff2d1e2707e0d1a48c9d37", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: hidp: NUL terminate a string in the compat ioctl\u000a\u000a[ Upstream commit dcae9052ebb0c5b2614de620323d615fcbfda7f8 ]\u000a\u000aThis change is similar to commit a1616a5ac99e (\"Bluetooth: hidp: fix\u000abuffer overflow\") but for the compat ioctl. We take a string from the\u000auser and forgot to ensure that it's NUL terminated.\u000a\u000aI have also changed the strncpy() in to strscpy() in hidp_setup_hid().\u000aThe difference is the strncpy() doesn't necessarily NUL terminate the\u000adestination string. Either change would fix the problem but it's nice\u000ato take a belt and suspenders approach and do both.\u000a\u000aSigned-off-by: Dan Carpenter \u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "11f91596e0c385ae61ff2d1e2707e0d1a48c9d37", "msg" : "Bluetooth: hidp: NUL terminate a string in the compat ioctl", "paths" : [ { "editType" : "edit", "file" : "net/bluetooth/hidp/core.c" }, { "editType" : "edit", "file" : "net/bluetooth/hidp/sock.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/gtp.c" ], "commitId" : "83e8d4c87dd3c215f501cce43a39c35f4fc4f9f5", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gtp: add missing gtp_encap_disable_sock() in gtp_encap_enable()\u000a\u000a[ Upstream commit e30155fd23c9c141cbe7d99b786e10a83a328837 ]\u000a\u000aIf an invalid role is sent from user space, gtp_encap_enable() will fail.\u000aThen, it should call gtp_encap_disable_sock() but current code doesn't.\u000aIt makes memory leak.\u000a\u000aFixes: 91ed81f9abc7 (\"gtp: support SGSN-side tunnels\")\u000aSigned-off-by: Taehee Yoo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "83e8d4c87dd3c215f501cce43a39c35f4fc4f9f5", "msg" : "gtp: add missing gtp_encap_disable_sock() in gtp_encap_enable()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/gtp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bluetooth/l2cap_core.c", "net/bluetooth/hci_event.c" ], "commitId" : "572af11ec2252a9c57cc6ee5e247ebe04da18bb7", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: validate BLE connection interval updates\u000a\u000a[ Upstream commit c49a8682fc5d298d44e8d911f4fa14690ea9485e ]\u000a\u000aProblem: The Linux Bluetooth stack yields complete control over the BLE\u000aconnection interval to the remote device.\u000a\u000aThe Linux Bluetooth stack provides access to the BLE connection interval\u000amin and max values through /sys/kernel/debug/bluetooth/hci0/\u000aconn_min_interval and /sys/kernel/debug/bluetooth/hci0/conn_max_interval.\u000aThese values are used for initial BLE connections, but the remote device\u000ahas the ability to request a connection parameter update. In the event\u000athat the remote side requests to change the connection interval, the Linux\u000akernel currently only validates that the desired value is within the\u000aacceptable range in the Bluetooth specification (6 - 3200, corresponding to\u000a7.5ms - 4000ms). There is currently no validation that the desired value\u000arequested by the remote device is within the min/max limits specified in\u000athe conn_min_interval/conn_max_interval configurations. This essentially\u000aleads to Linux yielding complete control over the connection interval to\u000athe remote device.\u000a\u000aThe proposed patch adds a verification step to the connection parameter\u000aupdate mechanism, ensuring that the desired value is within the min/max\u000abounds of the current connection. If the desired value is outside of the\u000acurrent connection min/max values, then the connection parameter update\u000arequest is rejected and the negative response is returned to the remote\u000adevice. Recall that the initial connection is established using the local\u000aconn_min_interval/conn_max_interval values, so this allows the Linux\u000aadministrator to retain control over the BLE connection interval.\u000a\u000aThe one downside that I see is that the current default Linux values for\u000aconn_min_interval and conn_max_interval typically correspond to 30ms and\u000a50ms respectively. If this change were accepted, then it is feasible that\u000asome devices would no longer be able to negotiate to their desired\u000aconnection interval values. This might be remedied by setting the default\u000aLinux conn_min_interval and conn_max_interval values to the widest\u000asupported range (6 - 3200 / 7.5ms - 4000ms). This could lead to the same\u000abehavior as the current implementation, where the remote device could\u000arequest to change the connection interval value to any value that is\u000apermitted by the Bluetooth specification, and Linux would accept the\u000adesired value.\u000a\u000aSigned-off-by: Carey Sonsino \u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "572af11ec2252a9c57cc6ee5e247ebe04da18bb7", "msg" : "Bluetooth: validate BLE connection interval updates", "paths" : [ { "editType" : "edit", "file" : "net/bluetooth/l2cap_core.c" }, { "editType" : "edit", "file" : "net/bluetooth/hci_event.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/gtp.c" ], "commitId" : "bf75202df8e473d4ee914894542f213158066d8b", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gtp: fix suspicious RCU usage\u000a\u000a[ Upstream commit e198987e7dd7d3645a53875151cd6f8fc425b706 ]\u000a\u000agtp_encap_enable_socket() and gtp_encap_destroy() are not protected\u000aby rcu_read_lock(). and it's not safe to write sk->sk_user_data.\u000aThis patch make these functions to use lock_sock() instead of\u000arcu_dereference_sk_user_data().\u000a\u000aTest commands:\u000a gtp-link add gtp1\u000a\u000aSplat looks like:\u000a[ 83.238315] =============================\u000a[ 83.239127] WARNING: suspicious RCU usage\u000a[ 83.239702] 5.2.0-rc6+ #49 Not tainted\u000a[ 83.240268] -----------------------------\u000a[ 83.241205] drivers/net/gtp.c:799 suspicious rcu_dereference_check() usage!\u000a[ 83.243828]\u000a[ 83.243828] other info that might help us debug this:\u000a[ 83.243828]\u000a[ 83.246325]\u000a[ 83.246325] rcu_scheduler_active = 2, debug_locks = 1\u000a[ 83.247314] 1 lock held by gtp-link/1008:\u000a[ 83.248523] #0: 0000000017772c7f (rtnl_mutex){+.+.}, at: __rtnl_newlink+0x5f5/0x11b0\u000a[ 83.251503]\u000a[ 83.251503] stack backtrace:\u000a[ 83.252173] CPU: 0 PID: 1008 Comm: gtp-link Not tainted 5.2.0-rc6+ #49\u000a[ 83.253271] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006\u000a[ 83.254562] Call Trace:\u000a[ 83.254995] dump_stack+0x7c/0xbb\u000a[ 83.255567] gtp_encap_enable_socket+0x2df/0x360 [gtp]\u000a[ 83.256415] ? gtp_find_dev+0x1a0/0x1a0 [gtp]\u000a[ 83.257161] ? memset+0x1f/0x40\u000a[ 83.257843] gtp_newlink+0x90/0xa21 [gtp]\u000a[ 83.258497] ? __netlink_ns_capable+0xc3/0xf0\u000a[ 83.259260] __rtnl_newlink+0xb9f/0x11b0\u000a[ 83.260022] ? rtnl_link_unregister+0x230/0x230\u000a[ ... ]\u000a\u000aFixes: 1e3a3abd8b28 (\"gtp: make GTP sockets in gtp_newlink optional\")\u000aSigned-off-by: Taehee Yoo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "bf75202df8e473d4ee914894542f213158066d8b", "msg" : "gtp: fix suspicious RCU usage", "paths" : [ { "editType" : "edit", "file" : "drivers/net/gtp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/gtp.c" ], "commitId" : "1ba3bba845b2f492b5901cbbd9c99e3b5452fad0", "timestamp" : 1564125170000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gtp: fix Illegal context switch in RCU read-side critical section.\u000a\u000a[ Upstream commit 3f167e1921865b379a9becf03828e7202c7b4917 ]\u000a\u000aipv4_pdp_add() is called in RCU read-side critical section.\u000aSo GFP_KERNEL should not be used in the function.\u000aThis patch make ipv4_pdp_add() to use GFP_ATOMIC instead of GFP_KERNEL.\u000a\u000aTest commands:\u000agtp-link add gtp1 &\u000agtp-tunnel add gtp1 v1 100 200 1.1.1.1 2.2.2.2\u000a\u000aSplat looks like:\u000a[ 130.618881] =============================\u000a[ 130.626382] WARNING: suspicious RCU usage\u000a[ 130.626994] 5.2.0-rc6+ #50 Not tainted\u000a[ 130.627622] -----------------------------\u000a[ 130.628223] ./include/linux/rcupdate.h:266 Illegal context switch in RCU read-side critical section!\u000a[ 130.629684]\u000a[ 130.629684] other info that might help us debug this:\u000a[ 130.629684]\u000a[ 130.631022]\u000a[ 130.631022] rcu_scheduler_active = 2, debug_locks = 1\u000a[ 130.632136] 4 locks held by gtp-tunnel/1025:\u000a[ 130.632925] #0: 000000002b93c8b7 (cb_lock){++++}, at: genl_rcv+0x15/0x40\u000a[ 130.634159] #1: 00000000f17bc999 (genl_mutex){+.+.}, at: genl_rcv_msg+0xfb/0x130\u000a[ 130.635487] #2: 00000000c644ed8e (rtnl_mutex){+.+.}, at: gtp_genl_new_pdp+0x18c/0x1150 [gtp]\u000a[ 130.636936] #3: 0000000007a1cde7 (rcu_read_lock){....}, at: gtp_genl_new_pdp+0x187/0x1150 [gtp]\u000a[ 130.638348]\u000a[ 130.638348] stack backtrace:\u000a[ 130.639062] CPU: 1 PID: 1025 Comm: gtp-tunnel Not tainted 5.2.0-rc6+ #50\u000a[ 130.641318] Call Trace:\u000a[ 130.641707] dump_stack+0x7c/0xbb\u000a[ 130.642252] ___might_sleep+0x2c0/0x3b0\u000a[ 130.642862] kmem_cache_alloc_trace+0x1cd/0x2b0\u000a[ 130.643591] gtp_genl_new_pdp+0x6c5/0x1150 [gtp]\u000a[ 130.644371] genl_family_rcv_msg+0x63a/0x1030\u000a[ 130.645074] ? mutex_lock_io_nested+0x1090/0x1090\u000a[ 130.645845] ? genl_unregister_family+0x630/0x630\u000a[ 130.646592] ? debug_show_all_locks+0x2d0/0x2d0\u000a[ 130.647293] ? check_flags.part.40+0x440/0x440\u000a[ 130.648099] genl_rcv_msg+0xa3/0x130\u000a[ ... ]\u000a\u000aFixes: 459aa660eb1d (\"gtp: add initial driver for datapath of GPRS Tunneling Protocol (GTP-U)\")\u000aSigned-off-by: Taehee Yoo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:50 +0200", "id" : "1ba3bba845b2f492b5901cbbd9c99e3b5452fad0", "msg" : "gtp: fix Illegal context switch in RCU read-side critical section.", "paths" : [ { "editType" : "edit", "file" : "drivers/net/gtp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/gtp.c" ], "commitId" : "8b9673c24ce734e0e10237a4434b1811aa9a4ce8", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gtp: fix use-after-free in gtp_encap_destroy()\u000a\u000a[ Upstream commit 1788b8569f5de27da09087fa3f6580d2aa04cc75 ]\u000a\u000agtp_encap_destroy() is called twice.\u000a1. When interface is deleted.\u000a2. When udp socket is destroyed.\u000aeither gtp->sk0 or gtp->sk1u could be freed by sock_put() in\u000agtp_encap_destroy(). so, when gtp_encap_destroy() is called again,\u000ait would uses freed sk pointer.\u000a\u000apatch makes gtp_encap_destroy() to set either gtp->sk0 or gtp->sk1u to\u000anull. in addition, both gtp->sk0 and gtp->sk1u pointer are protected\u000aby rtnl_lock. so, rtnl_lock() is added.\u000a\u000aTest command:\u000a gtp-link add gtp1 &\u000a killall gtp-link\u000a ip link del gtp1\u000a\u000aSplat looks like:\u000a[ 83.182767] BUG: KASAN: use-after-free in __lock_acquire+0x3a20/0x46a0\u000a[ 83.184128] Read of size 8 at addr ffff8880cc7d5360 by task ip/1008\u000a[ 83.185567] CPU: 1 PID: 1008 Comm: ip Not tainted 5.2.0-rc6+ #50\u000a[ 83.188469] Call Trace:\u000a[ ... ]\u000a[ 83.200126] lock_acquire+0x141/0x380\u000a[ 83.200575] ? lock_sock_nested+0x3a/0xf0\u000a[ 83.201069] _raw_spin_lock_bh+0x38/0x70\u000a[ 83.201551] ? lock_sock_nested+0x3a/0xf0\u000a[ 83.202044] lock_sock_nested+0x3a/0xf0\u000a[ 83.202520] gtp_encap_destroy+0x18/0xe0 [gtp]\u000a[ 83.203065] gtp_encap_disable.isra.14+0x13/0x50 [gtp]\u000a[ 83.203687] gtp_dellink+0x56/0x170 [gtp]\u000a[ 83.204190] rtnl_delete_link+0xb4/0x100\u000a[ ... ]\u000a[ 83.236513] Allocated by task 976:\u000a[ 83.236925] save_stack+0x19/0x80\u000a[ 83.237332] __kasan_kmalloc.constprop.3+0xa0/0xd0\u000a[ 83.237894] kmem_cache_alloc+0xd8/0x280\u000a[ 83.238360] sk_prot_alloc.isra.42+0x50/0x200\u000a[ 83.238874] sk_alloc+0x32/0x940\u000a[ 83.239264] inet_create+0x283/0xc20\u000a[ 83.239684] __sock_create+0x2dd/0x540\u000a[ 83.240136] __sys_socket+0xca/0x1a0\u000a[ 83.240550] __x64_sys_socket+0x6f/0xb0\u000a[ 83.240998] do_syscall_64+0x9c/0x450\u000a[ 83.241466] entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a[ 83.242061]\u000a[ 83.242249] Freed by task 0:\u000a[ 83.242616] save_stack+0x19/0x80\u000a[ 83.243013] __kasan_slab_free+0x111/0x150\u000a[ 83.243498] kmem_cache_free+0x89/0x250\u000a[ 83.244444] __sk_destruct+0x38f/0x5a0\u000a[ 83.245366] rcu_core+0x7e9/0x1c20\u000a[ 83.245766] __do_softirq+0x213/0x8fa\u000a\u000aFixes: 1e3a3abd8b28 (\"gtp: make GTP sockets in gtp_newlink optional\")\u000aSigned-off-by: Taehee Yoo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "8b9673c24ce734e0e10237a4434b1811aa9a4ce8", "msg" : "gtp: fix use-after-free in gtp_encap_destroy()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/gtp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/gtp.c" ], "commitId" : "29af1ae8002585a40ddd9e670ba8d383c5696fdc", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gtp: fix use-after-free in gtp_newlink()\u000a\u000a[ Upstream commit a2bed90704c68d3763bf24decb1b781a45395de8 ]\u000a\u000aCurrent gtp_newlink() could be called after unregister_pernet_subsys().\u000agtp_newlink() uses gtp_net but it can be destroyed by\u000aunregister_pernet_subsys().\u000aSo unregister_pernet_subsys() should be called after\u000artnl_link_unregister().\u000a\u000aTest commands:\u000a #SHELL 1\u000a while :\u000a do\u000a\u0009 for i in {1..5}\u000a\u0009 do\u000a\u0009\u0009./gtp-link add gtp$i &\u000a\u0009 done\u000a\u0009 killall gtp-link\u000a done\u000a\u000a #SHELL 2\u000a while :\u000a do\u000a\u0009modprobe -rv gtp\u000a done\u000a\u000aSplat looks like:\u000a[ 753.176631] BUG: KASAN: use-after-free in gtp_newlink+0x9b4/0xa5c [gtp]\u000a[ 753.177722] Read of size 8 at addr ffff8880d48f2458 by task gtp-link/7126\u000a[ 753.179082] CPU: 0 PID: 7126 Comm: gtp-link Tainted: G W 5.2.0-rc6+ #50\u000a[ 753.185801] Call Trace:\u000a[ 753.186264] dump_stack+0x7c/0xbb\u000a[ 753.186863] ? gtp_newlink+0x9b4/0xa5c [gtp]\u000a[ 753.187583] print_address_description+0xc7/0x240\u000a[ 753.188382] ? gtp_newlink+0x9b4/0xa5c [gtp]\u000a[ 753.189097] ? gtp_newlink+0x9b4/0xa5c [gtp]\u000a[ 753.189846] __kasan_report+0x12a/0x16f\u000a[ 753.190542] ? gtp_newlink+0x9b4/0xa5c [gtp]\u000a[ 753.191298] kasan_report+0xe/0x20\u000a[ 753.191893] gtp_newlink+0x9b4/0xa5c [gtp]\u000a[ 753.192580] ? __netlink_ns_capable+0xc3/0xf0\u000a[ 753.193370] __rtnl_newlink+0xb9f/0x11b0\u000a[ ... ]\u000a[ 753.241201] Allocated by task 7186:\u000a[ 753.241844] save_stack+0x19/0x80\u000a[ 753.242399] __kasan_kmalloc.constprop.3+0xa0/0xd0\u000a[ 753.243192] __kmalloc+0x13e/0x300\u000a[ 753.243764] ops_init+0xd6/0x350\u000a[ 753.244314] register_pernet_operations+0x249/0x6f0\u000a[ ... ]\u000a[ 753.251770] Freed by task 7178:\u000a[ 753.252288] save_stack+0x19/0x80\u000a[ 753.252833] __kasan_slab_free+0x111/0x150\u000a[ 753.253962] kfree+0xc7/0x280\u000a[ 753.254509] ops_free_list.part.11+0x1c4/0x2d0\u000a[ 753.255241] unregister_pernet_operations+0x262/0x390\u000a[ ... ]\u000a[ 753.285883] list_add corruption. next->prev should be prev (ffff8880d48f2458), but was ffff8880d497d878. (next.\u000a[ 753.287241] ------------[ cut here ]------------\u000a[ 753.287794] kernel BUG at lib/list_debug.c:25!\u000a[ 753.288364] invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI\u000a[ 753.289099] CPU: 0 PID: 7126 Comm: gtp-link Tainted: G B W 5.2.0-rc6+ #50\u000a[ 753.291036] RIP: 0010:__list_add_valid+0x74/0xd0\u000a[ 753.291589] Code: 48 39 da 75 27 48 39 f5 74 36 48 39 dd 74 31 48 83 c4 08 b8 01 00 00 00 5b 5d c3 48 89 d9 48b\u000a[ 753.293779] RSP: 0018:ffff8880cae8f398 EFLAGS: 00010286\u000a[ 753.294401] RAX: 0000000000000075 RBX: ffff8880d497d878 RCX: 0000000000000000\u000a[ 753.296260] RDX: 0000000000000075 RSI: 0000000000000008 RDI: ffffed10195d1e69\u000a[ 753.297070] RBP: ffff8880cd250ae0 R08: ffffed101b4bff21 R09: ffffed101b4bff21\u000a[ 753.297899] R10: 0000000000000001 R11: ffffed101b4bff20 R12: ffff8880d497d878\u000a[ 753.298703] R13: 0000000000000000 R14: ffff8880cd250ae0 R15: ffff8880d48f2458\u000a[ 753.299564] FS: 00007f5f79805740(0000) GS:ffff8880da400000(0000) knlGS:0000000000000000\u000a[ 753.300533] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 753.301231] CR2: 00007fe8c7ef4f10 CR3: 00000000b71a6006 CR4: 00000000000606f0\u000a[ 753.302183] Call Trace:\u000a[ 753.302530] gtp_newlink+0x5f6/0xa5c [gtp]\u000a[ 753.303037] ? __netlink_ns_capable+0xc3/0xf0\u000a[ 753.303576] __rtnl_newlink+0xb9f/0x11b0\u000a[ 753.304092] ? rtnl_link_unregister+0x230/0x230\u000a\u000aFixes: 459aa660eb1d (\"gtp: add initial driver for datapath of GPRS Tunneling Protocol (GTP-U)\")\u000aSigned-off-by: Taehee Yoo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "29af1ae8002585a40ddd9e670ba8d383c5696fdc", "msg" : "gtp: fix use-after-free in gtp_newlink()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/gtp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/net/xdp_sock.h", "net/xdp/xsk.c" ], "commitId" : "fd7c22ba7a0ad898b9ecf77dd53f5ccc48492e35", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xdp: fix race on generic receive path\u000a\u000a[ Upstream commit bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 ]\u000a\u000aUnlike driver mode, generic xdp receive could be triggered\u000aby different threads on different CPU cores at the same time\u000aleading to the fill and rx queue breakage. For example, this\u000acould happen while sending packets from two processes to the\u000afirst interface of veth pair while the second part of it is\u000aopen with AF_XDP socket.\u000a\u000aNeed to take a lock for each generic receive to avoid race.\u000a\u000aFixes: c497176cb2e4 (\"xsk: add Rx receive functions and poll support\")\u000aSigned-off-by: Ilya Maximets \u000aAcked-by: Magnus Karlsson \u000aTested-by: William Tu \u000aSigned-off-by: Daniel Borkmann \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "fd7c22ba7a0ad898b9ecf77dd53f5ccc48492e35", "msg" : "xdp: fix race on generic receive path", "paths" : [ { "editType" : "edit", "file" : "net/xdp/xsk.c" }, { "editType" : "edit", "file" : "include/net/xdp_sock.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/marvell/mvmdio.c" ], "commitId" : "067471e8d1475bf2b86b37cc6b95fab55a77ea08", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: mvmdio: defer probe of orion-mdio if a clock is not ready\u000a\u000a[ Upstream commit 433a06d7d74e677c40b1148c70c48677ff62fb6b ]\u000a\u000aDefer probing of the orion-mdio interface when getting a clock returns\u000aEPROBE_DEFER. This avoids locking up the Armada 8k SoC when mdio is used\u000abefore all clocks have been enabled.\u000a\u000aSigned-off-by: Josua Mayer \u000aReviewed-by: Andrew Lunn \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "067471e8d1475bf2b86b37cc6b95fab55a77ea08", "msg" : "net: mvmdio: defer probe of orion-mdio if a clock is not ready", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/marvell/mvmdio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" ], "commitId" : "5be48072f2ddad8968d3adb3856d021d73fd4295", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: hns3: fix __QUEUE_STATE_STACK_XOFF not cleared issue\u000a\u000a[ Upstream commit f96315f2f17e7b2580d2fec7c4d6a706a131d904 ]\u000a\u000aWhen change MTU or other operations, which just calling .reset_notify\u000ato do HNAE3_DOWN_CLIENT and HNAE3_UP_CLIENT, then\u000athe netdev_tx_reset_queue() in the hns3_clear_all_ring() will be\u000aignored. So the dev_watchdog() may misdiagnose a TX timeout.\u000a\u000aThis patch separates netdev_tx_reset_queue() from\u000ahns3_clear_all_ring(), and unifies hns3_clear_all_ring() and\u000ahns3_force_clear_all_ring into one, since they are doing\u000asimilar things.\u000a\u000aFixes: 3a30964a2eef (\"net: hns3: delay ring buffer clearing during reset\")\u000aSigned-off-by: Huazhong Tan \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "5be48072f2ddad8968d3adb3856d021d73fd4295", "msg" : "net: hns3: fix __QUEUE_STATE_STACK_XOFF not cleared issue", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/hisilicon/hns3/hns3_enet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/intel/iavf/iavf_txrx.c" ], "commitId" : "c05dbbddde888b51f8d94e502d435b0657a206a0", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iavf: fix dereference of null rx_buffer pointer\u000a\u000a[ Upstream commit 9fe06a51287b2d41baef7ece94df34b5abf19b90 ]\u000a\u000aA recent commit efa14c3985828d (\"iavf: allow null RX descriptors\") added\u000aa null pointer sanity check on rx_buffer, however, rx_buffer is being\u000adereferenced before that check, which implies a null pointer dereference\u000abug can potentially occur. Fix this by only dereferencing rx_buffer\u000auntil after the null pointer check.\u000a\u000aAddresses-Coverity: (\"Dereference before null check\")\u000aSigned-off-by: Colin Ian King \u000aTested-by: Andrew Bowers \u000aSigned-off-by: Jeff Kirsher \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "c05dbbddde888b51f8d94e502d435b0657a206a0", "msg" : "iavf: fix dereference of null rx_buffer pointer", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/intel/iavf/iavf_txrx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/blk-iolatency.c" ], "commitId" : "9a3aaff71f74d319fa1ba2bf8316a4558f841ab3", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "blk-iolatency: fix STS_AGAIN handling\u000a\u000a[ Upstream commit c9b3007feca018d3f7061f5d5a14cb00766ffe9b ]\u000a\u000aThe iolatency controller is based on rq_qos. It increments on\u000arq_qos_throttle() and decrements on either rq_qos_cleanup() or\u000arq_qos_done_bio(). a3fb01ba5af0 fixes the double accounting issue where\u000ablk_mq_make_request() may call both rq_qos_cleanup() and\u000arq_qos_done_bio() on REQ_NO_WAIT. So checking STS_AGAIN prevents the\u000adouble decrement.\u000a\u000aThe above works upstream as the only way we can get STS_AGAIN is from\u000ablk_mq_get_request() failing. The STS_AGAIN handling isn't a real\u000aproblem as bio_endio() skipping only happens on reserved tag allocation\u000afailures which can only be caused by driver bugs and already triggers\u000aWARN.\u000a\u000aHowever, the fix creates a not so great dependency on how STS_AGAIN can\u000abe propagated. Internally, we (Facebook) carry a patch that kills read\u000aahead if a cgroup is io congested or a fatal signal is pending. This\u000acombined with chained bios progagate their bi_status to the parent is\u000anot already set can can cause the parent bio to not clean up properly\u000aeven though it was successful. This consequently leaks the inflight\u000acounter and can hang all IOs under that blkg.\u000a\u000aTo nip the adverse interaction early, this removes the rq_qos_cleanup()\u000acallback in iolatency in favor of cleaning up always on the\u000arq_qos_done_bio() path.\u000a\u000aFixes: a3fb01ba5af0 (\"blk-iolatency: only account submitted bios\")\u000aDebugged-by: Tejun Heo \u000aDebugged-by: Josef Bacik \u000aSigned-off-by: Dennis Zhou \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "9a3aaff71f74d319fa1ba2bf8316a4558f841ab3", "msg" : "blk-iolatency: fix STS_AGAIN handling", "paths" : [ { "editType" : "edit", "file" : "block/blk-iolatency.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/lib/bpf/xsk.c" ], "commitId" : "ae01e55f53c3bfa6d4c4924958742f3837cadeaf", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "libbpf: fix another GCC8 warning for strncpy\u000a\u000a[ Upstream commit 763ff0e7d9c72e7094b31e7fb84a859be9325635 ]\u000a\u000aSimilar issue was fixed in cdfc7f888c2a (\"libbpf: fix GCC8 warning for\u000astrncpy\") already. This one was missed. Fixing now.\u000a\u000aCc: Magnus Karlsson \u000aSigned-off-by: Andrii Nakryiko \u000aAcked-by: Magnus Karlsson \u000aSigned-off-by: Alexei Starovoitov \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "ae01e55f53c3bfa6d4c4924958742f3837cadeaf", "msg" : "libbpf: fix another GCC8 warning for strncpy", "paths" : [ { "editType" : "edit", "file" : "tools/lib/bpf/xsk.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/block/floppy.c" ], "commitId" : "a2bd7b416d22a391cf095cb901ab52d10e264681", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "floppy: fix div-by-zero in setup_format_params\u000a\u000a[ Upstream commit f3554aeb991214cbfafd17d55e2bfddb50282e32 ]\u000a\u000aThis fixes a divide by zero error in the setup_format_params function of\u000athe floppy driver.\u000a\u000aTwo consecutive ioctls can trigger the bug: The first one should set the\u000adrive geometry with such .sect and .rate values for the F_SECT_PER_TRACK\u000ato become zero. Next, the floppy format operation should be called.\u000a\u000aA floppy disk is not required to be inserted. An unprivileged user\u000acould trigger the bug if the device is accessible.\u000a\u000aThe patch checks F_SECT_PER_TRACK for a non-zero value in the\u000aset_geometry function. The proper check should involve a reasonable\u000aupper limit for the .sect and .rate fields, but it could change the\u000aUAPI.\u000a\u000aThe patch also checks F_SECT_PER_TRACK in the setup_format_params, and\u000acancels the formatting operation in case of zero.\u000a\u000aThe bug was found by syzkaller.\u000a\u000aSigned-off-by: Denis Efremov \u000aTested-by: Willy Tarreau \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "a2bd7b416d22a391cf095cb901ab52d10e264681", "msg" : "floppy: fix div-by-zero in setup_format_params", "paths" : [ { "editType" : "edit", "file" : "drivers/block/floppy.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/block/floppy.c" ], "commitId" : "acf80219707230a9f67cc0a554e452c43aaa8733", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "floppy: fix out-of-bounds read in next_valid_format\u000a\u000a[ Upstream commit 5635f897ed83fd539df78e98ba69ee91592f9bb8 ]\u000a\u000aThis fixes a global out-of-bounds read access in the next_valid_format\u000afunction of the floppy driver.\u000a\u000aThe values from autodetect field of the struct floppy_drive_params are\u000aused as indices for the floppy_type array in the next_valid_format\u000afunction 'floppy_type[DP->autodetect[probed_format]].sect'.\u000a\u000aTo trigger the bug, one could use a value out of range and set the drive\u000aparameters with the FDSETDRVPRM ioctl. A floppy disk is not required to\u000abe inserted.\u000a\u000aCAP_SYS_ADMIN is required to call FDSETDRVPRM.\u000a\u000aThe patch adds the check for values of the autodetect field to be in the\u000a'0 <= x < ARRAY_SIZE(floppy_type)' range of the floppy_type array indices.\u000a\u000aThe bug was found by syzkaller.\u000a\u000aSigned-off-by: Denis Efremov \u000aTested-by: Willy Tarreau \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "acf80219707230a9f67cc0a554e452c43aaa8733", "msg" : "floppy: fix out-of-bounds read in next_valid_format", "paths" : [ { "editType" : "edit", "file" : "drivers/block/floppy.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/block/floppy.c" ], "commitId" : "deaa1395704c12ebea8c30a6da15b47ca3f88af5", "timestamp" : 1564125171000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "floppy: fix invalid pointer dereference in drive_name\u000a\u000a[ Upstream commit 9b04609b784027968348796a18f601aed9db3789 ]\u000a\u000aThis fixes the invalid pointer dereference in the drive_name function of\u000athe floppy driver.\u000a\u000aThe native_format field of the struct floppy_drive_params is used as\u000afloppy_type array index in the drive_name function. Thus, the field\u000ashould be checked the same way as the autodetect field.\u000a\u000aTo trigger the bug, one could use a value out of range and set the drive\u000aparameters with the FDSETDRVPRM ioctl. Next, FDGETDRVTYP ioctl should\u000abe used to call the drive_name. A floppy disk is not required to be\u000ainserted.\u000a\u000aCAP_SYS_ADMIN is required to call FDSETDRVPRM.\u000a\u000aThe patch adds the check for a value of the native_format field to be in\u000athe '0 <= x < ARRAY_SIZE(floppy_type)' range of the floppy_type array\u000aindices.\u000a\u000aThe bug was found by syzkaller.\u000a\u000aSigned-off-by: Denis Efremov \u000aTested-by: Willy Tarreau \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:51 +0200", "id" : "deaa1395704c12ebea8c30a6da15b47ca3f88af5", "msg" : "floppy: fix invalid pointer dereference in drive_name", "paths" : [ { "editType" : "edit", "file" : "drivers/block/floppy.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/block/floppy.c" ], "commitId" : "0a67173bdf79bc7f45947b998a5beadff03bce00", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "floppy: fix out-of-bounds read in copy_buffer\u000a\u000a[ Upstream commit da99466ac243f15fbba65bd261bfc75ffa1532b6 ]\u000a\u000aThis fixes a global out-of-bounds read access in the copy_buffer\u000afunction of the floppy driver.\u000a\u000aThe FDDEFPRM ioctl allows one to set the geometry of a disk. The sect\u000aand head fields (unsigned int) of the floppy_drive structure are used to\u000acompute the max_sector (int) in the make_raw_rw_request function. It is\u000apossible to overflow the max_sector. Next, max_sector is passed to the\u000acopy_buffer function and used in one of the memcpy calls.\u000a\u000aAn unprivileged user could trigger the bug if the device is accessible,\u000abut requires a floppy disk to be inserted.\u000a\u000aThe patch adds the check for the .sect * .head multiplication for not\u000aoverflowing in the set_geometry function.\u000a\u000aThe bug was found by syzkaller.\u000a\u000aSigned-off-by: Denis Efremov \u000aTested-by: Willy Tarreau \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "0a67173bdf79bc7f45947b998a5beadff03bce00", "msg" : "floppy: fix out-of-bounds read in copy_buffer", "paths" : [ { "editType" : "edit", "file" : "drivers/block/floppy.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/xen/balloon.c" ], "commitId" : "1548da4859c7a03808541616b723607da88d04ef", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xen: let alloc_xenballooned_pages() fail if not enough memory free\u000a\u000acommit a1078e821b605813b63bf6bca414a85f804d5c66 upstream.\u000a\u000aInstead of trying to allocate pages with GFP_USER in\u000aadd_ballooned_pages() check the available free memory via\u000asi_mem_available(). GFP_USER is far less limiting memory exhaustion\u000athan the test via si_mem_available().\u000a\u000aThis will avoid dom0 running out of memory due to excessive foreign\u000apage mappings especially on ARM and on x86 in PVH mode, as those don't\u000ahave a pre-ballooned area which can be used for foreign mappings.\u000a\u000aAs the normal ballooning suffers from the same problem don't balloon\u000adown more than si_mem_available() pages in one iteration. At the same\u000atime limit the default maximum number of retries.\u000a\u000aThis is part of XSA-300.\u000a\u000aSigned-off-by: Juergen Gross \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "1548da4859c7a03808541616b723607da88d04ef", "msg" : "xen: let alloc_xenballooned_pages() fail if not enough memory free", "paths" : [ { "editType" : "edit", "file" : "drivers/xen/balloon.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/NCR5380.c" ], "commitId" : "45749b156cbb47bf90ccd45a0f1f7cb257cf3496", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: NCR5380: Always re-enable reselection interrupt\u000a\u000acommit 57f31326518e98ee4cabf9a04efe00ed57c54147 upstream.\u000a\u000aThe reselection interrupt gets disabled during selection and must be\u000are-enabled when hostdata->connected becomes NULL. If it isn't re-enabled a\u000adisconnected command may time-out or the target may wedge the bus while\u000atrying to reselect the host. This can happen after a command is aborted.\u000a\u000aFix this by enabling the reselection interrupt in NCR5380_main() after\u000acalls to NCR5380_select() and NCR5380_information_transfer() return.\u000a\u000aCc: Michael Schmitz \u000aCc: stable@vger.kernel.org # v4.9+\u000aFixes: 8b00c3d5d40d (\"ncr5380: Implement new eh_abort_handler\")\u000aSigned-off-by: Finn Thain \u000aTested-by: Stan Johnson \u000aTested-by: Michael Schmitz \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "45749b156cbb47bf90ccd45a0f1f7cb257cf3496", "msg" : "scsi: NCR5380: Always re-enable reselection interrupt", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/NCR5380.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/NCR5380.c" ], "commitId" : "3e7b99aaf614bd77d72fe648ca2d52f663f170da", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: NCR5380: Handle PDMA failure reliably\u000a\u000acommit f9dfed1c785734b95b08d67600e05d2092508ab0 upstream.\u000a\u000aA PDMA error is handled in the core driver by setting the device's 'borken'\u000aflag and aborting the command. Unfortunately, do_abort() is not\u000adependable. Perform a SCSI bus reset instead, to make sure that the command\u000afails and gets retried.\u000a\u000aCc: Michael Schmitz \u000aCc: stable@vger.kernel.org # v4.20+\u000aFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\u000aSigned-off-by: Finn Thain \u000aTested-by: Stan Johnson \u000aTested-by: Michael Schmitz \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "3e7b99aaf614bd77d72fe648ca2d52f663f170da", "msg" : "scsi: NCR5380: Handle PDMA failure reliably", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/NCR5380.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/NCR5380.h" ], "commitId" : "38fd8cecc0e278cc929fd0cebdd97b935da41285", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Revert \"scsi: ncr5380: Increase register polling limit\"\u000a\u000acommit 25fcf94a2fa89dd3e73e965ebb0b38a2a4f72aa4 upstream.\u000a\u000aThis reverts commit 4822827a69d7cd3bc5a07b7637484ebd2cf88db6.\u000a\u000aThe purpose of that commit was to suppress a timeout warning message which\u000aappeared to be caused by target latency. But suppressing the warning is\u000aundesirable as the warning may indicate a messed up transfer count.\u000a\u000aAnother problem with that commit is that 15 ms is too long to keep\u000ainterrupts disabled as interrupt latency can cause system clock drift and\u000aother problems.\u000a\u000aCc: Michael Schmitz \u000aCc: stable@vger.kernel.org\u000aFixes: 4822827a69d7 (\"scsi: ncr5380: Increase register polling limit\")\u000aSigned-off-by: Finn Thain \u000aTested-by: Stan Johnson \u000aTested-by: Michael Schmitz \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "38fd8cecc0e278cc929fd0cebdd97b935da41285", "msg" : "Revert \"scsi: ncr5380: Increase register polling limit\"", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/NCR5380.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/scsi_lib.c" ], "commitId" : "f263fbd268c749d6de500f69b81dc46da0e049d8", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: core: Fix race on creating sense cache\u000a\u000acommit f9b0530fa02e0c73f31a49ef743e8f44eb8e32cc upstream.\u000a\u000aWhen scsi_init_sense_cache(host) is called concurrently from different\u000ahosts, each code path may find that no cache has been created and\u000aallocate a new one. The lack of locking can lead to potentially\u000aoverriding a cache allocated by a different host.\u000a\u000aFix the issue by moving 'mutex_lock(&scsi_sense_cache_mutex)' before\u000ascsi_select_sense_cache().\u000a\u000aFixes: 0a6ac4ee7c21 (\"scsi: respect unchecked_isa_dma for blk-mq\")\u000aCc: Stable \u000aCc: Christoph Hellwig \u000aCc: Hannes Reinecke \u000aCc: Ewan D. Milne \u000aSigned-off-by: Ming Lei \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "f263fbd268c749d6de500f69b81dc46da0e049d8", "msg" : "scsi: core: Fix race on creating sense cache", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/scsi_lib.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/sd_zbc.c" ], "commitId" : "7b10d7e3b6a0d597cc04734be5ca3213347079f2", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: sd_zbc: Fix compilation warning\u000a\u000acommit 0cdc58580b37a160fac4b884266b8b7cb096f539 upstream.\u000a\u000akbuild test robot gets the following compilation warning using gcc 7.4\u000across compilation for c6x (GCC_VERSION=7.4.0 make.cross ARCH=c6x).\u000a\u000a In file included from include/asm-generic/bug.h:18:0,\u000a from arch/c6x/include/asm/bug.h:12,\u000a from include/linux/bug.h:5,\u000a from include/linux/thread_info.h:12,\u000a from include/asm-generic/current.h:5,\u000a from ./arch/c6x/include/generated/asm/current.h:1,\u000a from include/linux/sched.h:12,\u000a from include/linux/blkdev.h:5,\u000a from drivers//scsi/sd_zbc.c:11:\u000a drivers//scsi/sd_zbc.c: In function 'sd_zbc_read_zones':\u000a>> include/linux/kernel.h:62:48: warning: 'zone_blocks' may be used\u000a uninitialized in this function [-Wmaybe-uninitialized]\u000a #define __round_mask(x, y) ((__typeof__(x))((y)-1))\u000a ^\u000a drivers//scsi/sd_zbc.c:464:6: note: 'zone_blocks' was declared here\u000a u32 zone_blocks;\u000a ^~~~~~~~~~~\u000a\u000aThis is a false-positive report. The variable zone_blocks is always\u000ainitialized in sd_zbc_check_zones() before use. It is not initialized\u000aonly and only if sd_zbc_check_zones() fails.\u000a\u000aAvoid this warning by initializing the zone_blocks variable to 0.\u000a\u000aFixes: 5f832a395859 (\"scsi: sd_zbc: Fix sd_zbc_check_zones() error checks\")\u000aCc: Stable \u000aSigned-off-by: Damien Le Moal \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "7b10d7e3b6a0d597cc04734be5ca3213347079f2", "msg" : "scsi: sd_zbc: Fix compilation warning", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/sd_zbc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/s390/scsi/zfcp_fsf.c" ], "commitId" : "30724adeccf63888ef684c29af09e43501653967", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: zfcp: fix request object use-after-free in send path causing seqno errors\u000a\u000acommit b76becde2b84137faa29bbc9a3b20953b5980e48 upstream.\u000a\u000aWith a recent change to our send path for FSF commands we introduced a\u000apossible use-after-free of request-objects, that might further lead to\u000azfcp crafting bad requests, which the FCP channel correctly complains\u000aabout with an error (FSF_PROT_SEQ_NUMB_ERROR). This error is then handled\u000aby an adapter-wide recovery.\u000a\u000aThe following sequence illustrates the possible use-after-free:\u000a\u000a Send Path:\u000a\u000a int zfcp_fsf_open_port(struct zfcp_erp_action *erp_action)\u000a {\u000a struct zfcp_fsf_req *req;\u000a ...\u000a spin_lock_irq(&qdio->req_q_lock);\u000a // ^^^^^^^^^^^^^^^^\u000a // protects QDIO queue during sending\u000a ...\u000a req = zfcp_fsf_req_create(qdio,\u000a FSF_QTCB_OPEN_PORT_WITH_DID,\u000a SBAL_SFLAGS0_TYPE_READ,\u000a qdio->adapter->pool.erp_req);\u000a // ^^^^^^^^^^^^^^^^^^^\u000a // allocation of the request-object\u000a ...\u000a retval = zfcp_fsf_req_send(req);\u000a ...\u000a spin_unlock_irq(&qdio->req_q_lock);\u000a return retval;\u000a }\u000a\u000a static int zfcp_fsf_req_send(struct zfcp_fsf_req *req)\u000a {\u000a struct zfcp_adapter *adapter = req->adapter;\u000a struct zfcp_qdio *qdio = adapter->qdio;\u000a ...\u000a zfcp_reqlist_add(adapter->req_list, req);\u000a // ^^^^^^^^^^^^^^^^\u000a // add request to our driver-internal hash-table for tracking\u000a // (protected by separate lock req_list->lock)\u000a ...\u000a if (zfcp_qdio_send(qdio, &req->qdio_req)) {\u000a // ^^^^^^^^^^^^^^\u000a // hand-off the request to FCP channel;\u000a // the request can complete at any point now\u000a ...\u000a }\u000a\u000a /* Don't increase for unsolicited status */\u000a if (!zfcp_fsf_req_is_status_read_buffer(req))\u000a // ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\u000a // possible use-after-free\u000a adapter->fsf_req_seq_no++;\u000a // ^^^^^^^^^^^^^^^^\u000a // because of the use-after-free we might\u000a // miss this accounting, and as follow-up\u000a // this results in the FCP channel error\u000a // FSF_PROT_SEQ_NUMB_ERROR\u000a adapter->req_no++;\u000a\u000a return 0;\u000a }\u000a\u000a static inline bool\u000a zfcp_fsf_req_is_status_read_buffer(struct zfcp_fsf_req *req)\u000a {\u000a return req->qtcb == NULL;\u000a // ^^^^^^^^^\u000a // possible use-after-free\u000a }\u000a\u000a Response Path:\u000a\u000a void zfcp_fsf_reqid_check(struct zfcp_qdio *qdio, int sbal_idx)\u000a {\u000a ...\u000a struct zfcp_fsf_req *fsf_req;\u000a ...\u000a for (idx = 0; idx < QDIO_MAX_ELEMENTS_PER_BUFFER; idx++) {\u000a ...\u000a fsf_req = zfcp_reqlist_find_rm(adapter->req_list,\u000a req_id);\u000a // ^^^^^^^^^^^^^^^^^^^^\u000a // remove request from our driver-internal\u000a // hash-table (lock req_list->lock)\u000a ...\u000a zfcp_fsf_req_complete(fsf_req);\u000a }\u000a }\u000a\u000a static void zfcp_fsf_req_complete(struct zfcp_fsf_req *req)\u000a {\u000a ...\u000a if (likely(req->status & ZFCP_STATUS_FSFREQ_CLEANUP))\u000a zfcp_fsf_req_free(req);\u000a // ^^^^^^^^^^^^^^^^^\u000a // free memory for request-object\u000a else\u000a complete(&req->completion);\u000a // ^^^^^^^^\u000a // completion notification for code-paths that wait\u000a // synchronous for the completion of the request; in\u000a // those the memory is freed separately\u000a }\u000a\u000aThe result of the use-after-free only affects the send path, and can not\u000alead to any data corruption. In case we miss the sequence-number\u000aaccounting, because the memory was already re-purposed, the next FSF\u000acommand will fail with said FCP channel error, and we will recover the\u000awhole adapter. This causes no additional errors, but it slows down\u000atraffic. There is a slight chance of the same thing happen again\u000arecursively after the adapter recovery, but so far this has not been seen.\u000a\u000aThis was seen under z/VM, where the send path might run on a virtual CPU\u000athat gets scheduled away by z/VM, while the return path might still run,\u000aand so create the necessary timing. Running with KASAN can also slow down\u000athe kernel sufficiently to run into this user-after-free, and then see the\u000areport by KASAN.\u000a\u000aTo fix this, simply pull the test for the sequence-number accounting in\u000afront of the hand-off to the FCP channel (this information doesn't change\u000aduring hand-off), but leave the sequence-number accounting itself where it\u000ais.\u000a\u000aTo make future regressions of the same kind less likely, add comments to\u000aall closely related code-paths.\u000a\u000aSigned-off-by: Benjamin Block \u000aFixes: f9eca0227600 (\"scsi: zfcp: drop duplicate fsf_command from zfcp_fsf_req which is also in QTCB header\")\u000aCc: #5.0+\u000aReviewed-by: Steffen Maier \u000aReviewed-by: Jens Remus \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "30724adeccf63888ef684c29af09e43501653967", "msg" : "scsi: zfcp: fix request object use-after-free in send path causing seqno errors", "paths" : [ { "editType" : "edit", "file" : "drivers/s390/scsi/zfcp_fsf.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/s390/scsi/zfcp_fsf.c" ], "commitId" : "3f0548a607d3c742356952a2445ccbbb8cf09fe3", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: zfcp: fix request object use-after-free in send path causing wrong traces\u000a\u000acommit 106d45f350c7cac876844dc685845cba4ffdb70b upstream.\u000a\u000aWhen tracing instances where we open and close WKA ports, we also pass the\u000arequest-ID of the respective FSF command.\u000a\u000aBut after successfully sending the FSF command we must not use the\u000arequest-object anymore, as this might result in an use-after-free (see\u000a\"zfcp: fix request object use-after-free in send path causing seqno\u000aerrors\" ).\u000a\u000aTo fix this add a new variable that caches the request-ID before sending\u000athe request. This won't change during the hand-off to the FCP channel,\u000aand so it's safe to trace this cached request-ID later, instead of using\u000athe request object.\u000a\u000aSigned-off-by: Benjamin Block \u000aFixes: d27a7cb91960 (\"zfcp: trace on request for open and close of WKA port\")\u000aCc: #2.6.38+\u000aReviewed-by: Steffen Maier \u000aReviewed-by: Jens Remus \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "3f0548a607d3c742356952a2445ccbbb8cf09fe3", "msg" : "scsi: zfcp: fix request object use-after-free in send path causing wrong traces", "paths" : [ { "editType" : "edit", "file" : "drivers/s390/scsi/zfcp_fsf.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/megaraid/megaraid_sas_base.c" ], "commitId" : "7c266d7af6a99d450282e39c02e7f4d22bbd7713", "timestamp" : 1564125172000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: megaraid_sas: Fix calculation of target ID\u000a\u000acommit c8f96df5b8e633056b7ebf5d52a9d6fb1b156ce3 upstream.\u000a\u000aIn megasas_get_target_prop(), driver is incorrectly calculating the target\u000aID for devices with channel 1 and 3. Due to this, firmware will either\u000afail the command (if there is no device with the target id sent from\u000adriver) or could return the properties for a target which was not\u000aintended. Devices could end up with the wrong queue depth due to this.\u000a\u000aFix target id calculation for channel 1 and 3.\u000a\u000aFixes: 96188a89cc6d (\"scsi: megaraid_sas: NVME interface target prop added\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Shivasharan S \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:52 +0200", "id" : "7c266d7af6a99d450282e39c02e7f4d22bbd7713", "msg" : "scsi: megaraid_sas: Fix calculation of target ID", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/megaraid/megaraid_sas_base.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/mac_scsi.c" ], "commitId" : "c8013794f2113741ab32dd2f20c37aade0a6f3fa", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: mac_scsi: Increase PIO/PDMA transfer length threshold\u000a\u000acommit 7398cee4c3e6aea1ba07a6449e5533ecd0b92cdd upstream.\u000a\u000aSome targets introduce delays when handshaking the response to certain\u000acommands. For example, a disk may send a 96-byte response to an INQUIRY\u000acommand (or a 24-byte response to a MODE SENSE command) too slowly.\u000a\u000aApparently the first 12 or 14 bytes are handshaked okay but then the system\u000abus error timeout is reached while transferring the next word.\u000a\u000aSince the scsi bus phase hasn't changed, the driver then sets the target\u000aborken flag to prevent further PDMA transfers. The driver also logs the\u000awarning, \"switching to slow handshake\".\u000a\u000aRaise the PDMA threshold to 512 bytes so that PIO transfers will be used\u000afor these commands. This default is sufficiently low that PDMA will still\u000abe used for READ and WRITE commands.\u000a\u000aThe existing threshold (16 bytes) was chosen more or less at random.\u000aHowever, best performance requires the threshold to be as low as possible.\u000aThose systems that don't need the PIO workaround at all may benefit from\u000amac_scsi.setup_use_pdma=1\u000a\u000aCc: Michael Schmitz \u000aCc: stable@vger.kernel.org # v4.14+\u000aFixes: 3a0f64bfa907 (\"mac_scsi: Fix pseudo DMA implementation\")\u000aSigned-off-by: Finn Thain \u000aTested-by: Stan Johnson \u000aTested-by: Michael Schmitz \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "c8013794f2113741ab32dd2f20c37aade0a6f3fa", "msg" : "scsi: mac_scsi: Increase PIO/PDMA transfer length threshold", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/mac_scsi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/mac_scsi.c" ], "commitId" : "dba955f28ae68e8cbf22cf699bc26c7714fd973e", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "scsi: mac_scsi: Fix pseudo DMA implementation, take 2\u000a\u000acommit 78ff751f8e6a9446e9fb26b2bff0b8d3f8974cbd upstream.\u000a\u000aA system bus error during a PDMA transfer can mess up the calculation of\u000athe transfer residual (the PDMA handshaking hardware lacks a byte\u000acounter). This results in data corruption.\u000a\u000aThe algorithm in this patch anticipates a bus error by starting each\u000atransfer with a MOVE.B instruction. If a bus error is caught the transfer\u000awill be retried. If a bus error is caught later in the transfer (for a\u000aMOVE.W instruction) the transfer gets failed and subsequent requests for\u000athat target will use PIO instead of PDMA.\u000a\u000aThis avoids the \"!REQ and !ACK\" error so the severity level of that message\u000ais reduced to KERN_DEBUG.\u000a\u000aCc: Michael Schmitz \u000aCc: Geert Uytterhoeven \u000aCc: stable@vger.kernel.org # v4.14+\u000aFixes: 3a0f64bfa907 (\"mac_scsi: Fix pseudo DMA implementation\")\u000aSigned-off-by: Finn Thain \u000aReported-by: Chris Jones \u000aTested-by: Stan Johnson \u000aTested-by: Michael Schmitz \u000aSigned-off-by: Martin K. Petersen \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "dba955f28ae68e8cbf22cf699bc26c7714fd973e", "msg" : "scsi: mac_scsi: Fix pseudo DMA implementation, take 2", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/mac_scsi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/ghash-generic.c" ], "commitId" : "f80432bff0bb917909b90198c51516369df339b7", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: ghash - fix unaligned memory access in ghash_setkey()\u000a\u000acommit 5c6bc4dfa515738149998bb0db2481a4fdead979 upstream.\u000a\u000aChanging ghash_mod_init() to be subsys_initcall made it start running\u000abefore the alignment fault handler has been installed on ARM. In kernel\u000abuilds where the keys in the ghash test vectors happened to be\u000amisaligned in the kernel image, this exposed the longstanding bug that\u000aghash_setkey() is incorrectly casting the key buffer (which can have any\u000aalignment) to be128 for passing to gf128mul_init_4k_lle().\u000a\u000aFix this by memcpy()ing the key to a temporary buffer.\u000a\u000aDon't fix it by setting an alignmask on the algorithm instead because\u000athat would unnecessarily force alignment of the data too.\u000a\u000aFixes: 2cdc6899a88e (\"crypto: ghash - Add GHASH digest algorithm for GCM\")\u000aReported-by: Peter Robinson \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Eric Biggers \u000aTested-by: Peter Robinson \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "f80432bff0bb917909b90198c51516369df339b7", "msg" : "crypto: ghash - fix unaligned memory access in ghash_setkey()", "paths" : [ { "editType" : "edit", "file" : "crypto/ghash-generic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/caam/caamalg.c" ], "commitId" : "f976273ae5ba05640893560901464cbfa08dfaa0", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: caam - limit output IV to CBC to work around CTR mode DMA issue\u000a\u000acommit ed527b13d800dd515a9e6c582f0a73eca65b2e1b upstream.\u000a\u000aThe CAAM driver currently violates an undocumented and slightly\u000acontroversial requirement imposed by the crypto stack that a buffer\u000areferred to by the request structure via its virtual address may not\u000abe modified while any scatterlists passed via the same request\u000astructure are mapped for inbound DMA.\u000a\u000aThis may result in errors like\u000a\u000a alg: aead: decryption failed on test 1 for gcm_base(ctr-aes-caam,ghash-generic): ret=74\u000a alg: aead: Failed to load transform for gcm(aes): -2\u000a\u000aon non-cache coherent systems, due to the fact that the GCM driver\u000apasses an IV buffer by virtual address which shares a cacheline with\u000athe auth_tag buffer passed via a scatterlist, resulting in corruption\u000aof the auth_tag when the IV is updated while the DMA mapping is live.\u000a\u000aSince the IV that is returned to the caller is only valid for CBC mode,\u000aand given that the in-kernel users of CBC (such as CTS) don't trigger the\u000asame issue as the GCM driver, let's just disable the output IV generation\u000afor all modes except CBC for the time being.\u000a\u000aFixes: 854b06f76879 (\"crypto: caam - properly set IV after {en,de}crypt\")\u000aCc: Horia Geanta \u000aCc: Iuliana Prodan \u000aReported-by: Sascha Hauer \u000aCc: \u000aSigned-off-by: Ard Biesheuvel \u000aReviewed-by: Horia Geanta \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "f976273ae5ba05640893560901464cbfa08dfaa0", "msg" : "crypto: caam - limit output IV to CBC to work around CTR mode DMA issue", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/caam/caamalg.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/ccp/ccp-dev.h", "drivers/crypto/ccp/ccp-dev.c" ], "commitId" : "8ab50be87e91e0fabd2a3d9e2265cb9f8b16169d", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: ccp - Validate the the error value used to index error messages\u000a\u000acommit 52393d617af7b554f03531e6756facf2ea687d2e upstream.\u000a\u000aThe error code read from the queue status register is only 6 bits wide,\u000abut we need to verify its value is within range before indexing the error\u000amessages.\u000a\u000aFixes: 81422badb3907 (\"crypto: ccp - Make syslog errors human-readable\")\u000aCc: \u000aReported-by: Cfir Cohen \u000aSigned-off-by: Gary R Hook \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "8ab50be87e91e0fabd2a3d9e2265cb9f8b16169d", "msg" : "crypto: ccp - Validate the the error value used to index error messages", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/ccp/ccp-dev.c" }, { "editType" : "edit", "file" : "drivers/crypto/ccp/ccp-dev.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/crypto/sha1-ce-glue.c" ], "commitId" : "a14c70b5110fe08667a13084775b976a5c54cff3", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: arm64/sha1-ce - correct digest for empty data in finup\u000a\u000acommit 1d4aaf16defa86d2665ae7db0259d6cb07e2091f upstream.\u000a\u000aThe sha1-ce finup implementation for ARM64 produces wrong digest\u000afor empty input (len=0). Expected: da39a3ee..., result: 67452301...\u000a(initial value of SHA internal state). The error is in sha1_ce_finup:\u000afor empty data `finalize` will be 1, so the code is relying on\u000asha1_ce_transform to make the final round. However, in\u000asha1_base_do_update, the block function will not be called when\u000alen == 0.\u000a\u000aFix it by setting finalize to 0 if data is empty.\u000a\u000aFixes: 07eb54d306f4 (\"crypto: arm64/sha1-ce - move SHA-1 ARMv8 implementation to base layer\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Elena Petrova \u000aReviewed-by: Ard Biesheuvel \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "a14c70b5110fe08667a13084775b976a5c54cff3", "msg" : "crypto: arm64/sha1-ce - correct digest for empty data in finup", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/crypto/sha1-ce-glue.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/crypto/sha2-ce-glue.c" ], "commitId" : "f8f4776c36ff2982389137d261c5a74cee89a81f", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: arm64/sha2-ce - correct digest for empty data in finup\u000a\u000acommit 6bd934de1e393466b319d29c4427598fda096c57 upstream.\u000a\u000aThe sha256-ce finup implementation for ARM64 produces wrong digest\u000afor empty input (len=0). Expected: the actual digest, result: initial\u000avalue of SHA internal state. The error is in sha256_ce_finup:\u000afor empty data `finalize` will be 1, so the code is relying on\u000asha2_ce_transform to make the final round. However, in\u000asha256_base_do_update, the block function will not be called when\u000alen == 0.\u000a\u000aFix it by setting finalize to 0 if data is empty.\u000a\u000aFixes: 03802f6a80b3a (\"crypto: arm64/sha2-ce - move SHA-224/256 ARMv8 implementation to base layer\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Elena Petrova \u000aReviewed-by: Ard Biesheuvel \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "f8f4776c36ff2982389137d261c5a74cee89a81f", "msg" : "crypto: arm64/sha2-ce - correct digest for empty data in finup", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/crypto/sha2-ce-glue.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "crypto/chacha20poly1305.c" ], "commitId" : "2fd5789c672b48e8f8b91405c2afb291835ee4dd", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: chacha20poly1305 - fix atomic sleep when using async algorithm\u000a\u000acommit 7545b6c2087f4ef0287c8c9b7eba6a728c67ff8e upstream.\u000a\u000aClear the CRYPTO_TFM_REQ_MAY_SLEEP flag when the chacha20poly1305\u000aoperation is being continued from an async completion callback, since\u000asleeping may not be allowed in that context.\u000a\u000aThis is basically the same bug that was recently fixed in the xts and\u000alrw templates. But, it's always been broken in chacha20poly1305 too.\u000aThis was found using syzkaller in combination with the updated crypto\u000aself-tests which actually test the MAY_SLEEP flag now.\u000a\u000aReproducer:\u000a\u000a python -c 'import socket; socket.socket(socket.AF_ALG, 5, 0).bind(\u000a \u0009 (\"aead\", \"rfc7539(cryptd(chacha20-generic),poly1305-generic)\"))'\u000a\u000aKernel output:\u000a\u000a BUG: sleeping function called from invalid context at include/crypto/algapi.h:426\u000a in_atomic(): 1, irqs_disabled(): 0, pid: 1001, name: kworker/2:2\u000a [...]\u000a CPU: 2 PID: 1001 Comm: kworker/2:2 Not tainted 5.2.0-rc2 #5\u000a Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-20181126_142135-anatol 04/01/2014\u000a Workqueue: crypto cryptd_queue_worker\u000a Call Trace:\u000a __dump_stack lib/dump_stack.c:77 [inline]\u000a dump_stack+0x4d/0x6a lib/dump_stack.c:113\u000a ___might_sleep kernel/sched/core.c:6138 [inline]\u000a ___might_sleep.cold.19+0x8e/0x9f kernel/sched/core.c:6095\u000a crypto_yield include/crypto/algapi.h:426 [inline]\u000a crypto_hash_walk_done+0xd6/0x100 crypto/ahash.c:113\u000a shash_ahash_update+0x41/0x60 crypto/shash.c:251\u000a shash_async_update+0xd/0x10 crypto/shash.c:260\u000a crypto_ahash_update include/crypto/hash.h:539 [inline]\u000a poly_setkey+0xf6/0x130 crypto/chacha20poly1305.c:337\u000a poly_init+0x51/0x60 crypto/chacha20poly1305.c:364\u000a async_done_continue crypto/chacha20poly1305.c:78 [inline]\u000a poly_genkey_done+0x15/0x30 crypto/chacha20poly1305.c:369\u000a cryptd_skcipher_complete+0x29/0x70 crypto/cryptd.c:279\u000a cryptd_skcipher_decrypt+0xcd/0x110 crypto/cryptd.c:339\u000a cryptd_queue_worker+0x70/0xa0 crypto/cryptd.c:184\u000a process_one_work+0x1ed/0x420 kernel/workqueue.c:2269\u000a worker_thread+0x3e/0x3a0 kernel/workqueue.c:2415\u000a kthread+0x11f/0x140 kernel/kthread.c:255\u000a ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:352\u000a\u000aFixes: 71ebc4d1b27d (\"crypto: chacha20poly1305 - Add a ChaCha20-Poly1305 AEAD construction, RFC7539\")\u000aCc: # v4.2+\u000aCc: Martin Willi \u000aSigned-off-by: Eric Biggers \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "2fd5789c672b48e8f8b91405c2afb291835ee4dd", "msg" : "crypto: chacha20poly1305 - fix atomic sleep when using async algorithm", "paths" : [ { "editType" : "edit", "file" : "crypto/chacha20poly1305.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/amcc/crypto4xx_core.c" ], "commitId" : "86f6ece461b85d41164b8860e55c9810943bec23", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: crypto4xx - fix AES CTR blocksize value\u000a\u000acommit bfa2ba7d9e6b20aca82b99e6842fe18842ae3a0f upstream.\u000a\u000aThis patch fixes a issue with crypto4xx's ctr(aes) that was\u000adiscovered by libcapi's kcapi-enc-test.sh test.\u000a\u000aThe some of the ctr(aes) encryptions test were failing on the\u000anon-power-of-two test:\u000a\u000akcapi-enc - Error: encryption failed with error 0\u000akcapi-enc - Error: decryption failed with error 0\u000a[FAILED: 32-bit - 5.1.0-rc1+] 15 bytes: STDIN / STDOUT enc test (128 bits):\u000aoriginal file (1d100e..cc96184c) and generated file (e3b0c442..1b7852b855)\u000a[FAILED: 32-bit - 5.1.0-rc1+] 15 bytes: STDIN / STDOUT enc test (128 bits)\u000a(openssl generated CT): original file (e3b0..5) and generated file (3..8e)\u000a[PASSED: 32-bit - 5.1.0-rc1+] 15 bytes: STDIN / STDOUT enc test (128 bits)\u000a(openssl generated PT)\u000a[FAILED: 32-bit - 5.1.0-rc1+] 15 bytes: STDIN / STDOUT enc test (password):\u000aoriginal file (1d1..84c) and generated file (e3b..852b855)\u000a\u000aBut the 16, 32, 512, 65536 tests always worked.\u000a\u000aThankfully, this isn't a hidden hardware problem like previously,\u000ainstead this turned out to be a copy and paste issue.\u000a\u000aWith this patch, all the tests are passing with and\u000akcapi-enc-test.sh gives crypto4xx's a clean bill of health:\u000a \"Number of failures: 0\" :).\u000a\u000aCc: stable@vger.kernel.org\u000aFixes: 98e87e3d933b (\"crypto: crypto4xx - add aes-ctr support\")\u000aFixes: f2a13e7cba9e (\"crypto: crypto4xx - enable AES RFC3686, ECB, CFB and OFB offloads\")\u000aSigned-off-by: Christian Lamparter \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "86f6ece461b85d41164b8860e55c9810943bec23", "msg" : "crypto: crypto4xx - fix AES CTR blocksize value", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/amcc/crypto4xx_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/amcc/crypto4xx_core.c" ], "commitId" : "16f0c3e3513ddff68f6956e4eda89b8b60528d52", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: crypto4xx - fix blocksize for cfb and ofb\u000a\u000acommit 70c4997f34b6c6888b3ac157adec49e01d0df2d5 upstream.\u000a\u000aWhile the hardware consider them to be blockciphers, the\u000areference implementation defines them as streamciphers.\u000a\u000aDo the right thing and set the blocksize to 1. This\u000awas found by CONFIG_CRYPTO_MANAGER_EXTRA_TESTS.\u000a\u000aThis fixes the following issues:\u000askcipher: blocksize for ofb-aes-ppc4xx (16) doesn't match generic impl (1)\u000askcipher: blocksize for cfb-aes-ppc4xx (16) doesn't match generic impl (1)\u000a\u000aCc: Eric Biggers \u000aCc: stable@vger.kernel.org\u000aFixes: f2a13e7cba9e (\"crypto: crypto4xx - enable AES RFC3686, ECB, CFB and OFB offloads\")\u000aSigned-off-by: Christian Lamparter \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "16f0c3e3513ddff68f6956e4eda89b8b60528d52", "msg" : "crypto: crypto4xx - fix blocksize for cfb and ofb", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/amcc/crypto4xx_core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/amcc/crypto4xx_core.c", "drivers/crypto/amcc/crypto4xx_core.h", "drivers/crypto/amcc/crypto4xx_alg.c" ], "commitId" : "0a7ac0e88274cb002ac8a47f9cf8e4d8cff23a5f", "timestamp" : 1564125173000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: crypto4xx - block ciphers should only accept complete blocks\u000a\u000acommit 0f7a81374060828280fcfdfbaa162cb559017f9f upstream.\u000a\u000aThe hardware automatically zero pads incomplete block ciphers\u000ablocks without raising any errors. This is a screw-up. This\u000awas noticed by CONFIG_CRYPTO_MANAGER_EXTRA_TESTS tests that\u000asent a incomplete blocks and expect them to fail.\u000a\u000aThis fixes:\u000acbc-aes-ppc4xx encryption unexpectedly succeeded on test vector\u000a\"random: len=2409 klen=32\"; expected_error=-22, cfg=\"random:\u000amay_sleep use_digest src_divs=[96.90%@+2295, 2.34%@+4066,\u000a0.32%@alignmask+12, 0.34%@+4087, 0.9%@alignmask+1787, 0.1%@+3767]\u000aiv_offset=6\"\u000a\u000aecb-aes-ppc4xx encryption unexpectedly succeeded on test vector\u000a\"random: len=1011 klen=32\"; expected_error=-22, cfg=\"random:\u000amay_sleep use_digest src_divs=[100.0%@alignmask+20]\u000adst_divs=[3.12%@+3001, 96.88%@+4070]\"\u000a\u000aCc: Eric Biggers \u000aCc: stable@vger.kernel.org [4.19, 5.0 and 5.1]\u000aSigned-off-by: Christian Lamparter \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:53 +0200", "id" : "0a7ac0e88274cb002ac8a47f9cf8e4d8cff23a5f", "msg" : "crypto: crypto4xx - block ciphers should only accept complete blocks", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/amcc/crypto4xx_core.c" }, { "editType" : "edit", "file" : "drivers/crypto/amcc/crypto4xx_core.h" }, { "editType" : "edit", "file" : "drivers/crypto/amcc/crypto4xx_alg.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/ccp/ccp-ops.c" ], "commitId" : "706393e2e920964a28e14b8a0e5ce1d89fd0aecf", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: ccp - memset structure fields to zero before reuse\u000a\u000acommit 20e833dc36355ed642d00067641a679c618303fa upstream.\u000a\u000aThe AES GCM function reuses an 'op' data structure, which members\u000acontain values that must be cleared for each (re)use.\u000a\u000aThis fix resolves a crypto self-test failure:\u000aalg: aead: gcm-aes-ccp encryption test failed (wrong result) on test vector 2, cfg=\"two even aligned splits\"\u000a\u000aFixes: 36cf515b9bbe (\"crypto: ccp - Enable support for AES GCM on v5 CCPs\")\u000aCc: \u000aSigned-off-by: Gary R Hook \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "706393e2e920964a28e14b8a0e5ce1d89fd0aecf", "msg" : "crypto: ccp - memset structure fields to zero before reuse", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/ccp/ccp-ops.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/ccp/ccp-ops.c" ], "commitId" : "bb6b587e64ac2e067d9b246e3c2ce3d1ddd712b1", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: ccp/gcm - use const time tag comparison.\u000a\u000acommit 538a5a072e6ef04377b180ee9b3ce5bae0a85da4 upstream.\u000a\u000aAvoid leaking GCM tag through timing side channel.\u000a\u000aFixes: 36cf515b9bbe (\"crypto: ccp - Enable support for AES GCM on v5 CCPs\")\u000aCc: # v4.12+\u000aSigned-off-by: Cfir Cohen \u000aAcked-by: Gary R Hook \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "bb6b587e64ac2e067d9b246e3c2ce3d1ddd712b1", "msg" : "crypto: ccp/gcm - use const time tag comparison.", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/ccp/ccp-ops.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/crypto/amcc/crypto4xx_trng.c" ], "commitId" : "54ebe857060c5b0323455bf17f4860c1bcd87c48", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "crypto: crypto4xx - fix a potential double free in ppc4xx_trng_probe\u000a\u000acommit 95566aa75cd6b3b404502c06f66956b5481194b3 upstream.\u000a\u000aThere is a possible double free issue in ppc4xx_trng_probe():\u000a\u000a85:\u0009dev->trng_base = of_iomap(trng, 0);\u000a86:\u0009of_node_put(trng); ---> released here\u000a87:\u0009if (!dev->trng_base)\u000a88:\u0009\u0009goto err_out;\u000a...\u000a110:\u0009ierr_out:\u000a111:\u0009\u0009of_node_put(trng); ---> double released here\u000a...\u000a\u000aThis issue was detected by using the Coccinelle software.\u000aWe fix it by removing the unnecessary of_node_put().\u000a\u000aFixes: 5343e674f32f (\"crypto4xx: integrate ppc4xx-rng into crypto4xx\")\u000aSigned-off-by: Wen Yang \u000aCc: \u000aCc: \"David S. Miller\" \u000aCc: Thomas Gleixner \u000aCc: Greg Kroah-Hartman \u000aCc: Allison Randal \u000aCc: Armijn Hemel \u000aCc: Julia Lawall \u000aCc: linux-crypto@vger.kernel.org\u000aCc: linux-kernel@vger.kernel.org\u000aAcked-by: Julia Lawall \u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "54ebe857060c5b0323455bf17f4860c1bcd87c48", "msg" : "crypto: crypto4xx - fix a potential double free in ppc4xx_trng_probe", "paths" : [ { "editType" : "edit", "file" : "drivers/crypto/amcc/crypto4xx_trng.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/cifs/connect.c" ], "commitId" : "43d753fdd4ec7a186af71642fe49489ad416553b", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cifs: always add credits back for unsolicited PDUs\u000a\u000acommit 3e2725796cbdfe4efc7eb7b27cacaeac2ddad1a5 upstream.\u000a\u000anot just if CONFIG_CIFS_DEBUG2 is enabled.\u000a\u000aSigned-off-by: Ronnie Sahlberg \u000aReviewed-by: Pavel Shilovsky \u000aCC: Stable \u000aSigned-off-by: Steve French \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "43d753fdd4ec7a186af71642fe49489ad416553b", "msg" : "cifs: always add credits back for unsolicited PDUs", "paths" : [ { "editType" : "edit", "file" : "fs/cifs/connect.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/cifs/smb2ops.c", "fs/cifs/smb2inode.c" ], "commitId" : "85324afd88d08447d5e2de1aa924f17f9f157349", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cifs: fix crash in smb2_compound_op()/smb2_set_next_command()\u000a\u000acommit 88a92c913cef09e70b1744a8877d177aa6cb2189 upstream.\u000a\u000aRHBZ: 1722704\u000a\u000aIn low memory situations the various SMB2_*_init() functions can fail\u000ato allocate a request PDU and thus leave the request iovector as NULL.\u000a\u000aIf we don't check the return code for failure we end up calling\u000asmb2_set_next_command() with a NULL iovector causing a crash when it tries\u000ato dereference it.\u000a\u000aCC: Stable \u000aSigned-off-by: Ronnie Sahlberg \u000aSigned-off-by: Steve French \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "85324afd88d08447d5e2de1aa924f17f9f157349", "msg" : "cifs: fix crash in smb2_compound_op()/smb2_set_next_command()", "paths" : [ { "editType" : "edit", "file" : "fs/cifs/smb2ops.c" }, { "editType" : "edit", "file" : "fs/cifs/smb2inode.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/cifs/cifs_fs_sb.h", "fs/cifs/misc.c", "fs/cifs/connect.c" ], "commitId" : "c0fcf57679ec80a83c5b752f1e1e96019c81ba4d", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cifs: Properly handle auto disabling of serverino option\u000a\u000acommit 29fbeb7a908a60a5ae8c50fbe171cb8fdcef1980 upstream.\u000a\u000aFix mount options comparison when serverino option is turned off later\u000ain cifs_autodisable_serverino() and thus avoiding mismatch of new cifs\u000amounts.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Paulo Alcantara (SUSE) \u000aSigned-off-by: Steve French \u000aReviewed-by: Pavel Shilovsky \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "c0fcf57679ec80a83c5b752f1e1e96019c81ba4d", "msg" : "cifs: Properly handle auto disabling of serverino option", "paths" : [ { "editType" : "edit", "file" : "fs/cifs/connect.c" }, { "editType" : "edit", "file" : "fs/cifs/misc.c" }, { "editType" : "edit", "file" : "fs/cifs/cifs_fs_sb.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/cifs/inode.c" ], "commitId" : "be5bc9daadec9ac656d04a8de34a0368607cdff0", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "cifs: flush before set-info if we have writeable handles\u000a\u000acommit aa081859b10c5d8b19f5c525c78883a59d73c2b8 upstream.\u000a\u000aServers can defer destaging any data and updating the mtime until close().\u000aThis means that if we do a setinfo to modify the mtime while other handles\u000aare open for write the server may overwrite our setinfo timestamps when\u000aif flushes the file on close() of the writeable handle.\u000a\u000aTo solve this we add an explicit flush when the mtime is about to\u000abe updated.\u000a\u000aThis fixes \"cp -p\" to preserve mtime when copying a file onto an SMB2 share.\u000a\u000aCC: Stable \u000aSigned-off-by: Ronnie Sahlberg \u000aReviewed-by: Pavel Shilovsky \u000aSigned-off-by: Steve French \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "be5bc9daadec9ac656d04a8de34a0368607cdff0", "msg" : "cifs: flush before set-info if we have writeable handles", "paths" : [ { "editType" : "edit", "file" : "fs/cifs/inode.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/cifs/smb2ops.c" ], "commitId" : "cfaa753a5de42f0263497822d89955c284158a97", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "CIFS: fix deadlock in cached root handling\u000a\u000acommit 7e5a70ad88b1e6f6d9b934b2efb41afff496820f upstream.\u000a\u000aPrevent deadlock between open_shroot() and\u000acifs_mark_open_files_invalid() by releasing the lock before entering\u000aSMB2_open, taking it again after and checking if we still need to use\u000athe result.\u000a\u000aLink: https://lore.kernel.org/linux-cifs/684ed01c-cbca-2716-bc28-b0a59a0f8521@prodrive-technologies.com/T/#u\u000aFixes: 3d4ef9a15343 (\"smb3: fix redundant opens on root\")\u000aSigned-off-by: Aurelien Aptel \u000aReviewed-by: Pavel Shilovsky \u000aSigned-off-by: Steve French \u000aCC: Stable \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "cfaa753a5de42f0263497822d89955c284158a97", "msg" : "CIFS: fix deadlock in cached root handling", "paths" : [ { "editType" : "edit", "file" : "fs/cifs/smb2ops.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/super.c" ], "commitId" : "f1f65afd3fb8afc7a7e4b14c457d3fd608bff327", "timestamp" : 1564125174000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Revert \"bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()\"\u000a\u000acommit 695277f16b3a102fcc22c97fdf2de77c7b19f0b3 upstream.\u000a\u000aThis reverts commit 6147305c73e4511ca1a975b766b97a779d442567.\u000a\u000aAlthough this patch helps the failed bcache device to stop faster when\u000atoo many I/O errors detected on corresponding cached device, setting\u000aCACHE_SET_IO_DISABLE bit to cache set c->flags was not a good idea. This\u000aoperation will disable all I/Os on cache set, which means other attached\u000abcache devices won't work neither.\u000a\u000aWithout this patch, the failed bcache device can also be stopped\u000aeventually if internal I/O accomplished (e.g. writeback). Therefore here\u000aI revert it.\u000a\u000aFixes: 6147305c73e4 (\"bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()\")\u000aReported-by: Yong Li \u000aSigned-off-by: Coly Li \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:54 +0200", "id" : "f1f65afd3fb8afc7a7e4b14c457d3fd608bff327", "msg" : "Revert \"bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()\"", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/super.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/journal.c", "drivers/md/bcache/bcache.h", "drivers/md/bcache/util.h" ], "commitId" : "b6dc61e01a47ae6e534065a973a39e8a7040e8b9", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: Revert \"bcache: fix high CPU occupancy during journal\"\u000a\u000acommit 249a5f6da57c28a903c75d81505d58ec8c10030d upstream.\u000a\u000aThis reverts commit c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0.\u000a\u000aThis patch enlarges a race between normal btree flush code path and\u000aflush_btree_write(), which causes deadlock when journal space is\u000aexhausted. Reverts this patch makes the race window from 128 btree\u000anodes to only 1 btree nodes.\u000a\u000aFixes: c4dc2497d50d (\"bcache: fix high CPU occupancy during journal\")\u000aSigned-off-by: Coly Li \u000aCc: stable@vger.kernel.org\u000aCc: Tang Junhui \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "b6dc61e01a47ae6e534065a973a39e8a7040e8b9", "msg" : "bcache: Revert \"bcache: fix high CPU occupancy during journal\"", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/journal.c" }, { "editType" : "edit", "file" : "drivers/md/bcache/bcache.h" }, { "editType" : "edit", "file" : "drivers/md/bcache/util.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/journal.c" ], "commitId" : "85b1a0ba74eba98ef509aa7a9e45d023558227f9", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: Revert \"bcache: free heap cache_set->flush_btree in bch_journal_free\"\u000a\u000acommit ba82c1ac1667d6efb91a268edb13fc9cdaecec9b upstream.\u000a\u000aThis reverts commit 6268dc2c4703aabfb0b35681be709acf4c2826c6.\u000a\u000aThis patch depends on commit c4dc2497d50d (\"bcache: fix high CPU\u000aoccupancy during journal\") which is reverted in previous patch. So\u000arevert this one too.\u000a\u000aFixes: 6268dc2c4703 (\"bcache: free heap cache_set->flush_btree in bch_journal_free\")\u000aSigned-off-by: Coly Li \u000aCc: stable@vger.kernel.org\u000aCc: Shenghui Wang \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "85b1a0ba74eba98ef509aa7a9e45d023558227f9", "msg" : "bcache: Revert \"bcache: free heap cache_set->flush_btree in bch_journal_free\"", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/journal.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/io.c" ], "commitId" : "4fd16a855cf5ac464a446ddafcbedecf8734a453", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: ignore read-ahead request failure on backing device\u000a\u000acommit 578df99b1b0531d19af956530fe4da63d01a1604 upstream.\u000a\u000aWhen md raid device (e.g. raid456) is used as backing device, read-ahead\u000arequests on a degrading and recovering md raid device might be failured\u000aimmediately by md raid code, but indeed this md raid array can still be\u000aread or write for normal I/O requests. Therefore such failed read-ahead\u000arequest are not real hardware failure. Further more, after degrading and\u000arecovering accomplished, read-ahead requests will be handled by md raid\u000aarray again.\u000a\u000aFor such condition, I/O failures of read-ahead requests don't indicate\u000areal health status (because normal I/O still be served), they should not\u000abe counted into I/O error counter dc->io_errors.\u000a\u000aSince there is no simple way to detect whether the backing divice is a\u000amd raid device, this patch simply ignores I/O failures for read-ahead\u000abios on backing device, to avoid bogus backing device failure on a\u000adegrading md raid array.\u000a\u000aSuggested-and-tested-by: Thorsten Knabe \u000aSigned-off-by: Coly Li \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "4fd16a855cf5ac464a446ddafcbedecf8734a453", "msg" : "bcache: ignore read-ahead request failure on backing device", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/io.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/sysfs.c" ], "commitId" : "f85c665b20a5a9a700c9b0707f7a960a1ea2ae14", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: fix mistaken sysfs entry for io_error counter\u000a\u000acommit 5461999848e0462c14f306a62923d22de820a59c upstream.\u000a\u000aIn bch_cached_dev_files[] from driver/md/bcache/sysfs.c, sysfs_errors is\u000aincorrectly inserted in. The correct entry should be sysfs_io_errors.\u000a\u000aThis patch fixes the problem and now I/O errors of cached device can be\u000aread from /sys/block/bcache/bcache/io_errors.\u000a\u000aFixes: c7b7bd07404c5 (\"bcache: add io_disable to struct cached_dev\")\u000aSigned-off-by: Coly Li \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "f85c665b20a5a9a700c9b0707f7a960a1ea2ae14", "msg" : "bcache: fix mistaken sysfs entry for io_error counter", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/sysfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/bcache/writeback.c" ], "commitId" : "84afbcade8bcdc63b30b563483b215783cbc7204", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bcache: destroy dc->writeback_write_wq if failed to create dc->writeback_thread\u000a\u000acommit f54d801dda14942dbefa00541d10603015b7859c upstream.\u000a\u000aCommit 9baf30972b55 (\"bcache: fix for gc and write-back race\") added a\u000anew work queue dc->writeback_write_wq, but forgot to destroy it in the\u000aerror condition when creating dc->writeback_thread failed.\u000a\u000aThis patch destroys dc->writeback_write_wq if kthread_create() returns\u000aerror pointer to dc->writeback_thread, then a memory leak is avoided.\u000a\u000aFixes: 9baf30972b55 (\"bcache: fix for gc and write-back race\")\u000aSigned-off-by: Coly Li \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "84afbcade8bcdc63b30b563483b215783cbc7204", "msg" : "bcache: destroy dc->writeback_write_wq if failed to create dc->writeback_thread", "paths" : [ { "editType" : "edit", "file" : "drivers/md/bcache/writeback.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/tablet/gtco.c" ], "commitId" : "430755b2d79ceb01290837636ca6ee87eae2c862", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: gtco - bounds check collection indent level\u000a\u000acommit 2a017fd82c5402b3c8df5e3d6e5165d9e6147dc1 upstream.\u000a\u000aThe GTCO tablet input driver configures itself from an HID report sent\u000avia USB during the initial enumeration process. Some debugging messages\u000aare generated during the parsing. A debugging message indentation\u000acounter is not bounds checked, leading to the ability for a specially\u000acrafted HID report to cause '-' and null bytes be written past the end\u000aof the indentation array. As long as the kernel has CONFIG_DYNAMIC_DEBUG\u000aenabled, this code will not be optimized out. This was discovered\u000aduring code review after a previous syzkaller bug was found in this\u000adriver.\u000a\u000aSigned-off-by: Grant Hernandez \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "430755b2d79ceb01290837636ca6ee87eae2c862", "msg" : "Input: gtco - bounds check collection indent level", "paths" : [ { "editType" : "edit", "file" : "drivers/input/tablet/gtco.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/mouse/alps.c" ], "commitId" : "59a976c977fb43c34c3df475b44722e467a7bda1", "timestamp" : 1564125175000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: alps - don't handle ALPS cs19 trackpoint-only device\u000a\u000acommit 7e4935ccc3236751e5fe4bd6846f86e46bb2e427 upstream.\u000a\u000aOn a latest Lenovo laptop, the trackpoint and 3 buttons below it\u000adon't work at all, when we move the trackpoint or press those 3\u000abuttons, the kernel will print out:\u000a\"Rejected trackstick packet from non DualPoint device\"\u000a\u000aThis device is identified as an alps touchpad but the packet has\u000atrackpoint format, so the alps.c drops the packet and prints out\u000athe message above.\u000a\u000aAccording to XiaoXiao's explanation, this device is named cs19 and\u000ais trackpoint-only device, its firmware is only for trackpoint, it\u000ais independent of touchpad and is a device completely different from\u000aDualPoint ones.\u000a\u000aTo drive this device with mininal changes to the existing driver, we\u000ajust let the alps driver not handle this device, then the trackpoint.c\u000awill be the driver of this device if the trackpoint driver is enabled.\u000a(if not, this device will fallback to a bare PS/2 device)\u000a\u000aWith the trackpoint.c, this trackpoint and 3 buttons all work well,\u000athey have all features that the trackpoint should have, like\u000ascrolling-screen, drag-and-drop and frame-selection.\u000a\u000aSigned-off-by: XiaoXiao Liu \u000aSigned-off-by: Hui Wang \u000aReviewed-by: Pali Rohár \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:55 +0200", "id" : "59a976c977fb43c34c3df475b44722e467a7bda1", "msg" : "Input: alps - don't handle ALPS cs19 trackpoint-only device", "paths" : [ { "editType" : "edit", "file" : "drivers/input/mouse/alps.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/mouse/synaptics.c" ], "commitId" : "b972bdd9798f9f5b67255800daee683b94f0f7a1", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: synaptics - whitelist Lenovo T580 SMBus intertouch\u000a\u000acommit 1976d7d200c5a32e72293a2ada36b7b7c9d6dd6e upstream.\u000a\u000aAdds the Lenovo T580 to the SMBus intertouch list for Synaptics\u000atouchpads. I've tested with this for a week now, and it seems a great\u000aimprovement. It's also nice to have the complaint gone from dmesg.\u000a\u000aSigned-off-by: Nick Black \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "b972bdd9798f9f5b67255800daee683b94f0f7a1", "msg" : "Input: synaptics - whitelist Lenovo T580 SMBus intertouch", "paths" : [ { "editType" : "edit", "file" : "drivers/input/mouse/synaptics.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/mouse/alps.c" ], "commitId" : "c4ffc082c88cb6b212f752b84f2e586d3e8ee5d3", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Input: alps - fix a mismatch between a condition check and its comment\u000a\u000acommit 771a081e44a9baa1991ef011cc453ef425591740 upstream.\u000a\u000aIn the function alps_is_cs19_trackpoint(), we check if the param[1] is\u000ain the 0x20~0x2f range, but the code we wrote for this checking is not\u000acorrect:\u000a(param[1] & 0x20) does not mean param[1] is in the range of 0x20~0x2f,\u000ait also means the param[1] is in the range of 0x30~0x3f, 0x60~0x6f...\u000a\u000aNow fix it with a new condition checking ((param[1] & 0xf0) == 0x20).\u000a\u000aFixes: 7e4935ccc323 (\"Input: alps - don't handle ALPS cs19 trackpoint-only device\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Hui Wang \u000aSigned-off-by: Dmitry Torokhov \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "c4ffc082c88cb6b212f752b84f2e586d3e8ee5d3", "msg" : "Input: alps - fix a mismatch between a condition check and its comment", "paths" : [ { "editType" : "edit", "file" : "drivers/input/mouse/alps.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/regulator/s2mps11.c" ], "commitId" : "a10d287f32d1d3fd34ce6c8c3e76ee71d8327f80", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "regulator: s2mps11: Fix ERR_PTR dereference on GPIO lookup failure\u000a\u000acommit 70ca117b02f3b1c8830fe95e4e3dea2937038e11 upstream.\u000a\u000aIf devm_gpiod_get_from_of_node() call returns ERR_PTR, it is assigned\u000ainto an array of GPIO descriptors and used later because such error is\u000anot treated as critical thus it is not propagated back to the probe\u000afunction.\u000a\u000aAll code later expects that such GPIO descriptor is either a NULL or\u000aproper value. This later might lead to dereference of ERR_PTR.\u000a\u000aOnly devices with S2MPS14 flavor are affected (other do not control\u000aregulators with GPIOs).\u000a\u000aFixes: 1c984942f0a4 (\"regulator: s2mps11: Pass descriptor instead of GPIO number\")\u000aCc: \u000aSigned-off-by: Krzysztof Kozlowski \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "a10d287f32d1d3fd34ce6c8c3e76ee71d8327f80", "msg" : "regulator: s2mps11: Fix ERR_PTR dereference on GPIO lookup failure", "paths" : [ { "editType" : "edit", "file" : "drivers/regulator/s2mps11.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/regulator/s2mps11.c" ], "commitId" : "03a9bb6813a9335632c61cf2e21ced7aef01bb36", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "regulator: s2mps11: Fix buck7 and buck8 wrong voltages\u000a\u000acommit 16da0eb5ab6ef2dd1d33431199126e63db9997cc upstream.\u000a\u000aOn S2MPS11 device, the buck7 and buck8 regulator voltages start at 750\u000amV, not 600 mV. Using wrong minimal value caused shifting of these\u000aregulator values by 150 mV (e.g. buck7 usually configured to v1.35 V was\u000areported as 1.2 V).\u000a\u000aOn most of the boards these regulators are left in default state so this\u000awas only affecting reported voltage. However if any driver wanted to\u000achange them, then effectively it would set voltage 150 mV higher than\u000aintended.\u000a\u000aCc: \u000aFixes: cb74685ecb39 (\"regulator: s2mps11: Add samsung s2mps11 regulator driver\")\u000aSigned-off-by: Krzysztof Kozlowski \u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "03a9bb6813a9335632c61cf2e21ced7aef01bb36", "msg" : "regulator: s2mps11: Fix buck7 and buck8 wrong voltages", "paths" : [ { "editType" : "edit", "file" : "drivers/regulator/s2mps11.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi" ], "commitId" : "6451bbd4e35b1c3f2b72a5f128c622d7d5e50635", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: tegra: Update Jetson TX1 GPU regulator timings\u000a\u000acommit ece6031ece2dd64d63708cfe1088016cee5b10c0 upstream.\u000a\u000aThe GPU regulator enable ramp delay for Jetson TX1 is set to 1ms which\u000anot sufficient because the enable ramp delay has been measured to be\u000agreater than 1ms. Furthermore, the downstream kernels released by NVIDIA\u000afor Jetson TX1 are using a enable ramp delay 2ms and a settling delay of\u000a160us. Update the GPU regulator enable ramp delay for Jetson TX1 to be\u000a2ms and add a settling delay of 160us.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jon Hunter \u000aFixes: 5e6b9a89afce (\"arm64: tegra: Add VDD_GPU regulator to Jetson TX1\")\u000aSigned-off-by: Thierry Reding \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "6451bbd4e35b1c3f2b72a5f128c622d7d5e50635", "msg" : "arm64: tegra: Update Jetson TX1 GPU regulator timings", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/iwl-csr.h", "drivers/net/wireless/intel/iwlwifi/pcie/trans.c" ], "commitId" : "b24823db268ee297e2fe3a06d3534c6ff59dc545", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: add support for hr1 RF ID\u000a\u000acommit 498d3eb5bfbb2e05e40005152976a7b9eadfb59c upstream.\u000a\u000aThe 22000 series FW that was meant to be used with hr is\u000aalso the FW that is used for hr1 and has a different RF ID.\u000aAdd support to load the hr FW when hr1 RF ID is detected.\u000a\u000aCc: stable@vger.kernel.org # 5.1+\u000aSigned-off-by: Oren Givon \u000aSigned-off-by: Luciano Coelho \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "b24823db268ee297e2fe3a06d3534c6ff59dc545", "msg" : "iwlwifi: add support for hr1 RF ID", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/iwl-csr.h" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/trans.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/pcie/rx.c" ], "commitId" : "fce4419df4c683b2f7e864e0278b40d2d1e13600", "timestamp" : 1564125176000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: pcie: don't service an interrupt that was masked\u000a\u000acommit 3b57a10ca14c619707398dc58fe5ece18c95b20b upstream.\u000a\u000aSometimes the register status can include interrupts that\u000awere masked. We can, for example, get the RF-Kill bit set\u000ain the interrupt status register although this interrupt\u000awas masked. Then if we get the ALIVE interrupt (for example)\u000athat was not masked, we need to *not* service the RF-Kill\u000ainterrupt.\u000aFix this in the MSI-X interrupt handler.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Emmanuel Grumbach \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:56 +0200", "id" : "fce4419df4c683b2f7e864e0278b40d2d1e13600", "msg" : "iwlwifi: pcie: don't service an interrupt that was masked", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/rx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/pcie/rx.c" ], "commitId" : "cbee0a113f7eda260a62737b31bddddf15e2ea41", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: pcie: fix ALIVE interrupt handling for gen2 devices w/o MSI-X\u000a\u000acommit ec46ae30245ecb41d73f8254613db07c653fb498 upstream.\u000a\u000aWe added code to restock the buffer upon ALIVE interrupt\u000awhen MSI-X is disabled. This was added as part of the context\u000ainfo code. This code was added only if the ISR debug level\u000ais set which is very unlikely to be related.\u000aMove this code to run even when the ISR debug level is not\u000aset.\u000a\u000aNote that gen2 devices work with MSI-X in most cases so that\u000athis path is seldom used.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Emmanuel Grumbach \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "cbee0a113f7eda260a62737b31bddddf15e2ea41", "msg" : "iwlwifi: pcie: fix ALIVE interrupt handling for gen2 devices w/o MSI-X", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/rx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/fw/smem.c" ], "commitId" : "cfe692268ad1b6dabc6502d2c1f5708df5d5c480", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: don't WARN when calling iwl_get_shared_mem_conf with RF-Kill\u000a\u000acommit 0d53cfd0cca3c729a089c39eef0e7d8ae7662974 upstream.\u000a\u000aiwl_mvm_send_cmd returns 0 when the command won't be sent\u000abecause RF-Kill is asserted. Do the same when we call\u000aiwl_get_shared_mem_conf since it is not sent through\u000aiwl_mvm_send_cmd but directly calls the transport layer.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Emmanuel Grumbach \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "cfe692268ad1b6dabc6502d2c1f5708df5d5c480", "msg" : "iwlwifi: don't WARN when calling iwl_get_shared_mem_conf with RF-Kill", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/fw/smem.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/pcie/internal.h", "drivers/net/wireless/intel/iwlwifi/pcie/trans-gen2.c", "drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info-gen3.c", "drivers/net/wireless/intel/iwlwifi/pcie/rx.c", "drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info.c" ], "commitId" : "d307dbc49e4c57f654e3defcc6c4f356d5b40320", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: fix RF-Kill interrupt while FW load for gen2 devices\u000a\u000acommit ed3e4c6d3cd8f093a3636cb05492429fe2af228d upstream.\u000a\u000aNewest devices have a new firmware load mechanism. This\u000amechanism is called the context info. It means that the\u000adriver doesn't need to load the sections of the firmware.\u000aThe driver rather prepares a place in DRAM, with pointers\u000ato the relevant sections of the firmware, and the firmware\u000aloads itself.\u000aAt the end of the process, the firmware sends the ALIVE\u000ainterrupt. This is different from the previous scheme in\u000awhich the driver expected the FH_TX interrupt after each\u000asection being transferred over the DMA.\u000a\u000aIn order to support this new flow, we enabled all the\u000ainterrupts. This broke the assumption that we have in the\u000acode that the RF-Kill interrupt can't interrupt the firmware\u000aload flow.\u000a\u000aChange the context info flow to enable only the ALIVE\u000ainterrupt, and re-enable all the other interrupts only\u000aafter the firmware is alive. Then, we won't see the RF-Kill\u000ainterrupt until then. Getting the RF-Kill interrupt while\u000aloading the firmware made us kill the firmware while it is\u000aloading and we ended up dumping garbage instead of the firmware\u000astate.\u000a\u000aRe-enable the ALIVE | RX interrupts from the ISR when we\u000aget the ALIVE interrupt to be able to get the RX interrupt\u000athat comes immediately afterwards for the ALIVE\u000anotification. This is needed for non MSI-X only.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Emmanuel Grumbach \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "d307dbc49e4c57f654e3defcc6c4f356d5b40320", "msg" : "iwlwifi: fix RF-Kill interrupt while FW load for gen2 devices", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/trans-gen2.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/rx.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info-gen3.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/pcie/internal.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/mvm/mvm.h", "drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c" ], "commitId" : "5de3b81feaf9e393c18593a3ed321046e0f690fb", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: mvm: delay GTK setting in FW in AP mode\u000a\u000acommit c56e00a3feaee2b46b7d33875fb7f52efd30241f upstream.\u000a\u000aIn AP (and IBSS) mode, we can only set GTKs to firmware after we have\u000asent down the multicast station, but this we can only do after we've\u000aenabled beaconing, etc.\u000a\u000aHowever, during rfkill exit, hostapd will configure the keys before\u000astarting the AP, and cfg80211/mac80211 accept it happily.\u000a\u000aOn earlier devices, this didn't bother us as GTK TX wasn't really\u000ahandled in firmware, we just put the key material into the TX cmd\u000aand thus it only mattered when we actually transmitted a frame.\u000a\u000aOn newer devices, however, the firmware needs to track all of this\u000aand that doesn't work if we add the key before the (multicast) sta\u000ait belongs to.\u000a\u000aTo fix this, keep a list of keys to add during AP enable, and call\u000athe function there.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Johannes Berg \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "5de3b81feaf9e393c18593a3ed321046e0f690fb", "msg" : "iwlwifi: mvm: delay GTK setting in FW in AP mode", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c" }, { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/mvm.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/intel/iwlwifi/mvm/fw.c" ], "commitId" : "068e5e7ea6268a3705157916452420b5bc9961a5", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "iwlwifi: mvm: clear rfkill_safe_init_done when we start the firmware\u000a\u000acommit 940225628652b340b2bfe99f42f3d2db9fd9ce6c upstream.\u000a\u000aOtherwise it'll stay set forever which is clearly buggy.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Emmanuel Grumbach \u000aSigned-off-by: Luca Coelho \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "068e5e7ea6268a3705157916452420b5bc9961a5", "msg" : "iwlwifi: mvm: clear rfkill_safe_init_done when we start the firmware", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/intel/iwlwifi/mvm/fw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/opp/core.c" ], "commitId" : "44c92c0c7407b150f50af0c063ddb54c91df3c84", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "opp: Don't use IS_ERR on invalid supplies\u000a\u000acommit 560d1bcad715c215e7ffe5d7cffe045974b623d0 upstream.\u000a\u000a_set_opp_custom() receives a set of OPP supplies as its arguments and\u000athe caller of it passes NULL when the supplies are not valid. But\u000a_set_opp_custom(), by mistake, checks for error by performing\u000aIS_ERR(old_supply) on it which will always evaluate to false.\u000a\u000aThe problem was spotted during of testing of upcoming update for the\u000aNVIDIA Tegra CPUFreq driver.\u000a\u000aCc: stable \u000aFixes: 7e535993fa4f (\"OPP: Separate out custom OPP handler specific code\")\u000aReported-by: Marc Dietrich \u000aSigned-off-by: Dmitry Osipenko \u000a[ Viresh: Massaged changelog ]\u000aSigned-off-by: Viresh Kumar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "44c92c0c7407b150f50af0c063ddb54c91df3c84", "msg" : "opp: Don't use IS_ERR on invalid supplies", "paths" : [ { "editType" : "edit", "file" : "drivers/opp/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/kernel/entry.S", "arch/arm64/kernel/irq.c", "kernel/irq/irqdesc.c", "drivers/irqchip/irq-gic-v3.c" ], "commitId" : "5c48d5d4e5f9ad8cceca84a1a2445a0e46eba47c", "timestamp" : 1564125177000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: Fix interrupt tracing in the presence of NMIs\u000a\u000acommit 17ce302f3117e9518395847a3120c8a108b587b8 upstream.\u000a\u000aIn the presence of any form of instrumentation, nmi_enter() should be\u000adone before calling any traceable code and any instrumentation code.\u000a\u000aCurrently, nmi_enter() is done in handle_domain_nmi(), which is much\u000atoo late as instrumentation code might get called before. Move the\u000anmi_enter/exit() calls to the arch IRQ vector handler.\u000a\u000aOn arm64, it is not possible to know if the IRQ vector handler was\u000acalled because of an NMI before acknowledging the interrupt. However, It\u000ais possible to know whether normal interrupts could be taken in the\u000ainterrupted context (i.e. if taking an NMI in that context could\u000aintroduce a potential race condition).\u000a\u000aWhen interrupting a context with IRQs disabled, call nmi_enter() as soon\u000aas possible. In contexts with IRQs enabled, defer this to the interrupt\u000acontroller, which is in a better position to know if an interrupt taken\u000ais an NMI.\u000a\u000aFixes: bc3c03ccb464 (\"arm64: Enable the support of pseudo-NMIs\")\u000aCc: # 5.1.x-\u000aCc: Will Deacon \u000aCc: Thomas Gleixner \u000aCc: Jason Cooper \u000aCc: Mark Rutland \u000aReviewed-by: Marc Zyngier \u000aSigned-off-by: Julien Thierry \u000aSigned-off-by: Catalin Marinas \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:57 +0200", "id" : "5c48d5d4e5f9ad8cceca84a1a2445a0e46eba47c", "msg" : "arm64: Fix interrupt tracing in the presence of NMIs", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/kernel/irq.c" }, { "editType" : "edit", "file" : "kernel/irq/irqdesc.c" }, { "editType" : "edit", "file" : "arch/arm64/kernel/entry.S" }, { "editType" : "edit", "file" : "drivers/irqchip/irq-gic-v3.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/nfs/inode.c", "fs/nfs/nfs4file.c" ], "commitId" : "b3dd02f968711844b132a1db7e46df8a2a660489", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "NFSv4: Handle the special Linux file open access mode\u000a\u000acommit 44942b4e457beda00981f616402a1a791e8c616e upstream.\u000a\u000aAccording to the open() manpage, Linux reserves the access mode 3\u000ato mean \"check for read and write permission on the file and return\u000aa file descriptor that can't be used for reading or writing.\"\u000a\u000aCurrently, the NFSv4 code will ask the server to open the file,\u000aand will use an incorrect share access mode of 0. Since it has\u000aan incorrect share access mode, the client later forgets to send\u000aa corresponding close, meaning it can leak stateids on the server.\u000a\u000aFixes: ce4ef7c0a8a05 (\"NFS: Split out NFS v4 file operations\")\u000aCc: stable@vger.kernel.org # 3.6+\u000aSigned-off-by: Trond Myklebust \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "b3dd02f968711844b132a1db7e46df8a2a660489", "msg" : "NFSv4: Handle the special Linux file open access mode", "paths" : [ { "editType" : "edit", "file" : "fs/nfs/inode.c" }, { "editType" : "edit", "file" : "fs/nfs/nfs4file.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/nfs/dir.c", "fs/nfs/internal.h" ], "commitId" : "3536b79ba75ba44b9ac1a9f1634f2e833bbb735c", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Revert \"NFS: readdirplus optimization by cache mechanism\" (memleak)\u000a\u000acommit db531db951f950b86d274cc8ed7b21b9e2240036 upstream.\u000a\u000aThis reverts commit be4c2d4723a4a637f0d1b4f7c66447141a4b3564.\u000a\u000aThat commit caused a severe memory leak in nfs_readdir_make_qstr().\u000a\u000aWhen listing a directory with more than 100 files (this is how many\u000astruct nfs_cache_array_entry elements fit in one 4kB page), all\u000aallocated file name strings past those 100 leak.\u000a\u000aThe root of the leakage is that those string pointers are managed in\u000apages which are never linked into the page cache.\u000a\u000afs/nfs/dir.c puts pages into the page cache by calling\u000aread_cache_page(); the callback function nfs_readdir_filler() will\u000athen fill the given page struct which was passed to it, which is\u000aalready linked in the page cache (by do_read_cache_page() calling\u000aadd_to_page_cache_lru()).\u000a\u000aCommit be4c2d4723a4 added another (local) array of allocated pages, to\u000abe filled with more data, instead of discarding excess items received\u000afrom the NFS server. Those additional pages can be used by the next\u000anfs_readdir_filler() call (from within the same nfs_readdir() call).\u000a\u000aThe leak happens when some of those additional pages are never used\u000a(copied to the page cache using copy_highpage()). The pages will be\u000afreed by nfs_readdir_free_pages(), but their contents will not. The\u000acommit did not invoke nfs_readdir_clear_array() (and doing so would\u000ahave been dangerous, because it did not track which of those pages\u000awere already copied to the page cache, risking double free bugs).\u000a\u000aHow to reproduce the leak:\u000a\u000a- Use a kernel with CONFIG_SLUB_DEBUG_ON.\u000a\u000a- Create a directory on a NFS mount with more than 100 files with\u000a names long enough to use the \"kmalloc-32\" slab (so we can easily\u000a look up the allocation counts):\u000a\u000a for i in `seq 110`; do touch ${i}_0123456789abcdef; done\u000a\u000a- Drop all caches:\u000a\u000a echo 3 >/proc/sys/vm/drop_caches\u000a\u000a- Check the allocation counter:\u000a\u000a grep nfs_readdir /sys/kernel/slab/kmalloc-32/alloc_calls\u000a 30564391 nfs_readdir_add_to_array+0x73/0xd0 age=534558/4791307/6540952 pid=370-1048386 cpus=0-47 nodes=0-1\u000a\u000a- Request a directory listing and check the allocation counters again:\u000a\u000a ls\u000a [...]\u000a grep nfs_readdir /sys/kernel/slab/kmalloc-32/alloc_calls\u000a 30564511 nfs_readdir_add_to_array+0x73/0xd0 age=207/4792999/6542663 pid=370-1048386 cpus=0-47 nodes=0-1\u000a\u000aThere are now 120 new allocations.\u000a\u000a- Drop all caches and check the counters again:\u000a\u000a echo 3 >/proc/sys/vm/drop_caches\u000a grep nfs_readdir /sys/kernel/slab/kmalloc-32/alloc_calls\u000a 30564401 nfs_readdir_add_to_array+0x73/0xd0 age=735/4793524/6543176 pid=370-1048386 cpus=0-47 nodes=0-1\u000a\u000a110 allocations are gone, but 10 have leaked and will never be freed.\u000a\u000aUnhelpfully, those allocations are explicitly excluded from KMEMLEAK,\u000athat's why my initial attempts with KMEMLEAK were not successful:\u000a\u000a\u0009/*\u000a\u0009 * Avoid a kmemleak false positive. The pointer to the name is stored\u000a\u0009 * in a page cache page which kmemleak does not scan.\u000a\u0009 */\u000a\u0009kmemleak_not_leak(string->name);\u000a\u000aIt would be possible to solve this bug without reverting the whole\u000acommit:\u000a\u000a- keep track of which pages were not used, and call\u000a nfs_readdir_clear_array() on them, or\u000a- manually link those pages into the page cache\u000a\u000aBut for now I have decided to just revert the commit, because the real\u000afix would require complex considerations, risking more dangerous\u000a(crash) bugs, which may seem unsuitable for the stable branches.\u000a\u000aSigned-off-by: Max Kellermann \u000aCc: stable@vger.kernel.org # v5.1+\u000aSigned-off-by: Trond Myklebust \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "3536b79ba75ba44b9ac1a9f1634f2e833bbb735c", "msg" : "Revert \"NFS: readdirplus optimization by cache mechanism\" (memleak)", "paths" : [ { "editType" : "edit", "file" : "fs/nfs/dir.c" }, { "editType" : "edit", "file" : "fs/nfs/internal.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/nfs/flexfilelayout/flexfilelayoutdev.c" ], "commitId" : "119c5aa1a3b5ce535880a9cb6ee96f957da0d431", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pnfs/flexfiles: Fix PTR_ERR() dereferences in ff_layout_track_ds_error\u000a\u000acommit 8e04fdfadda75a849c649f7e50fe7d97772e1fcb upstream.\u000a\u000amirror->mirror_ds can be NULL if uninitialised, but can contain\u000aa PTR_ERR() if call to GETDEVICEINFO failed.\u000a\u000aFixes: 65990d1afbd2 (\"pNFS/flexfiles: Fix a deadlock on LAYOUTGET\")\u000aSigned-off-by: Trond Myklebust \u000aCc: stable@vger.kernel.org # 4.10+\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "119c5aa1a3b5ce535880a9cb6ee96f957da0d431", "msg" : "pnfs/flexfiles: Fix PTR_ERR() dereferences in ff_layout_track_ds_error", "paths" : [ { "editType" : "edit", "file" : "fs/nfs/flexfilelayout/flexfilelayoutdev.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/nfs/pnfs.c" ], "commitId" : "95934ea7b4afe59501f6b7243e133ecf2d806f43", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pnfs: Fix a problem where we gratuitously start doing I/O through the MDS\u000a\u000acommit 58bbeab425c6c5e318f5b6ae31d351331ddfb34b upstream.\u000a\u000aIf the client has to stop in pnfs_update_layout() to wait for another\u000alayoutget to complete, it currently exits and defaults to I/O through\u000athe MDS if the layoutget was successful.\u000a\u000aFixes: d03360aaf5cc (\"pNFS: Ensure we return the error if someone kills...\")\u000aSigned-off-by: Trond Myklebust \u000aCc: stable@vger.kernel.org # v4.20+\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "95934ea7b4afe59501f6b7243e133ecf2d806f43", "msg" : "pnfs: Fix a problem where we gratuitously start doing I/O through the MDS", "paths" : [ { "editType" : "edit", "file" : "fs/nfs/pnfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/sunrpc/xprt.c", "net/sunrpc/xprtsock.c", "net/sunrpc/clnt.c" ], "commitId" : "fa1a44867c399ea96b5ab74e2a9ea3f7336011a2", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "SUNRPC: Ensure the bvecs are reset when we re-encode the RPC request\u000a\u000acommit 75369089820473eac45e9ddd970081901a373c08 upstream.\u000a\u000aThe bvec tracks the list of pages, so if the number of pages changes\u000adue to a re-encode, we need to reset the bvec as well.\u000a\u000aFixes: 277e4ab7d530 (\"SUNRPC: Simplify TCP receive code by switching...\")\u000aSigned-off-by: Trond Myklebust \u000aCc: stable@vger.kernel.org # v4.20+\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "fa1a44867c399ea96b5ab74e2a9ea3f7336011a2", "msg" : "SUNRPC: Ensure the bvecs are reset when we re-encode the RPC request", "paths" : [ { "editType" : "edit", "file" : "net/sunrpc/xprt.c" }, { "editType" : "edit", "file" : "net/sunrpc/xprtsock.c" }, { "editType" : "edit", "file" : "net/sunrpc/clnt.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "lib/scatterlist.c" ], "commitId" : "688cef5054f2e1cdfa316db52b546c5cf222d9c1", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "lib/scatterlist: Fix mapping iterator when sg->offset is greater than PAGE_SIZE\u000a\u000acommit aeb87246537a83c2aff482f3f34a2e0991e02cbc upstream.\u000a\u000aAll mapping iterator logic is based on the assumption that sg->offset\u000ais always lower than PAGE_SIZE.\u000a\u000aBut there are situations where sg->offset is such that the SG item\u000ais on the second page. In that case sg_copy_to_buffer() fails\u000aproperly copying the data into the buffer. One of the reason is\u000athat the data will be outside the kmapped area used to access that\u000adata.\u000a\u000aThis patch fixes the issue by adjusting the mapping iterator\u000aoffset and pgoffset fields such that offset is always lower than\u000aPAGE_SIZE.\u000a\u000aSigned-off-by: Christophe Leroy \u000aFixes: 4225fc8555a9 (\"lib/scatterlist: use page iterator in the mapping iterator\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "688cef5054f2e1cdfa316db52b546c5cf222d9c1", "msg" : "lib/scatterlist: Fix mapping iterator when sg->offset is greater than PAGE_SIZE", "paths" : [ { "editType" : "edit", "file" : "lib/scatterlist.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/soc-dapm.c" ], "commitId" : "f4d67769179d75e5ac1e2f599ec6cb4b656473ca", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: dapm: Adapt for debugfs API change\u000a\u000acommit ceaea851b9ea75f9ea2bbefb53ff0d4b27cd5a6e upstream.\u000a\u000aBack in ff9fb72bc07705c (debugfs: return error values, not NULL) the\u000adebugfs APIs were changed to return error pointers rather than NULL\u000apointers on error, breaking the error checking in ASoC. Update the\u000acode to use IS_ERR() and log the codes that are returned as part of\u000athe error messages.\u000a\u000aFixes: ff9fb72bc07705c (debugfs: return error values, not NULL)\u000aSigned-off-by: Mark Brown \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "f4d67769179d75e5ac1e2f599ec6cb4b656473ca", "msg" : "ASoC: dapm: Adapt for debugfs API change", "paths" : [ { "editType" : "edit", "file" : "sound/soc/soc-dapm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/soc/soc-core.c" ], "commitId" : "e36f752d0c0ecd6ea70fd7129d2f8b7dd521b372", "timestamp" : 1564125178000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ASoC: core: Adapt for debugfs API change\u000a\u000acommit c2c928c93173f220955030e8440517b87ec7df92 upstream.\u000a\u000aBack in ff9fb72bc07705c (debugfs: return error values, not NULL) the\u000adebugfs APIs were changed to return error pointers rather than NULL\u000apointers on error, breaking the error checking in ASoC. Update the\u000acode to use IS_ERR() and log the codes that are returned as part of\u000athe error messages.\u000a\u000aFixes: ff9fb72bc07705c (debugfs: return error values, not NULL)\u000aSigned-off-by: Mark Brown \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Mark Brown \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:58 +0200", "id" : "e36f752d0c0ecd6ea70fd7129d2f8b7dd521b372", "msg" : "ASoC: core: Adapt for debugfs API change", "paths" : [ { "editType" : "edit", "file" : "sound/soc/soc-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/raid5.c" ], "commitId" : "70ec79cec535c76c717618b1a603a91167966889", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "raid5-cache: Need to do start() part job after adding journal device\u000a\u000acommit d9771f5ec46c282d518b453c793635dbdc3a2a94 upstream.\u000a\u000acommit d5d885fd514f (\"md: introduce new personality funciton start()\")\u000asplits the init job to two parts. The first part run() does the jobs that\u000ado not require the md threads. The second part start() does the jobs that\u000arequire the md threads.\u000a\u000aNow it just does run() in adding new journal device. It needs to do the\u000asecond part start() too.\u000a\u000aFixes: d5d885fd514f (\"md: introduce new personality funciton start()\")\u000aCc: stable@vger.kernel.org #v4.9+\u000aReported-by: Michal Soltys \u000aSigned-off-by: Xiao Ni \u000aSigned-off-by: Song Liu \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "70ec79cec535c76c717618b1a603a91167966889", "msg" : "raid5-cache: Need to do start() part job after adding journal device", "paths" : [ { "editType" : "edit", "file" : "drivers/md/raid5.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/core/seq/seq_clientmgr.c" ], "commitId" : "6a16356616adf40354205b3e4c681f574f35315b", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: seq: Break too long mutex context in the write loop\u000a\u000acommit ede34f397ddb063b145b9e7d79c6026f819ded13 upstream.\u000a\u000aThe fix for the racy writes and ioctls to sequencer widened the\u000aapplication of client->ioctl_mutex to the whole write loop. Although\u000ait does unlock/relock for the lengthy operation like the event dup,\u000athe loop keeps the ioctl_mutex for the whole time in other\u000asituations. This may take quite long time if the user-space would\u000agive a huge buffer, and this is a likely cause of some weird behavior\u000aspotted by syzcaller fuzzer.\u000a\u000aThis patch puts a simple workaround, just adding a mutex break in the\u000aloop when a large number of events have been processed. This\u000ashouldn't hit any performance drop because the threshold is set high\u000aenough for usual operations.\u000a\u000aFixes: 7bd800915677 (\"ALSA: seq: More protection for concurrent write and ioctl races\")\u000aReported-by: syzbot+97aae04ce27e39cbfca9@syzkaller.appspotmail.com\u000aReported-by: syzbot+4c595632b98bb8ffcc66@syzkaller.appspotmail.com\u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "6a16356616adf40354205b3e4c681f574f35315b", "msg" : "ALSA: seq: Break too long mutex context in the write loop", "paths" : [ { "editType" : "edit", "file" : "sound/core/seq/seq_clientmgr.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/hda_codec.c", "include/sound/hda_codec.h", "sound/pci/hda/patch_hdmi.c" ], "commitId" : "68ffeea0dac5a7ce0a5e4c64fa69f0c8a0048493", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda - Don't resume forcibly i915 HDMI/DP codec\u000a\u000acommit 4914da2fb0c89205790503f20dfdde854f3afdd8 upstream.\u000a\u000aWe apply the codec resume forcibly at system resume callback for\u000aupdating and syncing the jack detection state that may have changed\u000aduring sleeping. This is, however, superfluous for the codec like\u000aIntel HDMI/DP, where the jack detection is managed via the audio\u000acomponent notification; i.e. the jack state change shall be reported\u000asooner or later from the graphics side at mode change.\u000a\u000aThis patch changes the codec resume callback to avoid the forcible\u000aresume conditionally with a new flag, codec->relaxed_resume, for\u000areducing the resume time. The flag is set in the codec probe.\u000a\u000aAlthough this doesn't fix the entire bug mentioned in the bugzilla\u000aentry below, it's still a good optimization and some improvements are\u000aseen.\u000a\u000aBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=201901\u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "68ffeea0dac5a7ce0a5e4c64fa69f0c8a0048493", "msg" : "ALSA: hda - Don't resume forcibly i915 HDMI/DP codec", "paths" : [ { "editType" : "edit", "file" : "include/sound/hda_codec.h" }, { "editType" : "edit", "file" : "sound/pci/hda/hda_codec.c" }, { "editType" : "edit", "file" : "sound/pci/hda/patch_hdmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_realtek.c" ], "commitId" : "7f6d5649255343aa326469e8a46ddadec9db35e4", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/realtek - Fixed Headphone Mic can't record on Dell platform\u000a\u000acommit fbc571290d9f7bfe089c50f4ac4028dd98ebfe98 upstream.\u000a\u000aIt assigned to wrong model. So, The headphone Mic can't work.\u000a\u000aFixes: 3f640970a414 (\"ALSA: hda - Fix headset mic detection problem for several Dell laptops\")\u000aSigned-off-by: Kailang Yang \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "7f6d5649255343aa326469e8a46ddadec9db35e4", "msg" : "ALSA: hda/realtek - Fixed Headphone Mic can't record on Dell platform", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_realtek.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_realtek.c" ], "commitId" : "7098182458e0bdd6fe392e8cf5e3a48f99b580bc", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/realtek: apply ALC891 headset fixup to one Dell machine\u000a\u000acommit 4b4e0e32e4b09274dbc9d173016c1a026f44608c upstream.\u000a\u000aWithout this patch, the headset-mic and headphone-mic don't work.\u000a\u000aCc: \u000aSigned-off-by: Hui Wang \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "7098182458e0bdd6fe392e8cf5e3a48f99b580bc", "msg" : "ALSA: hda/realtek: apply ALC891 headset fixup to one Dell machine", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_realtek.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_hdmi.c" ], "commitId" : "33b9b37da4dfc0d9540d99c5441843e63df45dcd", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/hdmi - Remove duplicated define\u000a\u000acommit eb4177116bf568a413c544eca3f4446cb4064be9 upstream.\u000a\u000aINTEL_GET_VENDOR_VERB is defined twice identically.\u000aLet's remove a superfluous line.\u000a\u000aFixes: b0d8bc50b9f2 (\"ALSA: hda: hdmi - add Icelake support\")\u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "33b9b37da4dfc0d9540d99c5441843e63df45dcd", "msg" : "ALSA: hda/hdmi - Remove duplicated define", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_hdmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "sound/pci/hda/patch_hdmi.c" ], "commitId" : "1d14907314edd074ee1666ed84d6d70c20ebeff5", "timestamp" : 1564125179000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ALSA: hda/hdmi - Fix i915 reverse port/pin mapping\u000a\u000acommit 3140aafb22edeab0cc41f15f53b12a118c0ac215 upstream.\u000a\u000aThe recent fix for Icelake HDMI codec introduced the mapping from pin\u000aNID to the i915 gfx port number. However, it forgot the reverse\u000amapping from the port number to the pin NID that is used in the ELD\u000anotifier callback. As a result, it's processed to a wrong widget and\u000agives a warning like\u000a snd_hda_codec_hdmi hdaudioC0D2: HDMI: pin nid 5 not registered\u000a\u000aThis patch corrects it with a proper reverse mapping function.\u000a\u000aBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204133\u000aFixes: b0d8bc50b9f2 (\"ALSA: hda: hdmi - add Icelake support\")\u000aReviewed-by: Kai Vehmanen \u000aCc: \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:12:59 +0200", "id" : "1d14907314edd074ee1666ed84d6d70c20ebeff5", "msg" : "ALSA: hda/hdmi - Fix i915 reverse port/pin mapping", "paths" : [ { "editType" : "edit", "file" : "sound/pci/hda/patch_hdmi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/ceph/file.c" ], "commitId" : "baa616aeee0e297704fb1297072fc2e9c5fb53c8", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ceph: fix end offset in truncate_inode_pages_range call\u000a\u000acommit d31d07b97a5e76f41e00eb81dcca740e84aa7782 upstream.\u000a\u000aCommit e450f4d1a5d6 (\"ceph: pass inclusive lend parameter to\u000afilemap_write_and_wait_range()\") fixed the end offset parameter used to\u000acall filemap_write_and_wait_range and invalidate_inode_pages2_range.\u000aUnfortunately it missed truncate_inode_pages_range, introducing a\u000aregression that is easily detected by xfstest generic/130.\u000a\u000aThe problem is that when doing direct IO it is possible that an extra page\u000ais truncated from the page cache when the end offset is page aligned.\u000aThis can cause data loss if that page hasn't been sync'ed to the OSDs.\u000a\u000aWhile there, change code to use PAGE_ALIGN macro instead.\u000a\u000aCc: stable@vger.kernel.org\u000aFixes: e450f4d1a5d6 (\"ceph: pass inclusive lend parameter to filemap_write_and_wait_range()\")\u000aSigned-off-by: Luis Henriques \u000aReviewed-by: Jeff Layton \u000aSigned-off-by: Ilya Dryomov \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "baa616aeee0e297704fb1297072fc2e9c5fb53c8", "msg" : "ceph: fix end offset in truncate_inode_pages_range call", "paths" : [ { "editType" : "edit", "file" : "fs/ceph/file.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/v4l2-core/v4l2-ctrls.c" ], "commitId" : "0efb47901bc015913fefcdc7ed9e6adff8949c27", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: v4l2: Test type instead of cfg->type in v4l2_ctrl_new_custom()\u000a\u000acommit 07d89227a983df957a6a7c56f7c040cde9ac571f upstream.\u000a\u000acfg->type can be overridden by v4l2_ctrl_fill() and the new value is\u000astored in the local type var. Fix the tests to use this local var.\u000a\u000aFixes: 0996517cf8ea (\"V4L/DVB: v4l2: Add new control handling framework\")\u000aCc: \u000aSigned-off-by: Boris Brezillon \u000a[hverkuil-cisco@xs4all.nl: change to !qmenu and !qmenu_int (checkpatch)]\u000aSigned-off-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "0efb47901bc015913fefcdc7ed9e6adff8949c27", "msg" : "media: v4l2: Test type instead of cfg->type in v4l2_ctrl_new_custom()", "paths" : [ { "editType" : "edit", "file" : "drivers/media/v4l2-core/v4l2-ctrls.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/coda/coda-bit.c" ], "commitId" : "8829a3a0826518016beb5673c8bf4871a3703970", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: coda: Remove unbalanced and unneeded mutex unlock\u000a\u000acommit 766b9b168f6c75c350dd87c3e0bc6a9b322f0013 upstream.\u000a\u000aThe mutex unlock in the threaded interrupt handler is not paired\u000awith any mutex lock. Remove it.\u000a\u000aThis bug has been here for a really long time, so it applies\u000ato any stable repo.\u000a\u000aReviewed-by: Philipp Zabel \u000aSigned-off-by: Ezequiel Garcia \u000aSigned-off-by: Hans Verkuil \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "8829a3a0826518016beb5673c8bf4871a3703970", "msg" : "media: coda: Remove unbalanced and unneeded mutex unlock", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/coda/coda-bit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/common/videobuf2/videobuf2-core.c" ], "commitId" : "1d9067ed8051dbeca284f4cefc447c9cdd936625", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: videobuf2-core: Prevent size alignment wrapping buffer size to 0\u000a\u000acommit defcdc5d89ced780fb45196d539d6570ec5b1ba5 upstream.\u000a\u000aPAGE_ALIGN() may wrap the buffer size around to 0. Prevent this by\u000achecking that the aligned value is not smaller than the unaligned one.\u000a\u000aNote on backporting to stable: the file used to be under\u000adrivers/media/v4l2-core, it was moved to the current location after 4.14.\u000a\u000aSigned-off-by: Sakari Ailus \u000aCc: stable@vger.kernel.org\u000aReviewed-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "1d9067ed8051dbeca284f4cefc447c9cdd936625", "msg" : "media: videobuf2-core: Prevent size alignment wrapping buffer size to 0", "paths" : [ { "editType" : "edit", "file" : "drivers/media/common/videobuf2/videobuf2-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/common/videobuf2/videobuf2-dma-sg.c" ], "commitId" : "95fdf43fe06bfcc18644cb70291beac5e5f8f191", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "media: videobuf2-dma-sg: Prevent size from overflowing\u000a\u000acommit 14f28f5cea9e3998442de87846d1907a531b6748 upstream.\u000a\u000abuf->size is an unsigned long; casting that to int will lead to an\u000aoverflow if buf->size exceeds INT_MAX.\u000a\u000aFix this by changing the type to unsigned long instead. This is possible\u000aas the buf->size is always aligned to PAGE_SIZE, and therefore the size\u000awill never have values lesser than 0.\u000a\u000aNote on backporting to stable: the file used to be under\u000adrivers/media/v4l2-core, it was moved to the current location after 4.14.\u000a\u000aSigned-off-by: Sakari Ailus \u000aCc: stable@vger.kernel.org\u000aReviewed-by: Hans Verkuil \u000aSigned-off-by: Mauro Carvalho Chehab \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "95fdf43fe06bfcc18644cb70291beac5e5f8f191", "msg" : "media: videobuf2-dma-sg: Prevent size from overflowing", "paths" : [ { "editType" : "edit", "file" : "drivers/media/common/videobuf2/videobuf2-dma-sg.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/nested.c" ], "commitId" : "4ff7d3d1986f7c8ae88b943f43d46f1362ac8d07", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: nVMX: Don't dump VMCS if virtual APIC page can't be mapped\u000a\u000acommit 73cb85568433feadb79e963bf2efba9b3e9ae3df upstream.\u000a\u000a... as a malicious userspace can run a toy guest to generate invalid\u000avirtual-APIC page addresses in L1, i.e. flood the kernel log with error\u000amessages.\u000a\u000aFixes: 690908104e39d (\"KVM: nVMX: allow tests to use bad virtual-APIC page address\")\u000aCc: stable@vger.kernel.org\u000aCc: Paolo Bonzini \u000aSigned-off-by: Sean Christopherson \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "4ff7d3d1986f7c8ae88b943f43d46f1362ac8d07", "msg" : "KVM: nVMX: Don't dump VMCS if virtual APIC page can't be mapped", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/nested.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/nested.c" ], "commitId" : "3ea511becc9dbcce71043549b9ee641cf4ad1e3f", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: nVMX: Always sync GUEST_BNDCFGS when it comes from vmcs01\u000a\u000acommit 3b013a2972d5bc344d6eaa8f24fdfe268211e45f upstream.\u000a\u000aIf L1 does not set VM_ENTRY_LOAD_BNDCFGS, then L1's BNDCFGS value must\u000abe propagated to vmcs02 since KVM always runs with VM_ENTRY_LOAD_BNDCFGS\u000awhen MPX is supported. Because the value effectively comes from vmcs01,\u000avmcs02 must be updated even if vmcs12 is clean.\u000a\u000aFixes: 62cf9bd8118c4 (\"KVM: nVMX: Fix emulation of VM_ENTRY_LOAD_BNDCFGS\")\u000aCc: stable@vger.kernel.org\u000aCc: Liran Alon \u000aSigned-off-by: Sean Christopherson \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "3ea511becc9dbcce71043549b9ee641cf4ad1e3f", "msg" : "KVM: nVMX: Always sync GUEST_BNDCFGS when it comes from vmcs01", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/nested.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/vmx.c" ], "commitId" : "e64176cd59c2f2915bea66627023f114f66e9e06", "timestamp" : 1564125180000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: VMX: Fix handling of #MC that occurs during VM-Entry\u000a\u000acommit beb8d93b3e423043e079ef3dda19dad7b28467a8 upstream.\u000a\u000aA previous fix to prevent KVM from consuming stale VMCS state after a\u000afailed VM-Entry inadvertantly blocked KVM's handling of machine checks\u000athat occur during VM-Entry.\u000a\u000aPer Intel's SDM, a #MC during VM-Entry is handled in one of three ways,\u000adepending on when the #MC is recognoized. As it pertains to this bug\u000afix, the third case explicitly states EXIT_REASON_MCE_DURING_VMENTRY\u000ais handled like any other VM-Exit during VM-Entry, i.e. sets bit 31 to\u000aindicate the VM-Entry failed.\u000a\u000aIf a machine-check event occurs during a VM entry, one of the following occurs:\u000a - The machine-check event is handled as if it occurred before the VM entry:\u000a ...\u000a - The machine-check event is handled after VM entry completes:\u000a ...\u000a - A VM-entry failure occurs as described in Section 26.7. The basic\u000a exit reason is 41, for \"VM-entry failure due to machine-check event\".\u000a\u000aExplicitly handle EXIT_REASON_MCE_DURING_VMENTRY as a one-off case in\u000avmx_vcpu_run() instead of binning it into vmx_complete_atomic_exit().\u000aDoing so allows vmx_vcpu_run() to handle VMX_EXIT_REASONS_FAILED_VMENTRY\u000ain a sane fashion and also simplifies vmx_complete_atomic_exit() since\u000aVMCS.VM_EXIT_INTR_INFO is guaranteed to be fresh.\u000a\u000aFixes: b060ca3b2e9e7 (\"kvm: vmx: Handle VMLAUNCH/VMRESUME failure properly\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Sean Christopherson \u000aReviewed-by: Jim Mattson \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:00 +0200", "id" : "e64176cd59c2f2915bea66627023f114f66e9e06", "msg" : "KVM: VMX: Fix handling of #MC that occurs during VM-Entry", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/vmx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/vmx.c" ], "commitId" : "f4905184931ec1664184f941215d04ebf29315f4", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: VMX: check CPUID before allowing read/write of IA32_XSS\u000a\u000acommit 4d763b168e9c5c366b05812c7bba7662e5ea3669 upstream.\u000a\u000aRaise #GP when guest read/write IA32_XSS, but the CPUID bits\u000asay that it shouldn't exist.\u000a\u000aFixes: 203000993de5 (kvm: vmx: add MSR logic for XSAVES)\u000aReported-by: Xiaoyao Li \u000aReported-by: Tao Xu \u000aCc: Paolo Bonzini \u000aCc: Radim Krčmář \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Wanpeng Li \u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "f4905184931ec1664184f941215d04ebf29315f4", "msg" : "KVM: VMX: check CPUID before allowing read/write of IA32_XSS", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/vmx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/kvm/book3s_hv.c" ], "commitId" : "eb6bb8d534b85690bb2e232ac21389feda1ca1c5", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: PPC: Book3S HV: Signed extend decrementer value if not using large decrementer\u000a\u000acommit 869537709ebf1dc865e75c3fc97b23f8acf37c16 upstream.\u000a\u000aOn POWER9 the decrementer can operate in large decrementer mode where\u000athe decrementer is 56 bits and signed extended to 64 bits. When not\u000aoperating in this mode the decrementer behaves as a 32 bit decrementer\u000awhich is NOT signed extended (as on POWER8).\u000a\u000aCurrently when reading a guest decrementer value we don't take into\u000aaccount whether the large decrementer is enabled or not, and this\u000ameans the value will be incorrect when the guest is not using the\u000alarge decrementer. Fix this by sign extending the value read when the\u000aguest isn't using the large decrementer.\u000a\u000aFixes: 95a6432ce903 (\"KVM: PPC: Book3S HV: Streamlined guest entry/exit path on P9 for radix guests\")\u000aCc: stable@vger.kernel.org # v4.20+\u000aSigned-off-by: Suraj Jitindar Singh \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "eb6bb8d534b85690bb2e232ac21389feda1ca1c5", "msg" : "KVM: PPC: Book3S HV: Signed extend decrementer value if not using large decrementer", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/kvm/book3s_hv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/kvm/book3s_hv.c" ], "commitId" : "5328368b74d21cf7ad5214f50f54fca215772f52", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: PPC: Book3S HV: Clear pending decrementer exceptions on nested guest entry\u000a\u000acommit 3c25ab35fbc8526ac0c9b298e8a78e7ad7a55479 upstream.\u000a\u000aIf we enter an L1 guest with a pending decrementer exception then this\u000ais cleared on guest exit if the guest has writtien a positive value\u000ainto the decrementer (indicating that it handled the decrementer\u000aexception) since there is no other way to detect that the guest has\u000ahandled the pending exception and that it should be dequeued. In the\u000aevent that the L1 guest tries to run a nested (L2) guest immediately\u000aafter this and the L2 guest decrementer is negative (which is loaded\u000aby L1 before making the H_ENTER_NESTED hcall), then the pending\u000adecrementer exception isn't cleared and the L2 entry is blocked since\u000aL1 has a pending exception, even though L1 may have already handled\u000athe exception and written a positive value for it's decrementer. This\u000aresults in a loop of L1 trying to enter the L2 guest and L0 blocking\u000athe entry since L1 has an interrupt pending with the outcome being\u000athat L2 never gets to run and hangs.\u000a\u000aFix this by clearing any pending decrementer exceptions when L1 makes\u000athe H_ENTER_NESTED hcall since it won't do this if it's decrementer\u000ahas gone negative, and anyway it's decrementer has been communicated\u000ato L0 in the hdec_expires field and L0 will return control to L1 when\u000athis goes negative by delivering an H_DECREMENTER exception.\u000a\u000aFixes: 95a6432ce903 (\"KVM: PPC: Book3S HV: Streamlined guest entry/exit path on P9 for radix guests\")\u000aCc: stable@vger.kernel.org # v4.20+\u000aSigned-off-by: Suraj Jitindar Singh \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "5328368b74d21cf7ad5214f50f54fca215772f52", "msg" : "KVM: PPC: Book3S HV: Clear pending decrementer exceptions on nested guest entry", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/kvm/book3s_hv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/kvm/book3s_hv_tm.c" ], "commitId" : "95680d0eb11e5ff0ac44af80588d657b9d6af352", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: PPC: Book3S HV: Fix CR0 setting in TM emulation\u000a\u000acommit 3fefd1cd95df04da67c83c1cb93b663f04b3324f upstream.\u000a\u000aWhen emulating tsr, treclaim and trechkpt, we incorrectly set CR0. The\u000acode currently sets:\u000a CR0 <- 00 || MSR[TS]\u000abut according to the ISA it should be:\u000a CR0 <- 0 || MSR[TS] || 0\u000a\u000aThis fixes the bit shift to put the bits in the correct location.\u000a\u000aThis is a data integrity issue as CR0 is corrupted.\u000a\u000aFixes: 4bb3c7a0208f (\"KVM: PPC: Book3S HV: Work around transactional memory bugs in POWER9\")\u000aCc: stable@vger.kernel.org # v4.17+\u000aTested-by: Suraj Jitindar Singh \u000aSigned-off-by: Michael Neuling \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "95680d0eb11e5ff0ac44af80588d657b9d6af352", "msg" : "KVM: PPC: Book3S HV: Fix CR0 setting in TM emulation", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/kvm/book3s_hv_tm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/pmu.c" ], "commitId" : "edadec197fbf335430c18ad188dd262028c5c18a", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: x86/vPMU: refine kvm_pmu err msg when event creation failed\u000a\u000acommit 6fc3977ccc5d3c22e851f2dce2d3ce2a0a843842 upstream.\u000a\u000aIf a perf_event creation fails due to any reason of the host perf\u000asubsystem, it has no chance to log the corresponding event for guest\u000awhich may cause abnormal sampling data in guest result. In debug mode,\u000athis message helps to understand the state of vPMC and we may not\u000alimit the number of occurrences but not in a spamming style.\u000a\u000aSuggested-by: Joe Perches \u000aSigned-off-by: Like Xu \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "edadec197fbf335430c18ad188dd262028c5c18a", "msg" : "KVM: x86/vPMU: refine kvm_pmu err msg when event creation failed", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/pmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/boot/dts/nvidia/tegra210.dtsi" ], "commitId" : "cc43c9ef3114e59eff0ea98738cef11b50e9a4ad", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: tegra: Fix AGIC register range\u000a\u000acommit ba24eee6686f6ed3738602b54d959253316a9541 upstream.\u000a\u000aThe Tegra AGIC interrupt controller is an ARM GIC400 interrupt\u000acontroller. Per the ARM GIC device-tree binding, the first address\u000aregion is for the GIC distributor registers and the second address\u000aregion is for the GIC CPU interface registers. The address space for\u000athe distributor registers is 4kB, but currently this is incorrectly\u000adefined as 8kB for the Tegra AGIC and overlaps with the CPU interface\u000aregisters. Correct the address space for the distributor to be 4kB.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jon Hunter \u000aFixes: bcdbde433542 (\"arm64: tegra: Add AGIC node for Tegra210\")\u000aSigned-off-by: Thierry Reding \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "cc43c9ef3114e59eff0ea98738cef11b50e9a4ad", "msg" : "arm64: tegra: Fix AGIC register range", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/boot/dts/nvidia/tegra210.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm64/include/asm/irqflags.h" ], "commitId" : "2cd1c187d315556e44db78b205530000f2cd49f8", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "arm64: irqflags: Add condition flags to inline asm clobber list\u000a\u000acommit f57065782f245ca96f1472209a485073bbc11247 upstream.\u000a\u000aSome of the inline assembly instruction use the condition flags and need\u000ato include \"cc\" in the clobber list.\u000a\u000aFixes: 4a503217ce37 (\"arm64: irqflags: Use ICC_PMR_EL1 for interrupt masking\")\u000aCc: # 5.1.x-\u000aSuggested-by: Marc Zyngier \u000aCc: Will Deacon \u000aReviewed-by: Marc Zyngier \u000aAcked-by: Mark Rutland \u000aSigned-off-by: Julien Thierry \u000aSigned-off-by: Catalin Marinas \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "2cd1c187d315556e44db78b205530000f2cd49f8", "msg" : "arm64: irqflags: Add condition flags to inline asm clobber list", "paths" : [ { "editType" : "edit", "file" : "arch/arm64/include/asm/irqflags.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/core/devio.c", "include/linux/sched/signal.h", "kernel/signal.c" ], "commitId" : "c8c3ea85d74f3d56c009a28ff5108a086ec90296", "timestamp" : 1564125181000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "signal/usb: Replace kill_pid_info_as_cred with kill_pid_usb_asyncio\u000a\u000acommit 70f1b0d34bdf03065fe869e93cc17cad1ea20c4a upstream.\u000a\u000aThe usb support for asyncio encoded one of it's values in the wrong\u000afield. It should have used si_value but instead used si_addr which is\u000anot present in the _rt union member of struct siginfo.\u000a\u000aThe practical result of this is that on a 64bit big endian kernel\u000awhen delivering a signal to a 32bit process the si_addr field\u000ais set to NULL, instead of the expected pointer value.\u000a\u000aThis issue can not be fixed in copy_siginfo_to_user32 as the usb\u000ausage of the the _sigfault (aka si_addr) member of the siginfo\u000aunion when SI_ASYNCIO is set is incompatible with the POSIX and\u000aglibc usage of the _rt member of the siginfo union.\u000a\u000aTherefore replace kill_pid_info_as_cred with kill_pid_usb_asyncio a\u000adedicated function for this one specific case. There are no other\u000ausers of kill_pid_info_as_cred so this specialization should have no\u000aimpact on the amount of code in the kernel. Have kill_pid_usb_asyncio\u000atake instead of a siginfo_t which is difficult and error prone, 3\u000aarguments, a signal number, an errno value, and an address enconded as\u000aa sigval_t. The encoding of the address as a sigval_t allows the\u000acode that reads the userspace request for a signal to handle this\u000acompat issue along with all of the other compat issues.\u000a\u000aAdd BUILD_BUG_ONs in kernel/signal.c to ensure that we can now place\u000athe pointer value at the in si_pid (instead of si_addr). That is the\u000acode now verifies that si_pid and si_addr always occur at the same\u000alocation. Further the code veries that for native structures a value\u000aplaced in si_pid and spilling into si_uid will appear in userspace in\u000asi_addr (on a byte by byte copy of siginfo or a field by field copy of\u000asiginfo). The code also verifies that for a 64bit kernel and a 32bit\u000auserspace the 32bit pointer will fit in si_pid.\u000a\u000aI have used the usbsig.c program below written by Alan Stern and\u000aslightly tweaked by me to run on a big endian machine to verify the\u000aissue exists (on sparc64) and to confirm the patch below fixes the issue.\u000a\u000a /* usbsig.c -- test USB async signal delivery */\u000a\u000a #define _GNU_SOURCE\u000a #include \u000a #include \u000a #include \u000a #include \u000a #include \u000a #include \u000a #include \u000a #include \u000a #include \u000a\u000a static struct usbdevfs_urb urb;\u000a static struct usbdevfs_disconnectsignal ds;\u000a static volatile sig_atomic_t done = 0;\u000a\u000a void urb_handler(int sig, siginfo_t *info , void *ucontext)\u000a {\u000a \u0009printf(\"Got signal %d, signo %d errno %d code %d addr: %p urb: %p\\n\",\u000a \u0009 sig, info->si_signo, info->si_errno, info->si_code,\u000a \u0009 info->si_addr, &urb);\u000a\u000a \u0009printf(\"%s\\n\", (info->si_addr == &urb) ? \"Good\" : \"Bad\");\u000a }\u000a\u000a void ds_handler(int sig, siginfo_t *info , void *ucontext)\u000a {\u000a \u0009printf(\"Got signal %d, signo %d errno %d code %d addr: %p ds: %p\\n\",\u000a \u0009 sig, info->si_signo, info->si_errno, info->si_code,\u000a \u0009 info->si_addr, &ds);\u000a\u000a \u0009printf(\"%s\\n\", (info->si_addr == &ds) ? \"Good\" : \"Bad\");\u000a \u0009done = 1;\u000a }\u000a\u000a int main(int argc, char **argv)\u000a {\u000a \u0009char *devfilename;\u000a \u0009int fd;\u000a \u0009int rc;\u000a \u0009struct sigaction act;\u000a \u0009struct usb_ctrlrequest *req;\u000a \u0009void *ptr;\u000a \u0009char buf[80];\u000a\u000a \u0009if (argc != 2) {\u000a \u0009\u0009fprintf(stderr, \"Usage: usbsig device-file-name\\n\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009devfilename = argv[1];\u000a \u0009fd = open(devfilename, O_RDWR);\u000a \u0009if (fd == -1) {\u000a \u0009\u0009perror(\"Error opening device file\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009act.sa_sigaction = urb_handler;\u000a \u0009sigemptyset(&act.sa_mask);\u000a \u0009act.sa_flags = SA_SIGINFO;\u000a\u000a \u0009rc = sigaction(SIGUSR1, &act, NULL);\u000a \u0009if (rc == -1) {\u000a \u0009\u0009perror(\"Error in sigaction\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009act.sa_sigaction = ds_handler;\u000a \u0009sigemptyset(&act.sa_mask);\u000a \u0009act.sa_flags = SA_SIGINFO;\u000a\u000a \u0009rc = sigaction(SIGUSR2, &act, NULL);\u000a \u0009if (rc == -1) {\u000a \u0009\u0009perror(\"Error in sigaction\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009memset(&urb, 0, sizeof(urb));\u000a \u0009urb.type = USBDEVFS_URB_TYPE_CONTROL;\u000a \u0009urb.endpoint = USB_DIR_IN | 0;\u000a \u0009urb.buffer = buf;\u000a \u0009urb.buffer_length = sizeof(buf);\u000a \u0009urb.signr = SIGUSR1;\u000a\u000a \u0009req = (struct usb_ctrlrequest *) buf;\u000a \u0009req->bRequestType = USB_DIR_IN | USB_TYPE_STANDARD | USB_RECIP_DEVICE;\u000a \u0009req->bRequest = USB_REQ_GET_DESCRIPTOR;\u000a \u0009req->wValue = htole16(USB_DT_DEVICE << 8);\u000a \u0009req->wIndex = htole16(0);\u000a \u0009req->wLength = htole16(sizeof(buf) - sizeof(*req));\u000a\u000a \u0009rc = ioctl(fd, USBDEVFS_SUBMITURB, &urb);\u000a \u0009if (rc == -1) {\u000a \u0009\u0009perror(\"Error in SUBMITURB ioctl\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009rc = ioctl(fd, USBDEVFS_REAPURB, &ptr);\u000a \u0009if (rc == -1) {\u000a \u0009\u0009perror(\"Error in REAPURB ioctl\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009memset(&ds, 0, sizeof(ds));\u000a \u0009ds.signr = SIGUSR2;\u000a \u0009ds.context = &ds;\u000a \u0009rc = ioctl(fd, USBDEVFS_DISCSIGNAL, &ds);\u000a \u0009if (rc == -1) {\u000a \u0009\u0009perror(\"Error in DISCSIGNAL ioctl\");\u000a \u0009\u0009return 1;\u000a \u0009}\u000a\u000a \u0009printf(\"Waiting for usb disconnect\\n\");\u000a \u0009while (!done) {\u000a \u0009\u0009sleep(1);\u000a \u0009}\u000a\u000a \u0009close(fd);\u000a \u0009return 0;\u000a }\u000a\u000aCc: Greg Kroah-Hartman \u000aCc: linux-usb@vger.kernel.org\u000aCc: Alan Stern \u000aCc: Oliver Neukum \u000aFixes: v2.3.39\u000aCc: stable@vger.kernel.org\u000aAcked-by: Alan Stern \u000aSigned-off-by: \"Eric W. Biederman\" \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:01 +0200", "id" : "c8c3ea85d74f3d56c009a28ff5108a086ec90296", "msg" : "signal/usb: Replace kill_pid_info_as_cred with kill_pid_usb_asyncio", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/core/devio.c" }, { "editType" : "edit", "file" : "include/linux/sched/signal.h" }, { "editType" : "edit", "file" : "kernel/signal.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/signal.c" ], "commitId" : "e897dd22800f02bd48aefb1511fff0b2ce96e94c", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "signal: Correct namespace fixups of si_pid and si_uid\u000a\u000acommit 7a0cf094944e2540758b7f957eb6846d5126f535 upstream.\u000a\u000aThe function send_signal was split from __send_signal so that it would\u000abe possible to bypass the namespace logic based upon current[1]. As it\u000aturns out the si_pid and the si_uid fixup are both inappropriate in\u000athe case of kill_pid_usb_asyncio so move that logic into send_signal.\u000a\u000aIt is difficult to arrange but possible for a signal with an si_code\u000aof SI_TIMER or SI_SIGIO to be sent across namespace boundaries. In\u000awhich case tests for when it is ok to change si_pid and si_uid based\u000aon SI_FROMUSER are incorrect. Replace the use of SI_FROMUSER with a\u000anew test has_si_pid_and_used based on siginfo_layout.\u000a\u000aNow that the uid fixup is no longer present after expanding\u000aSEND_SIG_NOINFO properly calculate the si_uid that the target\u000atask needs to read.\u000a\u000a[1] 7978b567d315 (\"signals: add from_ancestor_ns parameter to send_signal()\")\u000aCc: stable@vger.kernel.org\u000aFixes: 6588c1e3ff01 (\"signals: SI_USER: Masquerade si_pid when crossing pid ns boundary\")\u000aFixes: 6b550f949594 (\"user namespace: make signal.c respect user namespaces\")\u000aSigned-off-by: \"Eric W. Biederman\" \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "e897dd22800f02bd48aefb1511fff0b2ce96e94c", "msg" : "signal: Correct namespace fixups of si_pid and si_uid", "paths" : [ { "editType" : "edit", "file" : "kernel/signal.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/proc/proc_sysctl.c" ], "commitId" : "7eb45a94c279dd5af4cafaa738ae93737517eef4", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.\u000a\u000acommit 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf upstream.\u000a\u000aNormally, the inode's i_uid/i_gid are translated relative to s_user_ns,\u000abut this is not a correct behavior for proc. Since sysctl permission\u000acheck in test_perm is done against GLOBAL_ROOT_[UG]ID, it makes more\u000asense to use these values in u_[ug]id of proc inodes. In other words:\u000aalthough uid/gid in the inode is not read during test_perm, the inode\u000alogically belongs to the root of the namespace. I have confirmed this\u000awith Eric Biederman at LPC and in this thread:\u000a https://lore.kernel.org/lkml/87k1kzjdff.fsf@xmission.com\u000a\u000aConsequences\u000a============\u000a\u000aSince the i_[ug]id values of proc nodes are not used for permissions\u000achecks, this change usually makes no functional difference. However, it\u000acauses an issue in a setup where:\u000a\u000a * a namespace container is created without root user in container -\u000a hence the i_[ug]id of proc nodes are set to INVALID_[UG]ID\u000a\u000a * container creator tries to configure it by writing /proc/sys files,\u000a e.g. writing /proc/sys/kernel/shmmax to configure shared memory limit\u000a\u000aKernel does not allow to open an inode for writing if its i_[ug]id are\u000ainvalid, making it impossible to write shmmax and thus - configure the\u000acontainer.\u000a\u000aUsing a container with no root mapping is apparently rare, but we do use\u000athis configuration at Google. Also, we use a generic tool to configure\u000athe container limits, and the inability to write any of them causes a\u000afailure.\u000a\u000aHistory\u000a=======\u000a\u000aThe invalid uids/gids in inodes first appeared due to 81754357770e (fs:\u000aUpdate i_[ug]id_(read|write) to translate relative to s_user_ns).\u000aHowever, AFAIK, this did not immediately cause any issues. The\u000ainability to write to these \"invalid\" inodes was only caused by a later\u000acommit 0bd23d09b874 (vfs: Don't modify inodes with a uid or gid unknown\u000ato the vfs).\u000a\u000aTested: Used a repro program that creates a user namespace without any\u000amapping and stat'ed /proc/$PID/root/proc/sys/kernel/shmmax from outside.\u000aBefore the change, it shows the overflow uid, with the change it's 0.\u000aThe overflow uid indicates that the uid in the inode is not correct and\u000athus it is not possible to open the file for writing.\u000a\u000aLink: http://lkml.kernel.org/r/20190708115130.250149-1-rburny@google.com\u000aFixes: 0bd23d09b874 (\"vfs: Don't modify inodes with a uid or gid unknown to the vfs\")\u000aSigned-off-by: Radoslaw Burny \u000aAcked-by: Luis Chamberlain \u000aCc: Kees Cook \u000aCc: \"Eric W . Biederman\" \u000aCc: Seth Forshee \u000aCc: John Sperbeck \u000aCc: Alexey Dobriyan \u000aCc: \u0009[4.8+]\u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "7eb45a94c279dd5af4cafaa738ae93737517eef4", "msg" : "fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.", "paths" : [ { "editType" : "edit", "file" : "fs/proc/proc_sysctl.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/i3c/master.c" ], "commitId" : "3620a72ccc726aef247e4d7c5968546a94fdb551", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "i3c: fix i2c and i3c scl rate by bus mode\u000a\u000acommit ecc8fb54bd443bf69996d9d5ddb8d90a50f14936 upstream.\u000a\u000aCurrently the I3C framework limits SCL frequency to FM speed when\u000adealing with a mixed slow bus, even if all I2C devices are FM+ capable.\u000a\u000aThe core was also not accounting for I3C speed limitations when\u000aoperating in mixed slow mode and was erroneously using FM+ speed as the\u000amax I2C speed when operating in mixed fast mode.\u000a\u000aFixes: 3a379bbcea0a (\"i3c: Add core I3C infrastructure\")\u000aSigned-off-by: Vitor Soares \u000aCc: Boris Brezillon \u000aCc: \u000aCc: \u000aSigned-off-by: Boris Brezillon \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "3620a72ccc726aef247e4d7c5968546a94fdb551", "msg" : "i3c: fix i2c and i3c scl rate by bus mode", "paths" : [ { "editType" : "edit", "file" : "drivers/i3c/master.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "scripts/kconfig/confdata.c", "scripts/kconfig/expr.h" ], "commitId" : "ea3f1487159894501d1d3a1e120e826e24d3b3a3", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "kconfig: fix missing choice values in auto.conf\u000a\u000acommit 8e2442a5f86e1f77b86401fce274a7f622740bc4 upstream.\u000a\u000aSince commit 00c864f8903d (\"kconfig: allow all config targets to write\u000aauto.conf if missing\"), Kconfig creates include/config/auto.conf in the\u000adefconfig stage when it is missing.\u000a\u000aJoonas Kylmälä reported incorrect auto.conf generation under some\u000acircumstances.\u000a\u000aTo reproduce it, apply the following diff:\u000a\u000a| --- a/arch/arm/configs/imx_v6_v7_defconfig\u000a| +++ b/arch/arm/configs/imx_v6_v7_defconfig\u000a| @@ -345,14 +345,7 @@ CONFIG_USB_CONFIGFS_F_MIDI=y\u000a| CONFIG_USB_CONFIGFS_F_HID=y\u000a| CONFIG_USB_CONFIGFS_F_UVC=y\u000a| CONFIG_USB_CONFIGFS_F_PRINTER=y\u000a| -CONFIG_USB_ZERO=m\u000a| -CONFIG_USB_AUDIO=m\u000a| -CONFIG_USB_ETH=m\u000a| -CONFIG_USB_G_NCM=m\u000a| -CONFIG_USB_GADGETFS=m\u000a| -CONFIG_USB_FUNCTIONFS=m\u000a| -CONFIG_USB_MASS_STORAGE=m\u000a| -CONFIG_USB_G_SERIAL=m\u000a| +CONFIG_USB_FUNCTIONFS=y\u000a| CONFIG_MMC=y\u000a| CONFIG_MMC_SDHCI=y\u000a| CONFIG_MMC_SDHCI_PLTFM=y\u000a\u000aAnd then, run:\u000a\u000a$ make ARCH=arm mrproper imx_v6_v7_defconfig\u000a\u000aYou will see CONFIG_USB_FUNCTIONFS=y is correctly contained in the\u000a.config, but not in the auto.conf.\u000a\u000aPlease note drivers/usb/gadget/legacy/Kconfig is included from a choice\u000ablock in drivers/usb/gadget/Kconfig. So USB_FUNCTIONFS is a choice value.\u000a\u000aThis is probably a similar situation described in commit beaaddb62540\u000a(\"kconfig: tests: test defconfig when two choices interact\").\u000a\u000aWhen sym_calc_choice() is called, the choice symbol forgets the\u000aSYMBOL_DEF_USER unless all of its choice values are explicitly set by\u000athe user.\u000a\u000aThe choice symbol is given just one chance to recall it because\u000aset_all_choice_values() is called if SYMBOL_NEED_SET_CHOICE_VALUES\u000ais set.\u000a\u000aWhen sym_calc_choice() is called again, the choice symbol forgets it\u000aforever, since SYMBOL_NEED_SET_CHOICE_VALUES is a one-time aid.\u000aHence, we cannot call sym_clear_all_valid() again and again.\u000a\u000aIt is crazy to repeat set and unset of internal flags. However, we\u000acannot simply get rid of \"sym->flags &= flags | ~SYMBOL_DEF_USER;\"\u000aDoing so would re-introduce the problem solved by commit 5d09598d488f\u000a(\"kconfig: fix new choices being skipped upon config update\").\u000a\u000aTo work around the issue, conf_write_autoconf() stopped calling\u000asym_clear_all_valid().\u000a\u000aconf_write() must be changed accordingly. Currently, it clears\u000aSYMBOL_WRITE after the symbol is written into the .config file. This\u000ais needed to prevent it from writing the same symbol multiple times in\u000acase the symbol is declared in two or more locations. I added the new\u000aflag SYMBOL_WRITTEN, to track the symbols that have been written.\u000a\u000aAnyway, this is a cheesy workaround in order to suppress the issue\u000aas far as defconfig is concerned.\u000a\u000aHandling of choices is totally broken. sym_clear_all_valid() is called\u000aevery time a user touches a symbol from the GUI interface. To reproduce\u000ait, just add a new symbol drivers/usb/gadget/legacy/Kconfig, then touch\u000aaround unrelated symbols from menuconfig. USB_FUNCTIONFS will disappear\u000afrom the .config file.\u000a\u000aI added the Fixes tag since it is more fatal than before. But, this\u000ahas been broken since long long time before, and still it is.\u000aWe should take a closer look to fix this correctly somehow.\u000a\u000aFixes: 00c864f8903d (\"kconfig: allow all config targets to write auto.conf if missing\")\u000aCc: linux-stable # 4.19+\u000aReported-by: Joonas Kylmälä \u000aSigned-off-by: Masahiro Yamada \u000aTested-by: Joonas Kylmälä \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "ea3f1487159894501d1d3a1e120e826e24d3b3a3", "msg" : "kconfig: fix missing choice values in auto.conf", "paths" : [ { "editType" : "edit", "file" : "scripts/kconfig/expr.h" }, { "editType" : "edit", "file" : "scripts/kconfig/confdata.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/gemini-dlink-dir-685.dts" ], "commitId" : "4c64814abe29c823d9c91818d13996ae5dc81544", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ARM: dts: gemini: Set DIR-685 SPI CS as active low\u000a\u000acommit f90b8fda3a9d72a9422ea80ae95843697f94ea4a upstream.\u000a\u000aThe SPI to the display on the DIR-685 is active low, we were\u000ajust saved by the SPI library enforcing active low on everything\u000abefore, so set it as active low to avoid ambiguity.\u000a\u000aLink: https://lore.kernel.org/r/20190715202101.16060-1-linus.walleij@linaro.org\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Linus Walleij \u000aSigned-off-by: Olof Johansson \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "4c64814abe29c823d9c91818d13996ae5dc81544", "msg" : "ARM: dts: gemini: Set DIR-685 SPI CS as active low", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/gemini-dlink-dir-685.dts" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/drm/nouveau/nvkm/subdev/i2c/base.c" ], "commitId" : "8e74f324ea0042002157b1235156e1ef2d20c0f4", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/nouveau/i2c: Enable i2c pads & busses during preinit\u000a\u000acommit 7cb95eeea6706c790571042a06782e378b2561ea upstream.\u000a\u000aIt turns out that while disabling i2c bus access from software when the\u000aGPU is suspended was a step in the right direction with:\u000a\u000acommit 342406e4fbba (\"drm/nouveau/i2c: Disable i2c bus access after\u000a->fini()\")\u000a\u000aWe also ended up accidentally breaking the vbios init scripts on some\u000aolder Tesla GPUs, as apparently said scripts can actually use the i2c\u000abus. Since these scripts are executed before initializing any\u000asubdevices, we end up failing to acquire access to the i2c bus which has\u000aleft a number of cards with their fan controllers uninitialized. Luckily\u000athis doesn't break hardware - it just means the fan gets stuck at 100%.\u000a\u000aThis also means that we've always been using our i2c busses before\u000ainitializing them during the init scripts for older GPUs, we just didn't\u000anotice it until we started preventing them from being used until init.\u000aIt's pretty impressive this never caused us any issues before!\u000a\u000aSo, fix this by initializing our i2c pad and busses during subdev\u000apre-init. We skip initializing aux busses during pre-init, as those are\u000aguaranteed to only ever be used by nouveau for DP aux transactions.\u000a\u000aSigned-off-by: Lyude Paul \u000aTested-by: Marc Meledandri \u000aFixes: 342406e4fbba (\"drm/nouveau/i2c: Disable i2c bus access after ->fini()\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Ben Skeggs \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "8e74f324ea0042002157b1235156e1ef2d20c0f4", "msg" : "drm/nouveau/i2c: Enable i2c pads & busses during preinit", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/drm/nouveau/nvkm/subdev/i2c/base.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/padata.c" ], "commitId" : "2b335bac4ff4ca545b7b54b7a7e26f58caf0050b", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "padata: use smp_mb in padata_reorder to avoid orphaned padata jobs\u000a\u000acommit cf144f81a99d1a3928f90b0936accfd3f45c9a0a upstream.\u000a\u000aTesting padata with the tcrypt module on a 5.2 kernel...\u000a\u000a # modprobe tcrypt alg=\"pcrypt(rfc4106(gcm(aes)))\" type=3\u000a # modprobe tcrypt mode=211 sec=1\u000a\u000a...produces this splat:\u000a\u000a INFO: task modprobe:10075 blocked for more than 120 seconds.\u000a Not tainted 5.2.0-base+ #16\u000a modprobe D 0 10075 10064 0x80004080\u000a Call Trace:\u000a ? __schedule+0x4dd/0x610\u000a ? ring_buffer_unlock_commit+0x23/0x100\u000a schedule+0x6c/0x90\u000a schedule_timeout+0x3b/0x320\u000a ? trace_buffer_unlock_commit_regs+0x4f/0x1f0\u000a wait_for_common+0x160/0x1a0\u000a ? wake_up_q+0x80/0x80\u000a { crypto_wait_req } # entries in braces added by hand\u000a { do_one_aead_op }\u000a { test_aead_jiffies }\u000a test_aead_speed.constprop.17+0x681/0xf30 [tcrypt]\u000a do_test+0x4053/0x6a2b [tcrypt]\u000a ? 0xffffffffa00f4000\u000a tcrypt_mod_init+0x50/0x1000 [tcrypt]\u000a ...\u000a\u000aThe second modprobe command never finishes because in padata_reorder,\u000aCPU0's load of reorder_objects is executed before the unlocking store in\u000aspin_unlock_bh(pd->lock), causing CPU0 to miss CPU1's increment:\u000a\u000aCPU0 CPU1\u000a\u000apadata_reorder padata_do_serial\u000a LOAD reorder_objects // 0\u000a INC reorder_objects // 1\u000a padata_reorder\u000a TRYLOCK pd->lock // failed\u000a UNLOCK pd->lock\u000a\u000aCPU0 deletes the timer before returning from padata_reorder and since no\u000aother job is submitted to padata, modprobe waits indefinitely.\u000a\u000aAdd a pair of full barriers to guarantee proper ordering:\u000a\u000aCPU0 CPU1\u000a\u000apadata_reorder padata_do_serial\u000a UNLOCK pd->lock\u000a smp_mb()\u000a LOAD reorder_objects\u000a INC reorder_objects\u000a smp_mb__after_atomic()\u000a padata_reorder\u000a TRYLOCK pd->lock\u000a\u000asmp_mb__after_atomic is needed so the read part of the trylock operation\u000acomes after the INC, as Andrea points out. Thanks also to Andrea for\u000ahelp with writing a litmus test.\u000a\u000aFixes: 16295bec6398 (\"padata: Generic parallelization/serialization interface\")\u000aSigned-off-by: Daniel Jordan \u000aCc: \u000aCc: Andrea Parri \u000aCc: Boqun Feng \u000aCc: Herbert Xu \u000aCc: Paul E. McKenney \u000aCc: Peter Zijlstra \u000aCc: Steffen Klassert \u000aCc: linux-arch@vger.kernel.org\u000aCc: linux-crypto@vger.kernel.org\u000aCc: linux-kernel@vger.kernel.org\u000aSigned-off-by: Herbert Xu \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "2b335bac4ff4ca545b7b54b7a7e26f58caf0050b", "msg" : "padata: use smp_mb in padata_reorder to avoid orphaned padata jobs", "paths" : [ { "editType" : "edit", "file" : "kernel/padata.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/dm-zoned-metadata.c", "drivers/md/dm-zoned.h" ], "commitId" : "842ee766ffebdf9858775579c85a36145f91c6bf", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dm zoned: fix zone state management race\u000a\u000acommit 3b8cafdd5436f9298b3bf6eb831df5eef5ee82b6 upstream.\u000a\u000adm-zoned uses the zone flag DMZ_ACTIVE to indicate that a zone of the\u000abackend device is being actively read or written and so cannot be\u000areclaimed. This flag is set as long as the zone atomic reference\u000acounter is not 0. When this atomic is decremented and reaches 0 (e.g.\u000aon BIO completion), the active flag is cleared and set again whenever\u000athe zone is reused and BIO issued with the atomic counter incremented.\u000aThese 2 operations (atomic inc/dec and flag set/clear) are however not\u000aalways executed atomically under the target metadata mutex lock and\u000athis causes the warning:\u000a\u000aWARN_ON(!test_bit(DMZ_ACTIVE, &zone->flags));\u000a\u000ain dmz_deactivate_zone() to be displayed. This problem is regularly\u000atriggered with xfstests generic/209, generic/300, generic/451 and\u000axfs/077 with XFS being used as the file system on the dm-zoned target\u000adevice. Similarly, xfstests ext4/303, ext4/304, generic/209 and\u000ageneric/300 trigger the warning with ext4 use.\u000a\u000aThis problem can be easily fixed by simply removing the DMZ_ACTIVE flag\u000aand managing the \"ACTIVE\" state by directly looking at the reference\u000acounter value. To do so, the functions dmz_activate_zone() and\u000admz_deactivate_zone() are changed to inline functions respectively\u000acalling atomic_inc() and atomic_dec(), while the dmz_is_active() macro\u000ais changed to an inline function calling atomic_read().\u000a\u000aFixes: 3b1a94c88b79 (\"dm zoned: drive-managed zoned block device target\")\u000aCc: stable@vger.kernel.org\u000aReported-by: Masato Suzuki \u000aSigned-off-by: Damien Le Moal \u000aSigned-off-by: Mike Snitzer \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "842ee766ffebdf9858775579c85a36145f91c6bf", "msg" : "dm zoned: fix zone state management race", "paths" : [ { "editType" : "edit", "file" : "drivers/md/dm-zoned-metadata.c" }, { "editType" : "edit", "file" : "drivers/md/dm-zoned.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/xen/events/events_base.c", "include/xen/events.h", "drivers/xen/evtchn.c" ], "commitId" : "ccfc9d9da62232348c3d04b7b222cddb01784522", "timestamp" : 1564125182000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xen/events: fix binding user event channels to cpus\u000a\u000acommit bce5963bcb4f9934faa52be323994511d59fd13c upstream.\u000a\u000aWhen binding an interdomain event channel to a vcpu via\u000aIOCTL_EVTCHN_BIND_INTERDOMAIN not only the event channel needs to be\u000abound, but the affinity of the associated IRQi must be changed, too.\u000aOtherwise the IRQ and the event channel won't be moved to another vcpu\u000ain case the original vcpu they were bound to is going offline.\u000a\u000aCc: # 4.13\u000aFixes: c48f64ab472389df (\"xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to next online VCPU\")\u000aSigned-off-by: Juergen Gross \u000aReviewed-by: Boris Ostrovsky \u000aSigned-off-by: Juergen Gross \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:02 +0200", "id" : "ccfc9d9da62232348c3d04b7b222cddb01784522", "msg" : "xen/events: fix binding user event channels to cpus", "paths" : [ { "editType" : "edit", "file" : "drivers/xen/events/events_base.c" }, { "editType" : "edit", "file" : "include/xen/events.h" }, { "editType" : "edit", "file" : "drivers/xen/evtchn.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/9p/trans_xen.c" ], "commitId" : "36acd9cc5ee09d32c224f92ee12c591a2584eca3", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "9p/xen: Add cleanup path in p9_trans_xen_init\u000a\u000acommit 80a316ff16276b36d0392a8f8b2f63259857ae98 upstream.\u000a\u000aIf xenbus_register_frontend() fails in p9_trans_xen_init,\u000awe should call v9fs_unregister_trans() to do cleanup.\u000a\u000aLink: http://lkml.kernel.org/r/20190430143933.19368-1-yuehaibing@huawei.com\u000aCc: stable@vger.kernel.org\u000aFixes: 868eb122739a (\"xen/9pfs: introduce Xen 9pfs transport driver\")\u000aSigned-off-by: YueHaibing \u000aSigned-off-by: Dominique Martinet \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "36acd9cc5ee09d32c224f92ee12c591a2584eca3", "msg" : "9p/xen: Add cleanup path in p9_trans_xen_init", "paths" : [ { "editType" : "edit", "file" : "net/9p/trans_xen.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/9p/trans_virtio.c" ], "commitId" : "7f235a535b1752e3472a1c2a5bf055210ab0a4fe", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "9p/virtio: Add cleanup path in p9_virtio_init\u000a\u000acommit d4548543fc4ece56c6f04b8586f435fb4fd84c20 upstream.\u000a\u000aKASAN report this:\u000a\u000aBUG: unable to handle kernel paging request at ffffffffa0097000\u000aPGD 3870067 P4D 3870067 PUD 3871063 PMD 2326e2067 PTE 0\u000aOops: 0000 [#1\u000aCPU: 0 PID: 5340 Comm: modprobe Not tainted 5.1.0-rc7+ #25\u000aHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014\u000aRIP: 0010:__list_add_valid+0x10/0x70\u000aCode: c3 48 8b 06 55 48 89 e5 5d 48 39 07 0f 94 c0 0f b6 c0 c3 90 90 90 90 90 90 90 55 48 89 d0 48 8b 52 08 48 89 e5 48 39 f2 75 19 <48> 8b 32 48 39 f0 75 3a\u000a\u000aRSP: 0018:ffffc90000e23c68 EFLAGS: 00010246\u000aRAX: ffffffffa00ad000 RBX: ffffffffa009d000 RCX: 0000000000000000\u000aRDX: ffffffffa0097000 RSI: ffffffffa0097000 RDI: ffffffffa009d000\u000aRBP: ffffc90000e23c68 R08: 0000000000000001 R09: 0000000000000000\u000aR10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa0097000\u000aR13: ffff888231797180 R14: 0000000000000000 R15: ffffc90000e23e78\u000aFS: 00007fb215285540(0000) GS:ffff888237a00000(0000) knlGS:0000000000000000\u000aCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000aCR2: ffffffffa0097000 CR3: 000000022f144000 CR4: 00000000000006f0\u000aCall Trace:\u000a v9fs_register_trans+0x2f/0x60 [9pnet\u000a ? 0xffffffffa0087000\u000a p9_virtio_init+0x25/0x1000 [9pnet_virtio\u000a do_one_initcall+0x6c/0x3cc\u000a ? kmem_cache_alloc_trace+0x248/0x3b0\u000a do_init_module+0x5b/0x1f1\u000a load_module+0x1db1/0x2690\u000a ? m_show+0x1d0/0x1d0\u000a __do_sys_finit_module+0xc5/0xd0\u000a __x64_sys_finit_module+0x15/0x20\u000a do_syscall_64+0x6b/0x1d0\u000a entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000aRIP: 0033:0x7fb214d8e839\u000aCode: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01\u000a\u000aRSP: 002b:00007ffc96554278 EFLAGS: 00000246 ORIG_RAX: 0000000000000139\u000aRAX: ffffffffffffffda RBX: 000055e67eed2aa0 RCX: 00007fb214d8e839\u000aRDX: 0000000000000000 RSI: 000055e67ce95c2e RDI: 0000000000000003\u000aRBP: 000055e67ce95c2e R08: 0000000000000000 R09: 000055e67eed2aa0\u000aR10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000\u000aR13: 000055e67eeda500 R14: 0000000000040000 R15: 000055e67eed2aa0\u000aModules linked in: 9pnet_virtio(+) 9pnet gre rfkill vmw_vsock_virtio_transport_common vsock [last unloaded: 9pnet_virtio\u000aCR2: ffffffffa0097000\u000a---[ end trace 4a52bb13ff07b761\u000a\u000aIf register_virtio_driver() fails in p9_virtio_init,\u000awe should call v9fs_unregister_trans() to do cleanup.\u000a\u000aLink: http://lkml.kernel.org/r/20190430115942.41840-1-yuehaibing@huawei.com\u000aCc: stable@vger.kernel.org\u000aReported-by: Hulk Robot \u000aFixes: b530cc794024 (\"9p: add virtio transport\")\u000aSigned-off-by: YueHaibing \u000aSigned-off-by: Dominique Martinet \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "7f235a535b1752e3472a1c2a5bf055210ab0a4fe", "msg" : "9p/virtio: Add cleanup path in p9_virtio_init", "paths" : [ { "editType" : "edit", "file" : "net/9p/trans_virtio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/wireless/ralink/rt2x00/rt2x00usb.c" ], "commitId" : "bbe756698af485b9bfd84c29e65637bfe4960892", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rt2x00usb: fix rx queue hang\u000a\u000acommit 41a531ffa4c5aeb062f892227c00fabb3b4a9c91 upstream.\u000a\u000aSince commit ed194d136769 (\"usb: core: remove local_irq_save() around\u000a ->complete() handler\") the handler rt2x00usb_interrupt_rxdone() is\u000anot running with interrupts disabled anymore. So this completion handler\u000ais not guaranteed to run completely before workqueue processing starts\u000afor the same queue entry.\u000aBe sure to set all other flags in the entry correctly before marking\u000athis entry ready for workqueue processing. This way we cannot miss error\u000aconditions that need to be signalled from the completion handler to the\u000aworker thread.\u000aNote that rt2x00usb_work_rxdone() processes all available entries, not\u000aonly such for which queue_work() was called.\u000a\u000aThis patch is similar to what commit df71c9cfceea (\"rt2x00: fix order\u000aof entry flags modification\") did for TX processing.\u000a\u000aThis fixes a regression on a RT5370 based wifi stick in AP mode, which\u000asuddenly stopped data transmission after some period of heavy load. Also\u000astopping the hanging hostapd resulted in the error message \"ieee80211\u000aphy0: rt2x00queue_flush_queue: Warning - Queue 14 failed to flush\".\u000aOther operation modes are probably affected as well, this just was\u000athe used testcase.\u000a\u000aFixes: ed194d136769 (\"usb: core: remove local_irq_save() around ->complete() handler\")\u000aCc: stable@vger.kernel.org # 4.20+\u000aSigned-off-by: Soeren Moch \u000aAcked-by: Stanislaw Gruszka \u000aSigned-off-by: Kalle Valo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "bbe756698af485b9bfd84c29e65637bfe4960892", "msg" : "rt2x00usb: fix rx queue hang", "paths" : [ { "editType" : "edit", "file" : "drivers/net/wireless/ralink/rt2x00/rt2x00usb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kernel/mpparse.c" ], "commitId" : "7a45c6833e2dd14749667464f64e6972dc99f572", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "x86/boot: Fix memory leak in default_get_smp_config()\u000a\u000acommit e74bd96989dd42a51a73eddb4a5510a6f5e42ac3 upstream.\u000a\u000aWhen default_get_smp_config() is called with early == 1 and mpf->feature1\u000ais non-zero, mpf is leaked because the return path does not do\u000aearly_memunmap().\u000a\u000aFix this and share a common exit routine.\u000a\u000aFixes: 5997efb96756 (\"x86/boot: Use memremap() to map the MPF and MPC data\")\u000aReported-by: Cfir Cohen \u000aSigned-off-by: David Rientjes \u000aSigned-off-by: Thomas Gleixner \u000aCc: stable@vger.kernel.org\u000aLink: https://lkml.kernel.org/r/alpine.DEB.2.21.1907091942570.28240@chino.kir.corp.google.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "7a45c6833e2dd14749667464f64e6972dc99f572", "msg" : "x86/boot: Fix memory leak in default_get_smp_config()", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kernel/mpparse.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/events/intel/core.c" ], "commitId" : "f7aa77ced56b9800cb6c79ea3eba880d93ee23bf", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/x86/intel: Fix spurious NMI on fixed counter\u000a\u000acommit e4557c1a46b0d32746bd309e1941914b5a6912b4 upstream.\u000a\u000aIf a user first sample a PEBS event on a fixed counter, then sample a\u000anon-PEBS event on the same fixed counter on Icelake, it will trigger\u000aspurious NMI. For example:\u000a\u000a perf record -e 'cycles:p' -a\u000a perf record -e 'cycles' -a\u000a\u000aThe error message for spurious NMI:\u000a\u000a [June 21 15:38] Uhhuh. NMI received for unknown reason 30 on CPU 2.\u000a [ +0.000000] Do you have a strange power saving mode enabled?\u000a [ +0.000000] Dazed and confused, but trying to continue\u000a\u000aThe bug was introduced by the following commit:\u000a\u000a commit 6f55967ad9d9 (\"perf/x86/intel: Fix race in intel_pmu_disable_event()\")\u000a\u000aThe commit moves the intel_pmu_pebs_disable() after intel_pmu_disable_fixed(),\u000awhich returns immediately. The related bit of PEBS_ENABLE MSR will never be\u000acleared for the fixed counter. Then a non-PEBS event runs on the fixed counter,\u000abut the bit on PEBS_ENABLE is still set, which triggers spurious NMIs.\u000a\u000aCheck and disable PEBS for fixed counters after intel_pmu_disable_fixed().\u000a\u000aReported-by: Yi, Ammy \u000aSigned-off-by: Kan Liang \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aAcked-by: Jiri Olsa \u000aCc: \u000aCc: Alexander Shishkin \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Stephane Eranian \u000aCc: Thomas Gleixner \u000aCc: Vince Weaver \u000aFixes: 6f55967ad9d9 (\"perf/x86/intel: Fix race in intel_pmu_disable_event()\")\u000aLink: https://lkml.kernel.org/r/20190625142135.22112-1-kan.liang@linux.intel.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "f7aa77ced56b9800cb6c79ea3eba880d93ee23bf", "msg" : "perf/x86/intel: Fix spurious NMI on fixed counter", "paths" : [ { "editType" : "edit", "file" : "arch/x86/events/intel/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/events/amd/uncore.c" ], "commitId" : "3e1b297ed547986bdbce3d08a359349d68fdd863", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/x86/amd/uncore: Do not set 'ThreadMask' and 'SliceMask' for non-L3 PMCs\u000a\u000acommit 16f4641166b10e199f0d7b68c2c5f004fef0bda3 upstream.\u000a\u000aThe following commit:\u000a\u000a d7cbbe49a930 (\"perf/x86/amd/uncore: Set ThreadMask and SliceMask for L3 Cache perf events\")\u000a\u000aenables L3 PMC events for all threads and slices by writing 1's in\u000a'ChL3PmcCfg' (L3 PMC PERF_CTL) register fields.\u000a\u000aThose bitfields overlap with high order event select bits in the Data\u000aFabric PMC control register, however.\u000a\u000aSo when a user requests raw Data Fabric events (-e amd_df/event=0xYYY/),\u000athe two highest order bits get inadvertently set, changing the counter\u000aselect to events that don't exist, and for which no counts are read.\u000a\u000aThis patch changes the logic to write the L3 masks only when dealing\u000awith L3 PMC counters.\u000a\u000aAMD Family 16h and below Northbridge (NB) counters were not affected.\u000a\u000aSigned-off-by: Kim Phillips \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: \u000aCc: Alexander Shishkin \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Borislav Petkov \u000aCc: Gary Hook \u000aCc: H. Peter Anvin \u000aCc: Janakarajan Natarajan \u000aCc: Jiri Olsa \u000aCc: Linus Torvalds \u000aCc: Martin Liska \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aCc: Pu Wen \u000aCc: Stephane Eranian \u000aCc: Suravee Suthikulpanit \u000aCc: Thomas Gleixner \u000aCc: Vince Weaver \u000aFixes: d7cbbe49a930 (\"perf/x86/amd/uncore: Set ThreadMask and SliceMask for L3 Cache perf events\")\u000aLink: https://lkml.kernel.org/r/20190628215906.4276-1-kim.phillips@amd.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "3e1b297ed547986bdbce3d08a359349d68fdd863", "msg" : "perf/x86/amd/uncore: Do not set 'ThreadMask' and 'SliceMask' for non-L3 PMCs", "paths" : [ { "editType" : "edit", "file" : "arch/x86/events/amd/uncore.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/events/amd/uncore.c" ], "commitId" : "e457f13e1f4b2f9171d3aeafbea390e0e6d0a386", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/x86/amd/uncore: Set the thread mask for F17h L3 PMCs\u000a\u000acommit 2f217d58a8a086d3399fecce39fb358848e799c4 upstream.\u000a\u000aFill in the L3 performance event select register ThreadMask\u000abitfield, to enable per hardware thread accounting.\u000a\u000aSigned-off-by: Kim Phillips \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: \u000aCc: Alexander Shishkin \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Borislav Petkov \u000aCc: Gary Hook \u000aCc: H. Peter Anvin \u000aCc: Janakarajan Natarajan \u000aCc: Jiri Olsa \u000aCc: Linus Torvalds \u000aCc: Martin Liska \u000aCc: Namhyung Kim \u000aCc: Peter Zijlstra \u000aCc: Pu Wen \u000aCc: Stephane Eranian \u000aCc: Suravee Suthikulpanit \u000aCc: Thomas Gleixner \u000aCc: Vince Weaver \u000aLink: https://lkml.kernel.org/r/20190628215906.4276-2-kim.phillips@amd.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "e457f13e1f4b2f9171d3aeafbea390e0e6d0a386", "msg" : "perf/x86/amd/uncore: Set the thread mask for F17h L3 PMCs", "paths" : [ { "editType" : "edit", "file" : "arch/x86/events/amd/uncore.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/drm/drm_displayid.h", "drivers/gpu/drm/drm_edid.c" ], "commitId" : "9949a9002e06bd921eefa1fd8cf675597612c385", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "drm/edid: parse CEA blocks embedded in DisplayID\u000a\u000acommit e28ad544f462231d3fd081a7316339359efbb481 upstream.\u000a\u000aDisplayID blocks allow embedding of CEA blocks. The payloads are\u000aidentical to traditional top level CEA extension blocks, but the header\u000ais slightly different.\u000a\u000aThis change allows the CEA parser to find a CEA block inside a DisplayID\u000ablock. Additionally, it adds support for parsing the embedded CTA\u000aheader. No further changes are necessary due to payload parity.\u000a\u000aThis change fixes audio support for the Valve Index HMD.\u000a\u000aSigned-off-by: Andres Rodriguez \u000aReviewed-by: Dave Airlie \u000aCc: Jani Nikula \u000aCc: # v4.15\u000aSigned-off-by: Dave Airlie \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20190619180901.17901-1-andresx7@gmail.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "9949a9002e06bd921eefa1fd8cf675597612c385", "msg" : "drm/edid: parse CEA blocks embedded in DisplayID", "paths" : [ { "editType" : "edit", "file" : "include/drm/drm_displayid.h" }, { "editType" : "edit", "file" : "drivers/gpu/drm/drm_edid.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/bio.c" ], "commitId" : "397918f63afdf277dd044a22ffdfd0d686e340d4", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "block: Allow mapping of vmalloc-ed buffers\u000a\u000acommit b4c5875d36178e8df409bdce232f270cac89fafe upstream.\u000a\u000aTo allow the SCSI subsystem scsi_execute_req() function to issue\u000arequests using large buffers that are better allocated with vmalloc()\u000arather than kmalloc(), modify bio_map_kern() to allow passing a buffer\u000aallocated with vmalloc().\u000a\u000aTo do so, detect vmalloc-ed buffers using is_vmalloc_addr(). For\u000avmalloc-ed buffers, flush the buffer using flush_kernel_vmap_range(),\u000ause vmalloc_to_page() instead of virt_to_page() to obtain the pages of\u000athe buffer, and invalidate the buffer addresses with\u000ainvalidate_kernel_vmap_range() on completion of read BIOs. This last\u000apoint is executed using the function bio_invalidate_vmalloc_pages()\u000awhich is defined only if the architecture defines\u000aARCH_HAS_FLUSH_KERNEL_DCACHE_PAGE, that is, if the architecture\u000aactually needs the invalidation done.\u000a\u000aFixes: 515ce6061312 (\"scsi: sd_zbc: Fix sd_zbc_report_zones() buffer allocation\")\u000aFixes: e76239a3748c (\"block: add a report_zones method\")\u000aCc: stable@vger.kernel.org\u000aReviewed-by: Martin K. Petersen \u000aSigned-off-by: Damien Le Moal \u000aReviewed-by: Christoph Hellwig \u000aReviewed-by: Chaitanya Kulkarni \u000aReviewed-by: Ming Lei \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "397918f63afdf277dd044a22ffdfd0d686e340d4", "msg" : "block: Allow mapping of vmalloc-ed buffers", "paths" : [ { "editType" : "edit", "file" : "block/bio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/blkdev.h", "block/blk-zoned.c" ], "commitId" : "c1bbef41db5816913e3e1fa10f2c4ddae8dd0b50", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "block: Fix potential overflow in blk_report_zones()\u000a\u000acommit 113ab72ed4794c193509a97d7c6d32a6886e1682 upstream.\u000a\u000aFor large values of the number of zones reported and/or large zone\u000asizes, the sector increment calculated with\u000a\u000ablk_queue_zone_sectors(q) * n\u000a\u000ain blk_report_zones() loop can overflow the unsigned int type used for\u000athe calculation as both \"n\" and blk_queue_zone_sectors() value are\u000aunsigned int. E.g. for a device with 256 MB zones (524288 sectors),\u000aoverflow happens with 8192 or more zones reported.\u000a\u000aChanging the return type of blk_queue_zone_sectors() to sector_t, fixes\u000athis problem and avoids overflow problem for all other callers of this\u000ahelper too. The same change is also applied to the bdev_zone_sectors()\u000ahelper.\u000a\u000aFixes: e76239a3748c (\"block: add a report_zones method\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Damien Le Moal \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "c1bbef41db5816913e3e1fa10f2c4ddae8dd0b50", "msg" : "block: Fix potential overflow in blk_report_zones()", "paths" : [ { "editType" : "edit", "file" : "block/blk-zoned.c" }, { "editType" : "edit", "file" : "include/linux/blkdev.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/infiniband/ulp/srp/ib_srp.c" ], "commitId" : "2cb0539095b4cce84110f3e210f421176f6bb62b", "timestamp" : 1564125183000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "RDMA/srp: Accept again source addresses that do not have a port number\u000a\u000acommit bcef5b7215681250c4bf8961dfe15e9e4fef97d0 upstream.\u000a\u000aThe function srp_parse_in() is used both for parsing source address\u000aspecifications and for target address specifications. Target addresses\u000amust have a port number. Having to specify a port number for source\u000aaddresses is inconvenient. Make sure that srp_parse_in() supports again\u000aparsing addresses with no port number.\u000a\u000aCc: \u000aFixes: c62adb7def71 (\"IB/srp: Fix IPv6 address parsing\")\u000aSigned-off-by: Bart Van Assche \u000aSigned-off-by: Jason Gunthorpe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:03 +0200", "id" : "2cb0539095b4cce84110f3e210f421176f6bb62b", "msg" : "RDMA/srp: Accept again source addresses that do not have a port number", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/ulp/srp/ib_srp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hwtracing/intel_th/pci.c" ], "commitId" : "68d2b51d5d8d2edf1f6373b2d17d5dff5d474b67", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "intel_th: pci: Add Ice Lake NNPI support\u000a\u000acommit 4aa5aed2b6f267592705a526f57518a5d715b769 upstream.\u000a\u000aThis adds Ice Lake NNPI support to the Intel(R) Trace Hub.\u000a\u000aSigned-off-by: Alexander Shishkin \u000aReviewed-by: Andy Shevchenko \u000aCc: stable \u000aLink: https://lore.kernel.org/r/20190621161930.60785-5-alexander.shishkin@linux.intel.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "68d2b51d5d8d2edf1f6373b2d17d5dff5d474b67", "msg" : "intel_th: pci: Add Ice Lake NNPI support", "paths" : [ { "editType" : "edit", "file" : "drivers/hwtracing/intel_th/pci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pci/controller/pci-hyperv.c" ], "commitId" : "d3fbb2a14a29c0beac6f077bddcbe09aa4d81229", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "PCI: hv: Fix a use-after-free bug in hv_eject_device_work()\u000a\u000acommit 4df591b20b80cb77920953812d894db259d85bd7 upstream.\u000a\u000aFix a use-after-free in hv_eject_device_work().\u000a\u000aFixes: 05f151a73ec2 (\"PCI: hv: Fix a memory leak in hv_eject_device_work()\")\u000aSigned-off-by: Dexuan Cui \u000aSigned-off-by: Lorenzo Pieralisi \u000aReviewed-by: Michael Kelley \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "d3fbb2a14a29c0beac6f077bddcbe09aa4d81229", "msg" : "PCI: hv: Fix a use-after-free bug in hv_eject_device_work()", "paths" : [ { "editType" : "edit", "file" : "drivers/pci/controller/pci-hyperv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pci/pci.c" ], "commitId" : "e67c8a7e94f56f8dda15985023471de9db55309a", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "PCI: Do not poll for PME if the device is in D3cold\u000a\u000acommit 000dd5316e1c756a1c028f22e01d06a38249dd4d upstream.\u000a\u000aPME polling does not take into account that a device that is directly\u000aconnected to the host bridge may go into D3cold as well. This leads to a\u000asituation where the PME poll thread reads from a config space of a\u000adevice that is in D3cold and gets incorrect information because the\u000aconfig space is not accessible.\u000a\u000aHere is an example from Intel Ice Lake system where two PCIe root ports\u000aare in D3cold (I've instrumented the kernel to log the PMCSR register\u000acontents):\u000a\u000a [ 62.971442] pcieport 0000:00:07.1: Check PME status, PMCSR=0xffff\u000a [ 62.971504] pcieport 0000:00:07.0: Check PME status, PMCSR=0xffff\u000a\u000aSince 0xffff is interpreted so that PME is pending, the root ports will\u000abe runtime resumed. This repeats over and over again essentially\u000ablocking all runtime power management.\u000a\u000aPrevent this from happening by checking whether the device is in D3cold\u000abefore its PME status is read.\u000a\u000aFixes: 71a83bd727cc (\"PCI/PM: add runtime PM support to PCIe port\")\u000aSigned-off-by: Mika Westerberg \u000aReviewed-by: Lukas Wunner \u000aCc: 3.6+ # v3.6+\u000aSigned-off-by: Rafael J. Wysocki \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "e67c8a7e94f56f8dda15985023471de9db55309a", "msg" : "PCI: Do not poll for PME if the device is in D3cold", "paths" : [ { "editType" : "edit", "file" : "drivers/pci/pci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/pci/controller/dwc/pcie-qcom.c" ], "commitId" : "97392d4bac46324a8356788bbb3adc401786c323", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "PCI: qcom: Ensure that PERST is asserted for at least 100 ms\u000a\u000acommit 64adde31c8e996a6db6f7a1a4131180e363aa9f2 upstream.\u000a\u000aCurrently, there is only a 1 ms sleep after asserting PERST.\u000a\u000aReading the datasheets for different endpoints, some require PERST to be\u000aasserted for 10 ms in order for the endpoint to perform a reset, others\u000arequire it to be asserted for 50 ms.\u000a\u000aSeveral SoCs using this driver uses PCIe Mini Card, where we don't know\u000awhat endpoint will be plugged in.\u000a\u000aThe PCI Express Card Electromechanical Specification r2.0, section\u000a2.2, \"PERST# Signal\" specifies:\u000a\u000a\"On power up, the deassertion of PERST# is delayed 100 ms (TPVPERL) from\u000athe power rails achieving specified operating limits.\"\u000a\u000aAdd a sleep of 100 ms before deasserting PERST, in order to ensure that\u000awe are compliant with the spec.\u000a\u000aFixes: 82a823833f4e (\"PCI: qcom: Add Qualcomm PCIe controller driver\")\u000aSigned-off-by: Niklas Cassel \u000aSigned-off-by: Lorenzo Pieralisi \u000aAcked-by: Stanimir Varbanov \u000aCc: stable@vger.kernel.org # 4.5+\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "97392d4bac46324a8356788bbb3adc401786c323", "msg" : "PCI: qcom: Ensure that PERST is asserted for at least 100 ms", "paths" : [ { "editType" : "edit", "file" : "drivers/pci/controller/dwc/pcie-qcom.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/btrfs/tree-log.c" ], "commitId" : "79906804d77788696726000519657897f2831fbf", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Btrfs: fix data loss after inode eviction, renaming it, and fsync it\u000a\u000acommit d1d832a0b51dd9570429bb4b81b2a6c1759e681a upstream.\u000a\u000aWhen we log an inode, regardless of logging it completely or only that it\u000aexists, we always update it as logged (logged_trans and last_log_commit\u000afields of the inode are updated). This is generally fine and avoids future\u000aattempts to log it from having to do repeated work that brings no value.\u000a\u000aHowever, if we write data to a file, then evict its inode after all the\u000adealloc was flushed (and ordered extents completed), rename the file and\u000afsync it, we end up not logging the new extents, since the rename may\u000aresult in logging that the inode exists in case the parent directory was\u000alogged before. The following reproducer shows and explains how this can\u000ahappen:\u000a\u000a $ mkfs.btrfs -f /dev/sdb\u000a $ mount /dev/sdb /mnt\u000a\u000a $ mkdir /mnt/dir\u000a $ touch /mnt/dir/foo\u000a $ touch /mnt/dir/bar\u000a\u000a # Do a direct IO write instead of a buffered write because with a\u000a # buffered write we would need to make sure dealloc gets flushed and\u000a # complete before we do the inode eviction later, and we can not do that\u000a # from user space with call to things such as sync(2) since that results\u000a # in a transaction commit as well.\u000a $ xfs_io -d -c \"pwrite -S 0xd3 0 4K\" /mnt/dir/bar\u000a\u000a # Keep the directory dir in use while we evict inodes. We want our file\u000a # bar's inode to be evicted but we don't want our directory's inode to\u000a # be evicted (if it were evicted too, we would not be able to reproduce\u000a # the issue since the first fsync below, of file foo, would result in a\u000a # transaction commit.\u000a $ ( cd /mnt/dir; while true; do :; done ) &\u000a $ pid=$!\u000a\u000a # Wait a bit to give time for the background process to chdir.\u000a $ sleep 0.1\u000a\u000a # Evict all inodes, except the inode for the directory dir because it is\u000a # currently in use by our background process.\u000a $ echo 2 > /proc/sys/vm/drop_caches\u000a\u000a # fsync file foo, which ends up persisting information about the parent\u000a # directory because it is a new inode.\u000a $ xfs_io -c fsync /mnt/dir/foo\u000a\u000a # Rename bar, this results in logging that this inode exists (inode item,\u000a # names, xattrs) because the parent directory is in the log.\u000a $ mv /mnt/dir/bar /mnt/dir/baz\u000a\u000a # Now fsync baz, which ends up doing absolutely nothing because of the\u000a # rename operation which logged that the inode exists only.\u000a $ xfs_io -c fsync /mnt/dir/baz\u000a\u000a \u000a\u000a $ mount /dev/sdb /mnt\u000a $ od -t x1 -A d /mnt/dir/baz\u000a 0000000\u000a\u000a --> Empty file, data we wrote is missing.\u000a\u000aFix this by not updating last_sub_trans of an inode when we are logging\u000aonly that it exists and the inode was not yet logged since it was loaded\u000afrom disk (full_sync bit set), this is enough to make btrfs_inode_in_log()\u000areturn false for this scenario and make us log the inode. The logged_trans\u000aof the inode is still always setsince that alone is used to track if names\u000aneed to be deleted as part of unlink operations.\u000a\u000aFixes: 257c62e1bce03e (\"Btrfs: avoid tree log commit when there are no changes\")\u000aCC: stable@vger.kernel.org # 4.4+\u000aSigned-off-by: Filipe Manana \u000aSigned-off-by: David Sterba \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "79906804d77788696726000519657897f2831fbf", "msg" : "Btrfs: fix data loss after inode eviction, renaming it, and fsync it", "paths" : [ { "editType" : "edit", "file" : "fs/btrfs/tree-log.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/btrfs/tree-log.c" ], "commitId" : "82e85ad024d7244e451f0e24ed39b9255bed440a", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Btrfs: fix fsync not persisting dentry deletions due to inode evictions\u000a\u000acommit 803f0f64d17769071d7287d9e3e3b79a3e1ae937 upstream.\u000a\u000aIn order to avoid searches on a log tree when unlinking an inode, we check\u000aif the inode being unlinked was logged in the current transaction, as well\u000aas the inode of its parent directory. When any of the inodes are logged,\u000awe proceed to delete directory items and inode reference items from the\u000alog, to ensure that if a subsequent fsync of only the inode being unlinked\u000aor only of the parent directory when the other is not fsync'ed as well,\u000adoes not result in the entry still existing after a power failure.\u000a\u000aThat check however is not reliable when one of the inodes involved (the\u000aone being unlinked or its parent directory's inode) is evicted, since the\u000alogged_trans field is transient, that is, it is not stored on disk, so it\u000ais lost when the inode is evicted and loaded into memory again (which is\u000aset to zero on load). As a consequence the checks currently being done by\u000abtrfs_del_dir_entries_in_log() and btrfs_del_inode_ref_in_log() always\u000areturn true if the inode was evicted before, regardless of the inode\u000ahaving been logged or not before (and in the current transaction), this\u000aresults in the dentry being unlinked still existing after a log replay\u000aif after the unlink operation only one of the inodes involved is fsync'ed.\u000a\u000aExample:\u000a\u000a $ mkfs.btrfs -f /dev/sdb\u000a $ mount /dev/sdb /mnt\u000a\u000a $ mkdir /mnt/dir\u000a $ touch /mnt/dir/foo\u000a $ xfs_io -c fsync /mnt/dir/foo\u000a\u000a # Keep an open file descriptor on our directory while we evict inodes.\u000a # We just want to evict the file's inode, the directory's inode must not\u000a # be evicted.\u000a $ ( cd /mnt/dir; while true; do :; done ) &\u000a $ pid=$!\u000a\u000a # Wait a bit to give time to background process to chdir to our test\u000a # directory.\u000a $ sleep 0.5\u000a\u000a # Trigger eviction of the file's inode.\u000a $ echo 2 > /proc/sys/vm/drop_caches\u000a\u000a # Unlink our file and fsync the parent directory. After a power failure\u000a # we don't expect to see the file anymore, since we fsync'ed the parent\u000a # directory.\u000a $ rm -f $SCRATCH_MNT/dir/foo\u000a $ xfs_io -c fsync /mnt/dir\u000a\u000a \u000a\u000a $ mount /dev/sdb /mnt\u000a $ ls /mnt/dir\u000a foo\u000a $\u000a --> file still there, unlink not persisted despite explicit fsync on dir\u000a\u000aFix this by checking if the inode has the full_sync bit set in its runtime\u000aflags as well, since that bit is set everytime an inode is loaded from\u000adisk, or for other less common cases such as after a shrinking truncate\u000aor failure to allocate extent maps for holes, and gets cleared after the\u000afirst fsync. Also consider the inode as possibly logged only if it was\u000alast modified in the current transaction (besides having the full_fsync\u000aflag set).\u000a\u000aFixes: 3a5f1d458ad161 (\"Btrfs: Optimize btree walking while logging inodes\")\u000aCC: stable@vger.kernel.org # 4.4+\u000aSigned-off-by: Filipe Manana \u000aSigned-off-by: David Sterba \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "82e85ad024d7244e451f0e24ed39b9255bed440a", "msg" : "Btrfs: fix fsync not persisting dentry deletions due to inode evictions", "paths" : [ { "editType" : "edit", "file" : "fs/btrfs/tree-log.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/btrfs/file.c" ], "commitId" : "55d036c11bbe22b1576d08250481ea340d3d1b6c", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Btrfs: add missing inode version, ctime and mtime updates when punching hole\u000a\u000acommit 179006688a7e888cbff39577189f2e034786d06a upstream.\u000a\u000aIf the range for which we are punching a hole covers only part of a page,\u000awe end up updating the inode item but we skip the update of the inode's\u000aiversion, mtime and ctime. Fix that by ensuring we update those properties\u000aof the inode.\u000a\u000aA patch for fstests test case generic/059 that tests this as been sent\u000aalong with this fix.\u000a\u000aFixes: 2aaa66558172b0 (\"Btrfs: add hole punching\")\u000aFixes: e8c1c76e804b18 (\"Btrfs: add missing inode update when punching hole\")\u000aCC: stable@vger.kernel.org # 4.4+\u000aSigned-off-by: Filipe Manana \u000aSigned-off-by: David Sterba \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "55d036c11bbe22b1576d08250481ea340d3d1b6c", "msg" : "Btrfs: add missing inode version, ctime and mtime updates when punching hole", "paths" : [ { "editType" : "edit", "file" : "fs/btrfs/file.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/rdma/ib_verbs.h", "drivers/infiniband/hw/mlx5/main.c" ], "commitId" : "7211b04064474ae016c52e8b068a212c815f94ca", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "IB/mlx5: Report correctly tag matching rendezvous capability\u000a\u000acommit 89705e92700170888236555fe91b45e4c1bb0985 upstream.\u000a\u000aUserspace expects the IB_TM_CAP_RC bit to indicate that the device\u000asupports RC transport tag matching with rendezvous offload. However the\u000afirmware splits this into two capabilities for eager and rendezvous tag\u000amatching.\u000a\u000aOnly if the FW supports both modes should userspace be told the tag\u000amatching capability is available.\u000a\u000aCc: # 4.13\u000aFixes: eb761894351d (\"IB/mlx5: Fill XRQ capabilities\")\u000aSigned-off-by: Danit Goldberg \u000aReviewed-by: Yishai Hadas \u000aReviewed-by: Artemy Kovalyov \u000aSigned-off-by: Leon Romanovsky \u000aSigned-off-by: Jason Gunthorpe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "7211b04064474ae016c52e8b068a212c815f94ca", "msg" : "IB/mlx5: Report correctly tag matching rendezvous capability", "paths" : [ { "editType" : "edit", "file" : "drivers/infiniband/hw/mlx5/main.c" }, { "editType" : "edit", "file" : "include/rdma/ib_verbs.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/wacom_wac.h", "drivers/hid/wacom_sys.c", "drivers/hid/wacom_wac.c" ], "commitId" : "f9c9c9a20c39e5f947c79a7c205289a80f98e0fa", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: wacom: generic: only switch the mode on devices with LEDs\u000a\u000acommit d8e9806005f28bbb49899dab2068e3359e22ba35 upstream.\u000a\u000aCurrently, the driver will attempt to set the mode on all\u000adevices with a center button, but some devices with a center\u000abutton lack LEDs, and attempting to set the LEDs on devices\u000awithout LEDs results in the kernel error message of the form:\u000a\u000a\"leds input8::wacom-0.1: Setting an LED's brightness failed (-32)\"\u000a\u000aThis is because the generic codepath erroneously assumes that the\u000aBUTTON_CENTER usage indicates that the device has LEDs, the\u000apreviously ignored TOUCH_RING_SETTING usage is a more accurate\u000aindication of the existence of LEDs on the device.\u000a\u000aFixes: 10c55cacb8b2 (\"HID: wacom: generic: support LEDs\")\u000aCc: # v4.11+\u000aSigned-off-by: Aaron Armstrong Skomra \u000aReviewed-by: Jason Gerecke \u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "f9c9c9a20c39e5f947c79a7c205289a80f98e0fa", "msg" : "HID: wacom: generic: only switch the mode on devices with LEDs", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/wacom_wac.h" }, { "editType" : "edit", "file" : "drivers/hid/wacom_sys.c" }, { "editType" : "edit", "file" : "drivers/hid/wacom_wac.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/wacom_wac.c" ], "commitId" : "2e6ce3040ae6ecf2db791e2a08bdb57e9447496a", "timestamp" : 1564125184000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: wacom: generic: Correct pad syncing\u000a\u000acommit d4b8efeb46d99a5d02e7f88ac4eaccbe49370770 upstream.\u000a\u000aOnly sync the pad once per report, not once per collection.\u000aAlso avoid syncing the pad on battery reports.\u000a\u000aFixes: f8b6a74719b5 (\"HID: wacom: generic: Support multiple tools per report\")\u000aCc: # v4.17+\u000aSigned-off-by: Aaron Armstrong Skomra \u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:04 +0200", "id" : "2e6ce3040ae6ecf2db791e2a08bdb57e9447496a", "msg" : "HID: wacom: generic: Correct pad syncing", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/wacom_wac.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hid/wacom_wac.c" ], "commitId" : "84a7f9ba5a15d095ce4e90f2b2f57303a3560bef", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "HID: wacom: correct touch resolution x/y typo\u000a\u000acommit 68c20cc2164cc5c7c73f8012ae6491afdb1f7f72 upstream.\u000a\u000aThis affects the 2nd-gen Intuos Pro Medium and Large\u000awhen using their Bluetooth connection.\u000a\u000aFixes: 4922cd26f03c (\"HID: wacom: Support 2nd-gen Intuos Pro's Bluetooth classic interface\")\u000aCc: # v4.11+\u000aSigned-off-by: Aaron Armstrong Skomra \u000aReviewed-by: Jason Gerecke \u000aSigned-off-by: Jiri Kosina \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "84a7f9ba5a15d095ce4e90f2b2f57303a3560bef", "msg" : "HID: wacom: correct touch resolution x/y typo", "paths" : [ { "editType" : "edit", "file" : "drivers/hid/wacom_wac.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/iomem.c", "arch/powerpc/include/asm/pgtable.h", "include/linux/mm.h" ], "commitId" : "d08c8b6acc91b0d7cc97a49b813f2e8522c715a8", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mm/nvdimm: add is_ioremap_addr and use that to check ioremap address\u000a\u000acommit 9bd3bb6703d8c0a5fb8aec8e3287bd55b7341dcd upstream.\u000a\u000aArchitectures like powerpc use different address range to map ioremap\u000aand vmalloc range. The memunmap() check used by the nvdimm layer was\u000awrongly using is_vmalloc_addr() to check for ioremap range which fails\u000afor ppc64. This result in ppc64 not freeing the ioremap mapping. The\u000aside effect of this is an unbind failure during module unload with\u000apapr_scm nvdimm driver\u000a\u000aLink: http://lkml.kernel.org/r/20190701134038.14165-1-aneesh.kumar@linux.ibm.com\u000aSigned-off-by: Aneesh Kumar K.V \u000aFixes: b5beae5e224f (\"powerpc/pseries: Add driver for PAPR SCM regions\")\u000aCc: Dan Williams \u000aCc: \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "d08c8b6acc91b0d7cc97a49b813f2e8522c715a8", "msg" : "mm/nvdimm: add is_ioremap_addr and use that to check ioremap address", "paths" : [ { "editType" : "edit", "file" : "kernel/iomem.c" }, { "editType" : "edit", "file" : "arch/powerpc/include/asm/pgtable.h" }, { "editType" : "edit", "file" : "include/linux/mm.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/nvdimm/pfn.h", "drivers/nvdimm/dax_devs.c", "drivers/nvdimm/pfn_devs.c" ], "commitId" : "dabc0942d4fa1fe881f13ba38e941009796af2b7", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "libnvdimm/pfn: fix fsdax-mode namespace info-block zero-fields\u000a\u000acommit 7e3e888dfc138089f4c15a81b418e88f0978f744 upstream.\u000a\u000aAt namespace creation time there is the potential for the \"expected to\u000abe zero\" fields of a 'pfn' info-block to be filled with indeterminate\u000adata. While the kernel buffer is zeroed on allocation it is immediately\u000aoverwritten by nd_pfn_validate() filling it with the current contents of\u000athe on-media info-block location. For fields like, 'flags' and the\u000a'padding' it potentially means that future implementations can not rely on\u000athose fields being zero.\u000a\u000aIn preparation to stop using the 'start_pad' and 'end_trunc' fields for\u000asection alignment, arrange for fields that are not explicitly\u000ainitialized to be guaranteed zero. Bump the minor version to indicate\u000ait is safe to assume the 'padding' and 'flags' are zero. Otherwise,\u000athis corruption is expected to benign since all other critical fields\u000aare explicitly initialized.\u000a\u000aNote The cc: stable is about spreading this new policy to as many\u000akernels as possible not fixing an issue in those kernels. It is not\u000auntil the change titled \"libnvdimm/pfn: Stop padding pmem namespaces to\u000asection alignment\" where this improper initialization becomes a problem.\u000aSo if someone decides to backport \"libnvdimm/pfn: Stop padding pmem\u000anamespaces to section alignment\" (which is not tagged for stable), make\u000asure this pre-requisite is flagged.\u000a\u000aLink: http://lkml.kernel.org/r/156092356065.979959.6681003754765958296.stgit@dwillia2-desk3.amr.corp.intel.com\u000aFixes: 32ab0a3f5170 (\"libnvdimm, pmem: 'struct page' for pmem\")\u000aSigned-off-by: Dan Williams \u000aTested-by: Aneesh Kumar K.V \u0009[ppc64]\u000aCc: \u000aCc: David Hildenbrand \u000aCc: Jane Chu \u000aCc: Jeff Moyer \u000aCc: Jérôme Glisse \u000aCc: Jonathan Corbet \u000aCc: Logan Gunthorpe \u000aCc: Michal Hocko \u000aCc: Mike Rapoport \u000aCc: Oscar Salvador \u000aCc: Pavel Tatashin \u000aCc: Toshi Kani \u000aCc: Vlastimil Babka \u000aCc: Wei Yang \u000aCc: Jason Gunthorpe \u000aCc: Christoph Hellwig \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "dabc0942d4fa1fe881f13ba38e941009796af2b7", "msg" : "libnvdimm/pfn: fix fsdax-mode namespace info-block zero-fields", "paths" : [ { "editType" : "edit", "file" : "drivers/nvdimm/pfn.h" }, { "editType" : "edit", "file" : "drivers/nvdimm/dax_devs.c" }, { "editType" : "edit", "file" : "drivers/nvdimm/pfn_devs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/coda/file.c" ], "commitId" : "54793d5b069729fb7af641d55b653b41ea987864", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "coda: pass the host file in vma->vm_file on mmap\u000a\u000acommit 7fa0a1da3dadfd9216df7745a1331fdaa0940d1c upstream.\u000a\u000aPatch series \"Coda updates\".\u000a\u000aThe following patch series is a collection of various fixes for Coda,\u000amost of which were collected from linux-fsdevel or linux-kernel but\u000awhich have as yet not found their way upstream.\u000a\u000aThis patch (of 22):\u000a\u000aVarious file systems expect that vma->vm_file points at their own file\u000ahandle, several use file_inode(vma->vm_file) to get at their inode or\u000ause vma->vm_file->private_data. However the way Coda wrapped mmap on a\u000ahost file broke this assumption, vm_file was still pointing at the Coda\u000afile and the host file systems would scribble over Coda's inode and\u000aprivate file data.\u000a\u000aThis patch fixes the incorrect expectation and wraps vm_ops->open and\u000avm_ops->close to allow Coda to track when the vm_area_struct is\u000adestroyed so we still release the reference on the Coda file handle at\u000athe right time.\u000a\u000aLink: http://lkml.kernel.org/r/0e850c6e59c0b147dc2dcd51a3af004c948c3697.1558117389.git.jaharkes@cs.cmu.edu\u000aSigned-off-by: Jan Harkes \u000aCc: Arnd Bergmann \u000aCc: Colin Ian King \u000aCc: Dan Carpenter \u000aCc: David Howells \u000aCc: Fabian Frederick \u000aCc: Mikko Rapeli \u000aCc: Sam Protsenko \u000aCc: Yann Droneaud \u000aCc: Zhouyang Jia \u000aCc: \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "54793d5b069729fb7af641d55b653b41ea987864", "msg" : "coda: pass the host file in vma->vm_file on mmap", "paths" : [ { "editType" : "edit", "file" : "fs/coda/file.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/asm-generic/bug.h" ], "commitId" : "bbc6c816b6b919443ea1f150455d95b4de3b231e", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "include/asm-generic/bug.h: fix \"cut here\" for WARN_ON for __WARN_TAINT architectures\u000a\u000acommit 6b15f678fb7d5ef54e089e6ace72f007fe6e9895 upstream.\u000a\u000aFor architectures using __WARN_TAINT, the WARN_ON macro did not print\u000aout the \"cut here\" string. The other WARN_XXX macros would print \"cut\u000ahere\" inside __warn_printk, which is not called for WARN_ON since it\u000adoesn't have a message to print.\u000a\u000aLink: http://lkml.kernel.org/r/20190624154831.163888-1-ddavenport@chromium.org\u000aFixes: a7bed27af194 (\"bug: fix \"cut here\" location for __WARN_TAINT architectures\")\u000aSigned-off-by: Drew Davenport \u000aAcked-by: Kees Cook \u000aTested-by: Kees Cook \u000aCc: \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "bbc6c816b6b919443ea1f150455d95b4de3b231e", "msg" : "include/asm-generic/bug.h: fix \"cut here\" for WARN_ON for __WARN_TAINT architectures", "paths" : [ { "editType" : "edit", "file" : "include/asm-generic/bug.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/resource.c" ], "commitId" : "e57da6e2a2d625106e1389ac14dd3cc0e7cee861", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "resource: fix locking in find_next_iomem_res()\u000a\u000acommit 49f17c26c123b60fd1c74629eef077740d16ffc2 upstream.\u000a\u000aSince resources can be removed, locking should ensure that the resource\u000ais not removed while accessing it. However, find_next_iomem_res() does\u000anot hold the lock while copying the data of the resource.\u000a\u000aKeep holding the lock while the data is copied. While at it, change the\u000areturn value to a more informative value. It is disregarded by the\u000acallers.\u000a\u000a[akpm@linux-foundation.org: fix find_next_iomem_res() documentation]\u000aLink: http://lkml.kernel.org/r/20190613045903.4922-2-namit@vmware.com\u000aFixes: ff3cc952d3f00 (\"resource: Add remove_resource interface\")\u000aSigned-off-by: Nadav Amit \u000aReviewed-by: Andrew Morton \u000aReviewed-by: Dan Williams \u000aCc: Borislav Petkov \u000aCc: Toshi Kani \u000aCc: Peter Zijlstra \u000aCc: Dave Hansen \u000aCc: Bjorn Helgaas \u000aCc: Ingo Molnar \u000aCc: \u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "e57da6e2a2d625106e1389ac14dd3cc0e7cee861", "msg" : "resource: fix locking in find_next_iomem_res()", "paths" : [ { "editType" : "edit", "file" : "kernel/resource.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/xfs/xfs_file.c" ], "commitId" : "2c1e1b8bbf4700f45d5b1d0b0e14f25400590642", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "xfs: abort unaligned nowait directio early\u000a\u000a[ Upstream commit 1fdeaea4d92c69fb9f871a787af6ad00f32eeea7 ]\u000a\u000aDave Chinner noticed that xfs_file_dio_aio_write returns EAGAIN without\u000adropping the IOLOCK when its deciding not to wait, which means that we\u000aleak the IOLOCK there. Since we now make unaligned directio always\u000await, we have the opportunity to bail out before trying to take the\u000alock, which should reduce the overhead of this never-gonna-work case\u000aconsiderably while also solving the dropped lock problem.\u000a\u000aReported-by: Dave Chinner \u000aSigned-off-by: Darrick J. Wong \u000aReviewed-by: Brian Foster \u000aReviewed-by: Dave Chinner \u000aReviewed-by: Christoph Hellwig \u000aSigned-off-by: Sasha Levin \u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "2c1e1b8bbf4700f45d5b1d0b0e14f25400590642", "msg" : "xfs: abort unaligned nowait directio early", "paths" : [ { "editType" : "edit", "file" : "fs/xfs/xfs_file.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/ipu-v3/ipu-ic.c" ], "commitId" : "8e6d99ab0474bb85103c27c52196bf0d16abf098", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpu: ipu-v3: ipu-ic: Fix saturation bit offset in TPMEM\u000a\u000acommit 3d1f62c686acdedf5ed9642b763f3808d6a47d1e upstream.\u000a\u000aThe saturation bit was being set at bit 9 in the second 32-bit word\u000aof the TPMEM CSC. This isn't correct, the saturation bit is bit 42,\u000awhich is bit 10 of the second word.\u000a\u000aFixes: 1aa8ea0d2bd5d (\"gpu: ipu-v3: Add Image Converter unit\")\u000a\u000aSigned-off-by: Steve Longerbeam \u000aReviewed-by: Philipp Zabel \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Philipp Zabel \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "8e6d99ab0474bb85103c27c52196bf0d16abf098", "msg" : "gpu: ipu-v3: ipu-ic: Fix saturation bit offset in TPMEM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/ipu-v3/ipu-ic.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/parisc/kernel/ptrace.c" ], "commitId" : "5403c45acd20d2283656ba71de43f28f0088d8a5", "timestamp" : 1564125185000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "parisc: Ensure userspace privilege for ptraced processes in regset functions\u000a\u000acommit 34c32fc603311a72cb558e5e337555434f64c27b upstream.\u000a\u000aOn parisc the privilege level of a process is stored in the lowest two bits of\u000athe instruction pointers (IAOQ0 and IAOQ1). On Linux we use privilege level 0\u000afor the kernel and privilege level 3 for user-space. So userspace should not be\u000aallowed to modify IAOQ0 or IAOQ1 of a ptraced process to change it's privilege\u000alevel to e.g. 0 to try to gain kernel privileges.\u000a\u000aThis patch prevents such modifications in the regset support functions by\u000aalways setting the two lowest bits to one (which relates to privilege level 3\u000afor user-space) if IAOQ0 or IAOQ1 are modified via ptrace regset calls.\u000a\u000aLink: https://bugs.gentoo.org/481768\u000aCc: # v4.7+\u000aTested-by: Rolf Eike Beer \u000aSigned-off-by: Helge Deller \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:05 +0200", "id" : "5403c45acd20d2283656ba71de43f28f0088d8a5", "msg" : "parisc: Ensure userspace privilege for ptraced processes in regset functions", "paths" : [ { "editType" : "edit", "file" : "arch/parisc/kernel/ptrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/parisc/kernel/ptrace.c" ], "commitId" : "4368be27006d3cf6570b1556a3652d396287ed48", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "parisc: Fix kernel panic due invalid values in IAOQ0 or IAOQ1\u000a\u000acommit 10835c854685393a921b68f529bf740fa7c9984d upstream.\u000a\u000aOn parisc the privilege level of a process is stored in the lowest two bits of\u000athe instruction pointers (IAOQ0 and IAOQ1). On Linux we use privilege level 0\u000afor the kernel and privilege level 3 for user-space. So userspace should not be\u000aallowed to modify IAOQ0 or IAOQ1 of a ptraced process to change it's privilege\u000alevel to e.g. 0 to try to gain kernel privileges.\u000a\u000aThis patch prevents such modifications by always setting the two lowest bits to\u000aone (which relates to privilege level 3 for user-space) if IAOQ0 or IAOQ1 are\u000amodified via ptrace calls in the native and compat ptrace paths.\u000a\u000aLink: https://bugs.gentoo.org/481768\u000aReported-by: Jeroen Roovers \u000aCc: \u000aTested-by: Rolf Eike Beer \u000aSigned-off-by: Helge Deller \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "4368be27006d3cf6570b1556a3652d396287ed48", "msg" : "parisc: Fix kernel panic due invalid values in IAOQ0 or IAOQ1", "paths" : [ { "editType" : "edit", "file" : "arch/parisc/kernel/ptrace.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/platforms/powermac/sleep.S", "arch/powerpc/kernel/swsusp_32.S" ], "commitId" : "d991b26df4d13a77a4487bc0bb9e83ce74438404", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc/32s: fix suspend/resume when IBATs 4-7 are used\u000a\u000acommit 6ecb78ef56e08d2119d337ae23cb951a640dc52d upstream.\u000a\u000aPreviously, only IBAT1 and IBAT2 were used to map kernel linear mem.\u000aSince commit 63b2bc619565 (\"powerpc/mm/32s: Use BATs for\u000aSTRICT_KERNEL_RWX\"), we may have all 8 BATs used for mapping\u000akernel text. But the suspend/restore functions only save/restore\u000aBATs 0 to 3, and clears BATs 4 to 7.\u000a\u000aMake suspend and restore functions respectively save and reload\u000athe 8 BATs on CPUs having MMU_FTR_USE_HIGH_BATS feature.\u000a\u000aReported-by: Andreas Schwab \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Christophe Leroy \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "d991b26df4d13a77a4487bc0bb9e83ce74438404", "msg" : "powerpc/32s: fix suspend/resume when IBATs 4-7 are used", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/platforms/powermac/sleep.S" }, { "editType" : "edit", "file" : "arch/powerpc/kernel/swsusp_32.S" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/mm/pgtable_32.c" ], "commitId" : "fe4be55d069c0aed2a095960519627dae503b1bf", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc/mm/32s: fix condition that is always true\u000a\u000acommit 46c2478af610efb3212b8b08f74389d69899ef70 upstream.\u000a\u000aMove a misplaced paren that makes the condition always true.\u000a\u000aFixes: 63b2bc619565 (\"powerpc/mm/32s: Use BATs for STRICT_KERNEL_RWX\")\u000aCc: stable@vger.kernel.org # v5.1+\u000aSigned-off-by: Andreas Schwab \u000aReviewed-by: Christophe Leroy \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "fe4be55d069c0aed2a095960519627dae503b1bf", "msg" : "powerpc/mm/32s: fix condition that is always true", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/mm/pgtable_32.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/kernel/exceptions-64s.S" ], "commitId" : "aacd6a4ec8e671ccc8008b7ae6181b1223cca946", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc/watchpoint: Restore NV GPRs while returning from exception\u000a\u000acommit f474c28fbcbe42faca4eb415172c07d76adcb819 upstream.\u000a\u000apowerpc hardware triggers watchpoint before executing the instruction.\u000aTo make trigger-after-execute behavior, kernel emulates the\u000ainstruction. If the instruction is 'load something into non-volatile\u000aregister', exception handler should restore emulated register state\u000awhile returning back, otherwise there will be register state\u000acorruption. eg, adding a watchpoint on a list can corrput the list:\u000a\u000a # cat /proc/kallsyms | grep kthread_create_list\u000a c00000000121c8b8 d kthread_create_list\u000a\u000aAdd watchpoint on kthread_create_list->prev:\u000a\u000a # perf record -e mem:0xc00000000121c8c0\u000a\u000aRun some workload such that new kthread gets invoked. eg, I just\u000alogged out from console:\u000a\u000a list_add corruption. next->prev should be prev (c000000001214e00), \\\u000a\u0009but was c00000000121c8b8. (next=c00000000121c8b8).\u000a WARNING: CPU: 59 PID: 309 at lib/list_debug.c:25 __list_add_valid+0xb4/0xc0\u000a CPU: 59 PID: 309 Comm: kworker/59:0 Kdump: loaded Not tainted 5.1.0-rc7+ #69\u000a ...\u000a NIP __list_add_valid+0xb4/0xc0\u000a LR __list_add_valid+0xb0/0xc0\u000a Call Trace:\u000a __list_add_valid+0xb0/0xc0 (unreliable)\u000a __kthread_create_on_node+0xe0/0x260\u000a kthread_create_on_node+0x34/0x50\u000a create_worker+0xe8/0x260\u000a worker_thread+0x444/0x560\u000a kthread+0x160/0x1a0\u000a ret_from_kernel_thread+0x5c/0x70\u000a\u000aList corruption happened because it uses 'load into non-volatile\u000aregister' instruction:\u000a\u000aSnippet from __kthread_create_on_node:\u000a\u000a c000000000136be8: addis r29,r2,-19\u000a c000000000136bec: ld r29,31424(r29)\u000a if (!__list_add_valid(new, prev, next))\u000a c000000000136bf0: mr r3,r30\u000a c000000000136bf4: mr r5,r28\u000a c000000000136bf8: mr r4,r29\u000a c000000000136bfc: bl c00000000059a2f8 <__list_add_valid+0x8>\u000a\u000aRegister state from WARN_ON():\u000a\u000a GPR00: c00000000059a3a0 c000007ff23afb50 c000000001344e00 0000000000000075\u000a GPR04: 0000000000000000 0000000000000000 0000001852af8bc1 0000000000000000\u000a GPR08: 0000000000000001 0000000000000007 0000000000000006 00000000000004aa\u000a GPR12: 0000000000000000 c000007ffffeb080 c000000000137038 c000005ff62aaa00\u000a GPR16: 0000000000000000 0000000000000000 c000007fffbe7600 c000007fffbe7370\u000a GPR20: c000007fffbe7320 c000007fffbe7300 c000000001373a00 0000000000000000\u000a GPR24: fffffffffffffef7 c00000000012e320 c000007ff23afcb0 c000000000cb8628\u000a GPR28: c00000000121c8b8 c000000001214e00 c000007fef5b17e8 c000007fef5b17c0\u000a\u000aWatchpoint hit at 0xc000000000136bec.\u000a\u000a addis r29,r2,-19\u000a => r29 = 0xc000000001344e00 + (-19 << 16)\u000a => r29 = 0xc000000001214e00\u000a\u000a ld r29,31424(r29)\u000a => r29 = *(0xc000000001214e00 + 31424)\u000a => r29 = *(0xc00000000121c8c0)\u000a\u000a0xc00000000121c8c0 is where we placed a watchpoint and thus this\u000ainstruction was emulated by emulate_step. But because handle_dabr_fault\u000adid not restore emulated register state, r29 still contains stale\u000avalue in above register state.\u000a\u000aFixes: 5aae8a5370802 (\"powerpc, hw_breakpoints: Implement hw_breakpoints for 64-bit server processors\")\u000aSigned-off-by: Ravi Bangoria \u000aCc: stable@vger.kernel.org # 2.6.36+\u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "aacd6a4ec8e671ccc8008b7ae6181b1223cca946", "msg" : "powerpc/watchpoint: Restore NV GPRs while returning from exception", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/kernel/exceptions-64s.S" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/platforms/powernv/npu-dma.c" ], "commitId" : "1848f2fe61937411e47d1719807722d7d5bef074", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc/powernv/npu: Fix reference leak\u000a\u000acommit 02c5f5394918b9b47ff4357b1b18335768cd867d upstream.\u000a\u000aSince 902bdc57451c, get_pci_dev() calls pci_get_domain_bus_and_slot(). This\u000ahas the effect of incrementing the reference count of the PCI device, as\u000aexplained in drivers/pci/search.c:\u000a\u000a * Given a PCI domain, bus, and slot/function number, the desired PCI\u000a * device is located in the list of PCI devices. If the device is\u000a * found, its reference count is increased and this function returns a\u000a * pointer to its data structure. The caller must decrement the\u000a * reference count by calling pci_dev_put(). If no device is found,\u000a * %NULL is returned.\u000a\u000aNothing was done to call pci_dev_put() and the reference count of GPU and\u000aNPU PCI devices rockets up.\u000a\u000aA natural way to fix this would be to teach the callers about the change,\u000aso that they call pci_dev_put() when done with the pointer. This turns\u000aout to be quite intrusive, as it affects many paths in npu-dma.c,\u000apci-ioda.c and vfio_pci_nvlink2.c. Also, the issue appeared in 4.16 and\u000asome affected code got moved around since then: it would be problematic\u000ato backport the fix to stable releases.\u000a\u000aAll that code never cared for reference counting anyway. Call pci_dev_put()\u000afrom get_pci_dev() to revert to the previous behavior.\u000a\u000aFixes: 902bdc57451c (\"powerpc/powernv/idoa: Remove unnecessary pcidev from pci_dn\")\u000aCc: stable@vger.kernel.org # v4.16\u000aSigned-off-by: Greg Kurz \u000aReviewed-by: Alexey Kardashevskiy \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "1848f2fe61937411e47d1719807722d7d5bef074", "msg" : "powerpc/powernv/npu: Fix reference leak", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/platforms/powernv/npu-dma.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/platforms/powernv/pci-ioda.c" ], "commitId" : "ffd200758415a324fc831f3b8cded5c9989dde79", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc/powernv: Fix stale iommu table base after VFIO\u000a\u000acommit 5636427d087a55842c1a199dfb839e6545d30e5d upstream.\u000a\u000aThe powernv platform uses @dma_iommu_ops for non-bypass DMA. These ops\u000aneed an iommu_table pointer which is stored in\u000adev->archdata.iommu_table_base. It is initialized during\u000apcibios_setup_device() which handles boot time devices. However when a\u000adevice is taken from the system in order to pass it through, the\u000adefault IOMMU table is destroyed but the pointer in a device is not\u000aupdated; also when a device is returned back to the system, a new\u000atable pointer is not stored in dev->archdata.iommu_table_base either.\u000aSo when a just returned device tries using IOMMU, it crashes on\u000aaccessing stale iommu_table or its members.\u000a\u000aThis calls set_iommu_table_base() when the default window is created.\u000aNote it used to be there before but was wrongly removed (see \"fixes\").\u000aIt did not appear before as these days most devices simply use bypass.\u000a\u000aThis adds set_iommu_table_base(NULL) when a device is taken from the\u000asystem to make it clear that IOMMU DMA cannot be used past that point.\u000a\u000aFixes: c4e9d3c1e65a (\"powerpc/powernv/pseries: Rework device adding to IOMMU groups\")\u000aCc: stable@vger.kernel.org # v5.0+\u000aSigned-off-by: Alexey Kardashevskiy \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "ffd200758415a324fc831f3b8cded5c9989dde79", "msg" : "powerpc/powernv: Fix stale iommu table base after VFIO", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/platforms/powernv/pci-ioda.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/powerpc/platforms/pseries/hotplug-memory.c" ], "commitId" : "169e979c0b037a1d94e14cde238b9853fcc985f8", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "powerpc/pseries: Fix oops in hotplug memory notifier\u000a\u000acommit 0aa82c482ab2ece530a6f44897b63b274bb43c8e upstream.\u000a\u000aDuring post-migration device tree updates, we can oops in\u000apseries_update_drconf_memory() if the source device tree has an\u000aibm,dynamic-memory-v2 property and the destination has a\u000aibm,dynamic_memory (v1) property. The notifier processes an \"update\"\u000afor the ibm,dynamic-memory property but it's really an add in this\u000ascenario. So make sure the old property object is there before\u000adereferencing it.\u000a\u000aFixes: 2b31e3aec1db (\"powerpc/drmem: Add support for ibm, dynamic-memory-v2 property\")\u000aCc: stable@vger.kernel.org # v4.16+\u000aSigned-off-by: Nathan Lynch \u000aSigned-off-by: Michael Ellerman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "169e979c0b037a1d94e14cde238b9853fcc985f8", "msg" : "powerpc/pseries: Fix oops in hotplug memory notifier", "paths" : [ { "editType" : "edit", "file" : "arch/powerpc/platforms/pseries/hotplug-memory.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/mmc/host/sdhci-msm.c" ], "commitId" : "e96cbc377ca20cf0a2d725b3dd344184105c275b", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mmc: sdhci-msm: fix mutex while in spinlock\u000a\u000acommit 5e6b6651d22de109ebf48ca00d0373bc2c0cc080 upstream.\u000a\u000amutexes can sleep and therefore should not be taken while holding a\u000aspinlock. move clk_get_rate (can sleep) outside the spinlock protected\u000aregion.\u000a\u000aFixes: 83736352e0ca (\"mmc: sdhci-msm: Update DLL reset sequence\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Jorge Ramirez-Ortiz \u000aReviewed-by: Bjorn Andersson \u000aReviewed-by: Vinod Koul \u000aAcked-by: Adrian Hunter \u000aSigned-off-by: Ulf Hansson \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "e96cbc377ca20cf0a2d725b3dd344184105c275b", "msg" : "mmc: sdhci-msm: fix mutex while in spinlock", "paths" : [ { "editType" : "edit", "file" : "drivers/mmc/host/sdhci-msm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/ecryptfs/crypto.c" ], "commitId" : "26db170bfde4e0e0d7289c8493c622a298ca2264", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "eCryptfs: fix a couple type promotion bugs\u000a\u000acommit 0bdf8a8245fdea6f075a5fede833a5fcf1b3466c upstream.\u000a\u000aECRYPTFS_SIZE_AND_MARKER_BYTES is type size_t, so if \"rc\" is negative\u000athat gets type promoted to a high positive value and treated as success.\u000a\u000aFixes: 778aeb42a708 (\"eCryptfs: Cleanup and optimize ecryptfs_lookup_interpose()\")\u000aSigned-off-by: Dan Carpenter \u000a[tyhicks: Use \"if/else if\" rather than \"if/if\"]\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Tyler Hicks \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "26db170bfde4e0e0d7289c8493c622a298ca2264", "msg" : "eCryptfs: fix a couple type promotion bugs", "paths" : [ { "editType" : "edit", "file" : "fs/ecryptfs/crypto.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/mtd/nand/raw/mtk_nand.c" ], "commitId" : "df7cbb1049a2bb184ef058e806762c52881636b4", "timestamp" : 1564125186000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mtd: rawnand: mtk: Correct low level time calculation of r/w cycle\u000a\u000acommit e1884ffddacc0424d7e785e6f8087bd12f7196db upstream.\u000a\u000aAt present, the flow of calculating AC timing of read/write cycle in SDR\u000amode is that:\u000aAt first, calculate high hold time which is valid for both read and write\u000acycle using the max value between tREH_min and tWH_min.\u000aSecondly, calculate WE# pulse width using tWP_min.\u000aThridly, calculate RE# pulse width using the bigger one between tREA_max\u000aand tRP_min.\u000a\u000aBut NAND SPEC shows that Controller should also meet write/read cycle time.\u000aThat is write cycle time should be more than tWC_min and read cycle should\u000abe more than tRC_min. Obviously, we do not achieve that now.\u000a\u000aThis patch corrects the low level time calculation to meet minimum\u000aread/write cycle time required. After getting the high hold time, WE# low\u000alevel time will be promised to meet tWP_min and tWC_min requirement,\u000aand RE# low level time will be promised to meet tREA_max, tRP_min and\u000atRC_min requirement.\u000a\u000aFixes: edfee3619c49 (\"mtd: nand: mtk: add ->setup_data_interface() hook\")\u000aCc: stable@vger.kernel.org # v4.17+\u000aSigned-off-by: Xiaolei Li \u000aReviewed-by: Miquel Raynal \u000aSigned-off-by: Miquel Raynal \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:06 +0200", "id" : "df7cbb1049a2bb184ef058e806762c52881636b4", "msg" : "mtd: rawnand: mtk: Correct low level time calculation of r/w cycle", "paths" : [ { "editType" : "edit", "file" : "drivers/mtd/nand/raw/mtk_nand.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/mtd/nand/spi/core.c" ], "commitId" : "db7437dd05d91c19226f160c549d4c21427449fc", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mtd: spinand: read returns badly if the last page has bitflips\u000a\u000acommit b83408b580eccf8d2797cd6cb9ae42c2a28656a7 upstream.\u000a\u000aIn case of the last page containing bitflips (ret > 0),\u000aspinand_mtd_read() will return that number of bitflips for the last\u000apage while it should instead return max_bitflips like it does when the\u000alast page read returns with 0.\u000a\u000aSigned-off-by: Weixiong Liao \u000aReviewed-by: Boris Brezillon \u000aReviewed-by: Frieder Schrempf \u000aCc: stable@vger.kernel.org\u000aFixes: 7529df465248 (\"mtd: nand: Add core infrastructure to support SPI NANDs\")\u000aSigned-off-by: Miquel Raynal \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "db7437dd05d91c19226f160c549d4c21427449fc", "msg" : "mtd: spinand: read returns badly if the last page has bitflips", "paths" : [ { "editType" : "edit", "file" : "drivers/mtd/nand/spi/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/hwtracing/intel_th/msu.c" ], "commitId" : "298f90ab4a65fff39517c3f3353b98f1f582eec6", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "intel_th: msu: Fix single mode with disabled IOMMU\u000a\u000acommit 918b8646497b5dba6ae82d4a7325f01b258972b9 upstream.\u000a\u000aCommit 4e0eaf239fb3 (\"intel_th: msu: Fix single mode with IOMMU\") switched\u000athe single mode code to use dma mapping pages obtained from the page\u000aallocator, but with IOMMU disabled, that may lead to using SWIOTLB bounce\u000abuffers and without additional sync'ing, produces empty trace buffers.\u000a\u000aFix this by using a DMA32 GFP flag to the page allocation in single mode,\u000aas the device supports full 32-bit DMA addressing.\u000a\u000aSigned-off-by: Alexander Shishkin \u000aFixes: 4e0eaf239fb3 (\"intel_th: msu: Fix single mode with IOMMU\")\u000aReviewed-by: Andy Shevchenko \u000aReported-by: Ammy Yi \u000aCc: stable \u000aLink: https://lore.kernel.org/r/20190621161930.60785-4-alexander.shishkin@linux.intel.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "298f90ab4a65fff39517c3f3353b98f1f582eec6", "msg" : "intel_th: msu: Fix single mode with disabled IOMMU", "paths" : [ { "editType" : "edit", "file" : "drivers/hwtracing/intel_th/msu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bluetooth/smp.c" ], "commitId" : "9f1cdd0deca4063b46b90fef26ac870fdb0affa6", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Bluetooth: Add SMP workaround Microsoft Surface Precision Mouse bug\u000a\u000acommit 1d87b88ba26eabd4745e158ecfd87c93a9b51dc2 upstream.\u000a\u000aMicrosoft Surface Precision Mouse provides bogus identity address when\u000apairing. It connects with Static Random address but provides Public\u000aAddress in SMP Identity Address Information PDU. Address has same\u000avalue but type is different. Workaround this by dropping IRK if ID\u000aaddress discrepancy is detected.\u000a\u000a> HCI Event: LE Meta Event (0x3e) plen 19\u000a LE Connection Complete (0x01)\u000a Status: Success (0x00)\u000a Handle: 75\u000a Role: Master (0x00)\u000a Peer address type: Random (0x01)\u000a Peer address: E0:52:33:93:3B:21 (Static)\u000a Connection interval: 50.00 msec (0x0028)\u000a Connection latency: 0 (0x0000)\u000a Supervision timeout: 420 msec (0x002a)\u000a Master clock accuracy: 0x00\u000a\u000a....\u000a\u000a> ACL Data RX: Handle 75 flags 0x02 dlen 12\u000a SMP: Identity Address Information (0x09) len 7\u000a Address type: Public (0x00)\u000a Address: E0:52:33:93:3B:21\u000a\u000aSigned-off-by: Szymon Janc \u000aTested-by: Maarten Fonville \u000aBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=199461\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Marcel Holtmann \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "9f1cdd0deca4063b46b90fef26ac870fdb0affa6", "msg" : "Bluetooth: Add SMP workaround Microsoft Surface Precision Mouse bug", "paths" : [ { "editType" : "edit", "file" : "net/bluetooth/smp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/dax.c" ], "commitId" : "584cd9936ac1c52517711dbc0d6f380177069c97", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dax: Fix missed wakeup with PMD faults\u000a\u000acommit 23c84eb7837514e16d79ed6d849b13745e0ce688 upstream.\u000a\u000aRocksDB can hang indefinitely when using a DAX file. This is due to\u000aa bug in the XArray conversion when handling a PMD fault and finding a\u000aPTE entry. We use the wrong index in the hash and end up waiting on\u000athe wrong waitqueue.\u000a\u000aThere's actually no need to wait; if we find a PTE entry while looking\u000afor a PMD entry, we can return immediately as we know we should fall\u000aback to a PTE fault (which may not conflict with the lock held).\u000a\u000aWe reuse the XA_RETRY_ENTRY to signal a conflicting entry was found.\u000aThis value can never be found in an XArray while holding its lock, so\u000ait does not create an ambiguity.\u000a\u000aCc: \u000aLink: http://lkml.kernel.org/r/CAPcyv4hwHpX-MkUEqxwdTj7wCCZCN4RV-L4jsnuwLGyL_UEG4A@mail.gmail.com\u000aFixes: b15cd800682f (\"dax: Convert page fault handlers to XArray\")\u000aSigned-off-by: Matthew Wilcox (Oracle) \u000aTested-by: Dan Williams \u000aReported-by: Robert Barror \u000aReported-by: Seema Pandit \u000aReviewed-by: Jan Kara \u000aSigned-off-by: Dan Williams \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "584cd9936ac1c52517711dbc0d6f380177069c97", "msg" : "dax: Fix missed wakeup with PMD faults", "paths" : [ { "editType" : "edit", "file" : "fs/dax.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/core/hub.c" ], "commitId" : "24d22d774481e7d586534937b0f24d0a0dfb7e40", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "usb: Handle USB3 remote wakeup for LPM enabled devices correctly\u000a\u000acommit e244c4699f859cf7149b0781b1894c7996a8a1df upstream.\u000a\u000aWith Link Power Management (LPM) enabled USB3 links transition to low\u000apower U1/U2 link states from U0 state automatically.\u000a\u000aCurrent hub code detects USB3 remote wakeups by checking if the software\u000astate still shows suspended, but the link has transitioned from suspended\u000aU3 to enabled U0 state.\u000a\u000aAs it takes some time before the hub thread reads the port link state\u000aafter a USB3 wake notification, the link may have transitioned from U0\u000ato U1/U2, and wake is not detected by hub code.\u000a\u000aFix this by handling U1/U2 states in the same way as U0 in USB3 wakeup\u000ahandling\u000a\u000aThis patch should be added to stable kernels since 4.13 where LPM was\u000akept enabled during suspend/resume\u000a\u000aCc: # v4.13+\u000aSigned-off-by: Lee, Chiasheng \u000aSigned-off-by: Mathias Nyman \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "24d22d774481e7d586534937b0f24d0a0dfb7e40", "msg" : "usb: Handle USB3 remote wakeup for LPM enabled devices correctly", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/core/hub.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/blk-throttle.c" ], "commitId" : "2df91af73fd4f28c6ba39dd1c49f42e244d9f667", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "blk-throttle: fix zero wait time for iops throttled group\u000a\u000acommit 3a10f999ffd464d01c5a05592a15470a3c4bbc36 upstream.\u000a\u000aAfter commit 991f61fe7e1d (\"Blk-throttle: reduce tail io latency when\u000aiops limit is enforced\") wait time could be zero even if group is\u000athrottled and cannot issue requests right now. As a result\u000athrotl_select_dispatch() turns into busy-loop under irq-safe queue\u000aspinlock.\u000a\u000aFix is simple: always round up target time to the next throttle slice.\u000a\u000aFixes: 991f61fe7e1d (\"Blk-throttle: reduce tail io latency when iops limit is enforced\")\u000aSigned-off-by: Konstantin Khlebnikov \u000aCc: stable@vger.kernel.org # v4.19+\u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "2df91af73fd4f28c6ba39dd1c49f42e244d9f667", "msg" : "blk-throttle: fix zero wait time for iops throttled group", "paths" : [ { "editType" : "edit", "file" : "block/blk-throttle.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/clk/imx/clk-imx8mm.c" ], "commitId" : "d9b2310494f7925905ee151bb6f6556559efefe6", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "clk: imx: imx8mm: correct audio_pll2_clk to audio_pll2_out\u000a\u000acommit 5b933e28d8b1fbdc7fbac4bfc569f3b152c3dd59 upstream.\u000a\u000aThere is no audio_pll2_clk registered, it should be audio_pll2_out.\u000a\u000aCc: \u000aFixes: ba5625c3e272 (\"clk: imx: Add clock driver support for imx8mm\")\u000aSigned-off-by: Peng Fan \u000aSigned-off-by: Shawn Guo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "d9b2310494f7925905ee151bb6f6556559efefe6", "msg" : "clk: imx: imx8mm: correct audio_pll2_clk to audio_pll2_out", "paths" : [ { "editType" : "edit", "file" : "drivers/clk/imx/clk-imx8mm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/blk-iolatency.c" ], "commitId" : "bea58a0e6844f244d8d1789f08dab3678483f24c", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "blk-iolatency: clear use_delay when io.latency is set to zero\u000a\u000acommit 5de0073fcd50cc1f150895a7bb04d3cf8067b1d7 upstream.\u000a\u000aIf use_delay was non-zero when the latency target of a cgroup was set\u000ato zero, it will stay stuck until io.latency is enabled on the cgroup\u000aagain. This keeps readahead disabled for the cgroup impacting\u000aperformance negatively.\u000a\u000aSigned-off-by: Tejun Heo \u000aCc: Josef Bacik \u000aFixes: d70675121546 (\"block: introduce blk-iolatency io controller\")\u000aCc: stable@vger.kernel.org # v4.19+\u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "bea58a0e6844f244d8d1789f08dab3678483f24c", "msg" : "blk-iolatency: clear use_delay when io.latency is set to zero", "paths" : [ { "editType" : "edit", "file" : "block/blk-iolatency.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "block/blk-cgroup.c" ], "commitId" : "2bee53a06de245207d5ec9d20a9f09face83841d", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "blkcg: update blkcg_print_stat() to handle larger outputs\u000a\u000acommit f539da82f2158916e154d206054e0efd5df7ab61 upstream.\u000a\u000aDepending on the number of devices, blkcg stats can go over the\u000adefault seqfile buf size. seqfile normally retries with a larger\u000abuffer but since the ->pd_stat() addition, blkcg_print_stat() doesn't\u000atell seqfile that overflow has happened and the output gets printed\u000atruncated. Fix it by calling seq_commit() w/ -1 on possible\u000aoverflows.\u000a\u000aSigned-off-by: Tejun Heo \u000aFixes: 903d23f0a354 (\"blk-cgroup: allow controllers to output their own stats\")\u000aCc: stable@vger.kernel.org # v4.19+\u000aCc: Josef Bacik \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "2bee53a06de245207d5ec9d20a9f09face83841d", "msg" : "blkcg: update blkcg_print_stat() to handle larger outputs", "paths" : [ { "editType" : "edit", "file" : "block/blk-cgroup.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/marvell/mvmdio.c" ], "commitId" : "fcf852316acd57621db43109474303fcdd4169df", "timestamp" : 1564125187000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: mvmdio: allow up to four clocks to be specified for orion-mdio\u000a\u000acommit 4aabed699c400810981d3dda170f05fa4d782905 upstream.\u000a\u000aAllow up to four clocks to be specified and enabled for the orion-mdio\u000ainterface, which are required by the Armada 8k and defined in\u000aarmada-cp110.dtsi.\u000a\u000aFixes a hang in probing the mvmdio driver that was encountered on the\u000aClearfog GT 8K with all drivers built as modules, but also affects other\u000aboards such as the MacchiatoBIN.\u000a\u000aCc: stable@vger.kernel.org\u000aFixes: 96cb43423822 (\"net: mvmdio: allow up to three clocks to be specified for orion-mdio\")\u000aReviewed-by: Andrew Lunn \u000aSigned-off-by: Josua Mayer \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:07 +0200", "id" : "fcf852316acd57621db43109474303fcdd4169df", "msg" : "net: mvmdio: allow up to four clocks to be specified for orion-mdio", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/marvell/mvmdio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Documentation/devicetree/bindings/net/marvell-orion-mdio.txt" ], "commitId" : "61c3ed42bc2e55d600bc614e8d7de8a9c4f6a1cf", "timestamp" : 1564125188000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dt-bindings: allow up to four clocks for orion-mdio\u000a\u000acommit 80785f5a22e9073e2ded5958feb7f220e066d17b upstream.\u000a\u000aArmada 8040 needs four clocks to be enabled for MDIO accesses to work.\u000aUpdate the binding to allow the extra clock to be specified.\u000a\u000aCc: stable@vger.kernel.org\u000aFixes: 6d6a331f44a1 (\"dt-bindings: allow up to three clocks for orion-mdio\")\u000aReviewed-by: Andrew Lunn \u000aSigned-off-by: Josua Mayer \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:08 +0200", "id" : "61c3ed42bc2e55d600bc614e8d7de8a9c4f6a1cf", "msg" : "dt-bindings: allow up to four clocks for orion-mdio", "paths" : [ { "editType" : "edit", "file" : "Documentation/devicetree/bindings/net/marvell-orion-mdio.txt" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/pstore/inode.c" ], "commitId" : "09afa9e360259e8c797c5778df73c9bb645a0725", "timestamp" : 1564125188000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "pstore: Fix double-free in pstore_mkfile() failure path\u000a\u000acommit 4c6d80e1144bdf48cae6b602ae30d41f3e5c76a9 upstream.\u000a\u000aThe pstore_mkfile() function is passed a pointer to a struct\u000apstore_record. On success it consumes this 'record' pointer and\u000areferences it from the created inode.\u000a\u000aOn failure, however, it may or may not free the record. There are even\u000atwo different code paths which return -ENOMEM -- one of which does and\u000athe other doesn't free the record.\u000a\u000aMake the behaviour deterministic by never consuming and freeing the\u000arecord when returning failure, allowing the caller to do the cleanup\u000aconsistently.\u000a\u000aSigned-off-by: Norbert Manthey \u000aLink: https://lore.kernel.org/r/1562331960-26198-1-git-send-email-nmanthey@amazon.de\u000aFixes: 83f70f0769ddd (\"pstore: Do not duplicate record metadata\")\u000aFixes: 1dfff7dd67d1a (\"pstore: Pass record contents instead of copying\")\u000aCc: stable@vger.kernel.org\u000a[kees: also move \"private\" allocation location, rename inode cleanup label]\u000aSigned-off-by: Kees Cook \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:08 +0200", "id" : "09afa9e360259e8c797c5778df73c9bb645a0725", "msg" : "pstore: Fix double-free in pstore_mkfile() failure path", "paths" : [ { "editType" : "edit", "file" : "fs/pstore/inode.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/md/dm-bufio.c" ], "commitId" : "f27cc07fe474b6db286f9fa6aed5e4336606f0b7", "timestamp" : 1564125188000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dm bufio: fix deadlock with loop device\u000a\u000acommit bd293d071ffe65e645b4d8104f9d8fe15ea13862 upstream.\u000a\u000aWhen thin-volume is built on loop device, if available memory is low,\u000athe following deadlock can be triggered:\u000a\u000aOne process P1 allocates memory with GFP_FS flag, direct alloc fails,\u000amemory reclaim invokes memory shrinker in dm_bufio, dm_bufio_shrink_scan()\u000aruns, mutex dm_bufio_client->lock is acquired, then P1 waits for dm_buffer\u000aIO to complete in __try_evict_buffer().\u000a\u000aBut this IO may never complete if issued to an underlying loop device\u000athat forwards it using direct-IO, which allocates memory using\u000aGFP_KERNEL (see: do_blockdev_direct_IO()). If allocation fails, memory\u000areclaim will invoke memory shrinker in dm_bufio, dm_bufio_shrink_scan()\u000awill be invoked, and since the mutex is already held by P1 the loop\u000athread will hang, and IO will never complete. Resulting in ABBA\u000adeadlock.\u000a\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Junxiao Bi \u000aSigned-off-by: Mike Snitzer \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-26 09:13:08 +0200", "id" : "f27cc07fe474b6db286f9fa6aed5e4336606f0b7", "msg" : "dm bufio: fix deadlock with loop device", "paths" : [ { "editType" : "edit", "file" : "drivers/md/dm-bufio.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Makefile" ], "commitId" : "aac977a09eca0e62280644a2bdc3403a61892348", "timestamp" : 1564125188000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Linux 5.1.20\u000a", "date" : "2019-07-26 09:13:08 +0200", "id" : "aac977a09eca0e62280644a2bdc3403a61892348", "msg" : "Linux 5.1.20", "paths" : [ { "editType" : "edit", "file" : "Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c" ], "commitId" : "c73a6485a8aa9fe08ca8d31af3c9925ff59cf9c7", "timestamp" : 1564295303000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "bnx2x: Prevent load reordering in tx completion processing\u000a\u000a[ Upstream commit ea811b795df24644a8eb760b493c43fba4450677 ]\u000a\u000aThis patch fixes an issue seen on Power systems with bnx2x which results\u000ain the skb is NULL WARN_ON in bnx2x_free_tx_pkt firing due to the skb\u000apointer getting loaded in bnx2x_free_tx_pkt prior to the hw_cons\u000aload in bnx2x_tx_int. Adding a read memory barrier resolves the issue.\u000a\u000aSigned-off-by: Brian King \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:23 +0200", "id" : "c73a6485a8aa9fe08ca8d31af3c9925ff59cf9c7", "msg" : "bnx2x: Prevent load reordering in tx completion processing", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/caif/caif_hsi.c" ], "commitId" : "14f7a56762aa6a290b34bcb037defd3ea4d312f2", "timestamp" : 1564295303000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "caif-hsi: fix possible deadlock in cfhsi_exit_module()\u000a\u000a[ Upstream commit fdd258d49e88a9e0b49ef04a506a796f1c768a8e ]\u000a\u000acfhsi_exit_module() calls unregister_netdev() under rtnl_lock().\u000abut unregister_netdev() internally calls rtnl_lock().\u000aSo deadlock would occur.\u000a\u000aFixes: c41254006377 (\"caif-hsi: Add rtnl support\")\u000aSigned-off-by: Taehee Yoo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:23 +0200", "id" : "14f7a56762aa6a290b34bcb037defd3ea4d312f2", "msg" : "caif-hsi: fix possible deadlock in cfhsi_exit_module()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/caif/caif_hsi.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/hyperv/netvsc_drv.c" ], "commitId" : "5b8385de62269b5344f4c15ed92619c06ec92526", "timestamp" : 1564295304000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "hv_netvsc: Fix extra rcu_read_unlock in netvsc_recv_callback()\u000a\u000a[ Upstream commit be4363bdf0ce9530f15aa0a03d1060304d116b15 ]\u000a\u000aThere is an extra rcu_read_unlock left in netvsc_recv_callback(),\u000aafter a previous patch that removes RCU from this function.\u000aThis patch removes the extra RCU unlock.\u000a\u000aFixes: 345ac08990b8 (\"hv_netvsc: pass netvsc_device to receive callback\")\u000aSigned-off-by: Haiyang Zhang \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:24 +0200", "id" : "5b8385de62269b5344f4c15ed92619c06ec92526", "msg" : "hv_netvsc: Fix extra rcu_read_unlock in netvsc_recv_callback()", "paths" : [ { "editType" : "edit", "file" : "drivers/net/hyperv/netvsc_drv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv4/igmp.c" ], "commitId" : "ce6994f56e7a6e1ac0630328e65fa2d9d919786d", "timestamp" : 1564295304000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "igmp: fix memory leak in igmpv3_del_delrec()\u000a\u000a[ Upstream commit e5b1c6c6277d5a283290a8c033c72544746f9b5b ]\u000a\u000aim->tomb and/or im->sources might not be NULL, but we\u000acurrently overwrite their values blindly.\u000a\u000aUsing swap() will make sure the following call to kfree_pmc(pmc)\u000awill properly free the psf structures.\u000a\u000aTested with the C repro provided by syzbot, which basically does :\u000a\u000a socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3\u000a setsockopt(3, SOL_IP, IP_ADD_MEMBERSHIP, \"\\340\\0\\0\\2\\177\\0\\0\\1\\0\\0\\0\\0\", 12) = 0\u000a ioctl(3, SIOCSIFFLAGS, {ifr_name=\"lo\", ifr_flags=0}) = 0\u000a setsockopt(3, SOL_IP, IP_MSFILTER, \"\\340\\0\\0\\2\\177\\0\\0\\1\\1\\0\\0\\0\\1\\0\\0\\0\\377\\377\\377\\377\", 20) = 0\u000a ioctl(3, SIOCSIFFLAGS, {ifr_name=\"lo\", ifr_flags=IFF_UP}) = 0\u000a exit_group(0) = ?\u000a\u000aBUG: memory leak\u000aunreferenced object 0xffff88811450f140 (size 64):\u000a comm \"softirq\", pid 0, jiffies 4294942448 (age 32.070s)\u000a hex dump (first 32 bytes):\u000a 00 00 00 00 00 00 00 00 ff ff ff ff 00 00 00 00 ................\u000a 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................\u000a backtrace:\u000a [<00000000c7bad083>] kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline]\u000a [<00000000c7bad083>] slab_post_alloc_hook mm/slab.h:439 [inline]\u000a [<00000000c7bad083>] slab_alloc mm/slab.c:3326 [inline]\u000a [<00000000c7bad083>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553\u000a [<000000009acc4151>] kmalloc include/linux/slab.h:547 [inline]\u000a [<000000009acc4151>] kzalloc include/linux/slab.h:742 [inline]\u000a [<000000009acc4151>] ip_mc_add1_src net/ipv4/igmp.c:1976 [inline]\u000a [<000000009acc4151>] ip_mc_add_src+0x36b/0x400 net/ipv4/igmp.c:2100\u000a [<000000004ac14566>] ip_mc_msfilter+0x22d/0x310 net/ipv4/igmp.c:2484\u000a [<0000000052d8f995>] do_ip_setsockopt.isra.0+0x1795/0x1930 net/ipv4/ip_sockglue.c:959\u000a [<000000004ee1e21f>] ip_setsockopt+0x3b/0xb0 net/ipv4/ip_sockglue.c:1248\u000a [<0000000066cdfe74>] udp_setsockopt+0x4e/0x90 net/ipv4/udp.c:2618\u000a [<000000009383a786>] sock_common_setsockopt+0x38/0x50 net/core/sock.c:3126\u000a [<00000000d8ac0c94>] __sys_setsockopt+0x98/0x120 net/socket.c:2072\u000a [<000000001b1e9666>] __do_sys_setsockopt net/socket.c:2083 [inline]\u000a [<000000001b1e9666>] __se_sys_setsockopt net/socket.c:2080 [inline]\u000a [<000000001b1e9666>] __x64_sys_setsockopt+0x26/0x30 net/socket.c:2080\u000a [<00000000420d395e>] do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301\u000a [<000000007fd83a4b>] entry_SYSCALL_64_after_hwframe+0x44/0xa9\u000a\u000aFixes: 24803f38a5c0 (\"igmp: do not remove igmp souce list info when set link down\")\u000aSigned-off-by: Eric Dumazet \u000aCc: Hangbin Liu \u000aReported-by: syzbot+6ca1abd0db68b5173a4f@syzkaller.appspotmail.com\u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:24 +0200", "id" : "ce6994f56e7a6e1ac0630328e65fa2d9d919786d", "msg" : "igmp: fix memory leak in igmpv3_del_delrec()", "paths" : [ { "editType" : "edit", "file" : "net/ipv4/igmp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv4/devinet.c" ], "commitId" : "7719f7253677b5a9a3db8b95d2861d32081cfca0", "timestamp" : 1564295304000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipv4: don't set IPv6 only flags to IPv4 addresses\u000a\u000a[ Upstream commit 2e60546368165c2449564d71f6005dda9205b5fb ]\u000a\u000aAvoid the situation where an IPV6 only flag is applied to an IPv4 address:\u000a\u000a # ip addr add 192.0.2.1/24 dev dummy0 nodad home mngtmpaddr noprefixroute\u000a # ip -4 addr show dev dummy0\u000a 2: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000\u000a inet 192.0.2.1/24 scope global noprefixroute dummy0\u000a valid_lft forever preferred_lft forever\u000a\u000aOr worse, by sending a malicious netlink command:\u000a\u000a # ip -4 addr show dev dummy0\u000a 2: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000\u000a inet 192.0.2.1/24 scope global nodad optimistic dadfailed home tentative mngtmpaddr noprefixroute stable-privacy dummy0\u000a valid_lft forever preferred_lft forever\u000a\u000aSigned-off-by: Matteo Croce \u000aReviewed-by: David Ahern \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:24 +0200", "id" : "7719f7253677b5a9a3db8b95d2861d32081cfca0", "msg" : "ipv4: don't set IPv6 only flags to IPv4 addresses", "paths" : [ { "editType" : "edit", "file" : "net/ipv4/devinet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv6/route.c" ], "commitId" : "f2acb2903f1603643a7b683c04bd88a7781888dd", "timestamp" : 1564295305000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipv6: rt6_check should return NULL if 'from' is NULL\u000a\u000a[ Upstream commit 49d05fe2c9d1b4a27761c9807fec39b8155bef9e ]\u000a\u000aPaul reported that l2tp sessions were broken after the commit referenced\u000ain the Fixes tag. Prior to this commit rt6_check returned NULL if the\u000art6_info 'from' was NULL - ie., the dst_entry was disconnected from a FIB\u000aentry. Restore that behavior.\u000a\u000aFixes: 93531c674315 (\"net/ipv6: separate handling of FIB entries from dst based routes\")\u000aReported-by: Paul Donohue \u000aTested-by: Paul Donohue \u000aSigned-off-by: David Ahern \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:25 +0200", "id" : "f2acb2903f1603643a7b683c04bd88a7781888dd", "msg" : "ipv6: rt6_check should return NULL if 'from' is NULL", "paths" : [ { "editType" : "edit", "file" : "net/ipv6/route.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv6/ip6_fib.c" ], "commitId" : "847b4237cfa6512dad7117207f1c5dcebeba35ec", "timestamp" : 1564295305000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ipv6: Unlink sibling route in case of failure\u000a\u000a[ Upstream commit 54851aa90cf27041d64b12f65ac72e9f97bd90fd ]\u000a\u000aWhen a route needs to be appended to an existing multipath route,\u000afib6_add_rt2node() first appends it to the siblings list and increments\u000athe number of sibling routes on each sibling.\u000a\u000aLater, the function notifies the route via call_fib6_entry_notifiers().\u000aIn case the notification is vetoed, the route is not unlinked from the\u000asiblings list, which can result in a use-after-free.\u000a\u000aFix this by unlinking the route from the siblings list before returning\u000aan error.\u000a\u000aAudited the rest of the call sites from which the FIB notification chain\u000ais called and could not find more problems.\u000a\u000aFixes: 2233000cba40 (\"net/ipv6: Move call_fib6_entry_notifiers up for route adds\")\u000aSigned-off-by: Ido Schimmel \u000aReported-by: Alexander Petrovskiy \u000aReviewed-by: David Ahern \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:25 +0200", "id" : "847b4237cfa6512dad7117207f1c5dcebeba35ec", "msg" : "ipv6: Unlink sibling route in case of failure", "paths" : [ { "editType" : "edit", "file" : "net/ipv6/ip6_fib.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/broadcom/genet/bcmgenet.c" ], "commitId" : "17f782cc4039d48436587b897658937158c2ef33", "timestamp" : 1564295306000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: bcmgenet: use promisc for unsupported filters\u000a\u000a[ Upstream commit 35cbef9863640f06107144687bd13151bc2e8ce3 ]\u000a\u000aCurrently we silently ignore filters if we cannot meet the filter\u000arequirements. This will lead to the MAC dropping packets that are\u000aexpected to pass. A better solution would be to set the NIC to promisc\u000amode when the required filters cannot be met.\u000a\u000aAlso correct the number of MDF filters supported. It should be 17,\u000anot 16.\u000a\u000aSigned-off-by: Justin Chen \u000aReviewed-by: Florian Fainelli \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:26 +0200", "id" : "17f782cc4039d48436587b897658937158c2ef33", "msg" : "net: bcmgenet: use promisc for unsupported filters", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/broadcom/genet/bcmgenet.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/dsa/mv88e6xxx/chip.c" ], "commitId" : "4b2e53dfcb599ecdaa3db1a2e7d5bef9bacd5502", "timestamp" : 1564295307000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: dsa: mv88e6xxx: wait after reset deactivation\u000a\u000a[ Upstream commit 7b75e49de424ceb53d13e60f35d0a73765626fda ]\u000a\u000aAdd a 1ms delay after reset deactivation. Otherwise the chip returns\u000abogus ID value. This is observed with 88E6390 (Peridot) chip.\u000a\u000aSigned-off-by: Baruch Siach \u000aReviewed-by: Andrew Lunn \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:27 +0200", "id" : "4b2e53dfcb599ecdaa3db1a2e7d5bef9bacd5502", "msg" : "net: dsa: mv88e6xxx: wait after reset deactivation", "paths" : [ { "editType" : "edit", "file" : "drivers/net/dsa/mv88e6xxx/chip.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netfilter/nf_queue.c", "include/net/dst.h" ], "commitId" : "4912f3f1a8868afc6b36293454b5307368f88c22", "timestamp" : 1564295307000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: make skb_dst_force return true when dst is refcounted\u000a\u000a[ Upstream commit b60a77386b1d4868f72f6353d35dabe5fbe981f2 ]\u000a\u000anetfilter did not expect that skb_dst_force() can cause skb to lose its\u000adst entry.\u000a\u000aI got a bug report with a skb->dst NULL dereference in netfilter\u000aoutput path. The backtrace contains nf_reinject(), so the dst might have\u000abeen cleared when skb got queued to userspace.\u000a\u000aOther users were fixed via\u000aif (skb_dst(skb)) {\u000a\u0009skb_dst_force(skb);\u000a\u0009if (!skb_dst(skb))\u000a\u0009\u0009goto handle_err;\u000a}\u000a\u000aBut I think its preferable to make the 'dst might be cleared' part\u000aof the function explicit.\u000a\u000aIn netfilter case, skb with a null dst is expected when queueing in\u000aprerouting hook, so drop skb for the other hooks.\u000a\u000av2:\u000a v1 of this patch returned true in case skb had no dst entry.\u000a Eric said:\u000a Say if we have two skb_dst_force() calls for some reason\u000a on the same skb, only the first one will return false.\u000a\u000a This now returns false even when skb had no dst, as per Erics\u000a suggestion, so callers might need to check skb_dst() first before\u000a skb_dst_force().\u000a\u000aSigned-off-by: Florian Westphal \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:27 +0200", "id" : "4912f3f1a8868afc6b36293454b5307368f88c22", "msg" : "net: make skb_dst_force return true when dst is refcounted", "paths" : [ { "editType" : "edit", "file" : "include/net/dst.h" }, { "editType" : "edit", "file" : "net/netfilter/nf_queue.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/core/neighbour.c" ], "commitId" : "821aa330150e493dec7379963211cc4145117aea", "timestamp" : 1564295308000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: neigh: fix multiple neigh timer scheduling\u000a\u000a[ Upstream commit 071c37983d99da07797294ea78e9da1a6e287144 ]\u000a\u000aNeigh timer can be scheduled multiple times from userspace adding\u000amultiple neigh entries and forcing the neigh timer scheduling passing\u000aNTF_USE in the netlink requests.\u000aThis will result in a refcount leak and in the following dump stack:\u000a\u000a[ 32.465295] NEIGH: BUG, double timer add, state is 8\u000a[ 32.465308] CPU: 0 PID: 416 Comm: double_timer_ad Not tainted 5.2.0+ #65\u000a[ 32.465311] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.12.0-2.fc30 04/01/2014\u000a[ 32.465313] Call Trace:\u000a[ 32.465318] dump_stack+0x7c/0xc0\u000a[ 32.465323] __neigh_event_send+0x20c/0x880\u000a[ 32.465326] ? ___neigh_create+0x846/0xfb0\u000a[ 32.465329] ? neigh_lookup+0x2a9/0x410\u000a[ 32.465332] ? neightbl_fill_info.constprop.0+0x800/0x800\u000a[ 32.465334] neigh_add+0x4f8/0x5e0\u000a[ 32.465337] ? neigh_xmit+0x620/0x620\u000a[ 32.465341] ? find_held_lock+0x85/0xa0\u000a[ 32.465345] rtnetlink_rcv_msg+0x204/0x570\u000a[ 32.465348] ? rtnl_dellink+0x450/0x450\u000a[ 32.465351] ? mark_held_locks+0x90/0x90\u000a[ 32.465354] ? match_held_lock+0x1b/0x230\u000a[ 32.465357] netlink_rcv_skb+0xc4/0x1d0\u000a[ 32.465360] ? rtnl_dellink+0x450/0x450\u000a[ 32.465363] ? netlink_ack+0x420/0x420\u000a[ 32.465366] ? netlink_deliver_tap+0x115/0x560\u000a[ 32.465369] ? __alloc_skb+0xc9/0x2f0\u000a[ 32.465372] netlink_unicast+0x270/0x330\u000a[ 32.465375] ? netlink_attachskb+0x2f0/0x2f0\u000a[ 32.465378] netlink_sendmsg+0x34f/0x5a0\u000a[ 32.465381] ? netlink_unicast+0x330/0x330\u000a[ 32.465385] ? move_addr_to_kernel.part.0+0x20/0x20\u000a[ 32.465388] ? netlink_unicast+0x330/0x330\u000a[ 32.465391] sock_sendmsg+0x91/0xa0\u000a[ 32.465394] ___sys_sendmsg+0x407/0x480\u000a[ 32.465397] ? copy_msghdr_from_user+0x200/0x200\u000a[ 32.465401] ? _raw_spin_unlock_irqrestore+0x37/0x40\u000a[ 32.465404] ? lockdep_hardirqs_on+0x17d/0x250\u000a[ 32.465407] ? __wake_up_common_lock+0xcb/0x110\u000a[ 32.465410] ? __wake_up_common+0x230/0x230\u000a[ 32.465413] ? netlink_bind+0x3e1/0x490\u000a[ 32.465416] ? netlink_setsockopt+0x540/0x540\u000a[ 32.465420] ? __fget_light+0x9c/0xf0\u000a[ 32.465423] ? sockfd_lookup_light+0x8c/0xb0\u000a[ 32.465426] __sys_sendmsg+0xa5/0x110\u000a[ 32.465429] ? __ia32_sys_shutdown+0x30/0x30\u000a[ 32.465432] ? __fd_install+0xe1/0x2c0\u000a[ 32.465435] ? lockdep_hardirqs_off+0xb5/0x100\u000a[ 32.465438] ? mark_held_locks+0x24/0x90\u000a[ 32.465441] ? do_syscall_64+0xf/0x270\u000a[ 32.465444] do_syscall_64+0x63/0x270\u000a[ 32.465448] entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a\u000aFix the issue unscheduling neigh_timer if selected entry is in 'IN_TIMER'\u000areceiving a netlink request with NTF_USE flag set\u000a\u000aReported-by: Marek Majkowski \u000aFixes: 0c5c2d308906 (\"neigh: Allow for user space users of the neighbour table\")\u000aSigned-off-by: Lorenzo Bianconi \u000aReviewed-by: David Ahern \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:28 +0200", "id" : "821aa330150e493dec7379963211cc4145117aea", "msg" : "net: neigh: fix multiple neigh timer scheduling", "paths" : [ { "editType" : "edit", "file" : "net/core/neighbour.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/openvswitch/actions.c" ], "commitId" : "af0cab5c15d134cb88534f9479107bb36011cb2f", "timestamp" : 1564295308000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: openvswitch: fix csum updates for MPLS actions\u000a\u000a[ Upstream commit 0e3183cd2a64843a95b62f8bd4a83605a4cf0615 ]\u000a\u000aSkbs may have their checksum value populated by HW. If this is a checksum\u000acalculated over the entire packet then the CHECKSUM_COMPLETE field is\u000amarked. Changes to the data pointer on the skb throughout the network\u000astack still try to maintain this complete csum value if it is required\u000athrough functions such as skb_postpush_rcsum.\u000a\u000aThe MPLS actions in Open vSwitch modify a CHECKSUM_COMPLETE value when\u000achanges are made to packet data without a push or a pull. This occurs when\u000athe ethertype of the MAC header is changed or when MPLS lse fields are\u000amodified.\u000a\u000aThe modification is carried out using the csum_partial function to get the\u000acsum of a buffer and add it into the larger checksum. The buffer is an\u000ainversion of the data to be removed followed by the new data. Because the\u000acsum is calculated over 16 bits and these values align with 16 bits, the\u000aeffect is the removal of the old value from the CHECKSUM_COMPLETE and\u000aaddition of the new value.\u000a\u000aHowever, the csum fed into the function and the outcome of the\u000acalculation are also inverted. This would only make sense if it was the\u000anew value rather than the old that was inverted in the input buffer.\u000a\u000aFix the issue by removing the bit inverts in the csum_partial calculation.\u000a\u000aThe bug was verified and the fix tested by comparing the folded value of\u000athe updated CHECKSUM_COMPLETE value with the folded value of a full\u000asoftware checksum calculation (reset skb->csum to 0 and run\u000askb_checksum_complete(skb)). Prior to the fix the outcomes differed but\u000aafter they produce the same result.\u000a\u000aFixes: 25cd9ba0abc0 (\"openvswitch: Add basic MPLS support to kernel\")\u000aFixes: bc7cc5999fd3 (\"openvswitch: update checksum in {push,pop}_mpls\")\u000aSigned-off-by: John Hurley \u000aReviewed-by: Jakub Kicinski \u000aReviewed-by: Simon Horman \u000aAcked-by: Pravin B Shelar \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:28 +0200", "id" : "af0cab5c15d134cb88534f9479107bb36011cb2f", "msg" : "net: openvswitch: fix csum updates for MPLS actions", "paths" : [ { "editType" : "edit", "file" : "net/openvswitch/actions.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/phy/sfp.c" ], "commitId" : "ba5f4cb33e9bdcbc895902dc78fd990a526de005", "timestamp" : 1564295309000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: phy: sfp: hwmon: Fix scaling of RX power\u000a\u000a[ Upstream commit 0cea0e1148fe134a4a3aaf0b1496f09241fb943a ]\u000a\u000aThe RX power read from the SFP uses units of 0.1uW. This must be\u000ascaled to units of uW for HWMON. This requires a divide by 10, not the\u000acurrent 100.\u000a\u000aWith this change in place, sensors(1) and ethtool -m agree:\u000a\u000asff2-isa-0000\u000aAdapter: ISA adapter\u000ain0: +3.23 V\u000atemp1: +33.1 C\u000apower1: 270.00 uW\u000apower2: 200.00 uW\u000acurr1: +0.01 A\u000a\u000a Laser output power : 0.2743 mW / -5.62 dBm\u000a Receiver signal average optical power : 0.2014 mW / -6.96 dBm\u000a\u000aReported-by: chris.healy@zii.aero\u000aSigned-off-by: Andrew Lunn \u000aFixes: 1323061a018a (\"net: phy: sfp: Add HWMON support for module sensors\")\u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:29 +0200", "id" : "ba5f4cb33e9bdcbc895902dc78fd990a526de005", "msg" : "net: phy: sfp: hwmon: Fix scaling of RX power", "paths" : [ { "editType" : "edit", "file" : "drivers/net/phy/sfp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/sched/cls_api.c", "net/sched/sch_fq_codel.c", "net/sched/sch_sfq.c" ], "commitId" : "e6da0a5873732f9ea06345bb01a8117fd4529a43", "timestamp" : 1564295309000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net_sched: unset TCQ_F_CAN_BYPASS when adding filters\u000a\u000a[ Upstream commit 3f05e6886a595c9a29a309c52f45326be917823c ]\u000a\u000aFor qdisc's that support TC filters and set TCQ_F_CAN_BYPASS,\u000anotably fq_codel, it makes no sense to let packets bypass the TC\u000afilters we setup in any scenario, otherwise our packets steering\u000apolicy could not be enforced.\u000a\u000aThis can be reproduced easily with the following script:\u000a\u000a ip li add dev dummy0 type dummy\u000a ifconfig dummy0 up\u000a tc qd add dev dummy0 root fq_codel\u000a tc filter add dev dummy0 parent 8001: protocol arp basic action mirred egress redirect dev lo\u000a tc filter add dev dummy0 parent 8001: protocol ip basic action mirred egress redirect dev lo\u000a ping -I dummy0 192.168.112.1\u000a\u000aWithout this patch, packets are sent directly to dummy0 without\u000ahitting any of the filters. With this patch, packets are redirected\u000ato loopback as expected.\u000a\u000aThis fix is not perfect, it only unsets the flag but does not set it back\u000abecause we have to save the information somewhere in the qdisc if we\u000areally want that. Note, both fq_codel and sfq clear this flag in their\u000a->bind_tcf() but this is clearly not sufficient when we don't use any\u000aclass ID.\u000a\u000aFixes: 23624935e0c4 (\"net_sched: TCQ_F_CAN_BYPASS generalization\")\u000aCc: Eric Dumazet \u000aSigned-off-by: Cong Wang \u000aReviewed-by: Eric Dumazet \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:29 +0200", "id" : "e6da0a5873732f9ea06345bb01a8117fd4529a43", "msg" : "net_sched: unset TCQ_F_CAN_BYPASS when adding filters", "paths" : [ { "editType" : "edit", "file" : "net/sched/cls_api.c" }, { "editType" : "edit", "file" : "net/sched/sch_fq_codel.c" }, { "editType" : "edit", "file" : "net/sched/sch_sfq.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c" ], "commitId" : "7a78bda3cad948939f006cb923893184a30a8d75", "timestamp" : 1564295310000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: stmmac: Re-work the queue selection for TSO packets\u000a\u000a[ Upstream commit 4993e5b37e8bcb55ac90f76eb6d2432647273747 ]\u000a\u000aBen Hutchings says:\u000a\u0009\"This is the wrong place to change the queue mapping.\u000a\u0009stmmac_xmit() is called with a specific TX queue locked,\u000a\u0009and accessing a different TX queue results in a data race\u000a\u0009for all of that queue's state.\u000a\u000a\u0009I think this commit should be reverted upstream and in all\u000a\u0009stable branches. Instead, the driver should implement the\u000a\u0009ndo_select_queue operation and override the queue mapping there.\"\u000a\u000aFixes: c5acdbee22a1 (\"net: stmmac: Send TSO packets always from Queue 0\")\u000aSuggested-by: Ben Hutchings \u000aSigned-off-by: Jose Abreu \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:30 +0200", "id" : "7a78bda3cad948939f006cb923893184a30a8d75", "msg" : "net: stmmac: Re-work the queue selection for TSO packets", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/tls/tls_device.c", "net/tls/tls_main.c", "include/net/tls.h" ], "commitId" : "5edaba9e9e06b9c310eeec995ca7320c2dc64f2b", "timestamp" : 1564295310000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/tls: make sure offload also gets the keys wiped\u000a\u000a[ Upstream commit acd3e96d53a24d219f720ed4012b62723ae05da1 ]\u000a\u000aCommit 86029d10af18 (\"tls: zero the crypto information from tls_context\u000abefore freeing\") added memzero_explicit() calls to clear the key material\u000abefore freeing struct tls_context, but it missed tls_device.c has its\u000aown way of freeing this structure. Replace the missing free.\u000a\u000aFixes: 86029d10af18 (\"tls: zero the crypto information from tls_context before freeing\")\u000aSigned-off-by: Jakub Kicinski \u000aReviewed-by: Dirk van der Merwe \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:30 +0200", "id" : "5edaba9e9e06b9c310eeec995ca7320c2dc64f2b", "msg" : "net/tls: make sure offload also gets the keys wiped", "paths" : [ { "editType" : "edit", "file" : "include/net/tls.h" }, { "editType" : "edit", "file" : "net/tls/tls_main.c" }, { "editType" : "edit", "file" : "net/tls/tls_device.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/nfc/nci/data.c" ], "commitId" : "e1f7bc510d84532d3140da37830e9a84e5984e65", "timestamp" : 1564295310000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "nfc: fix potential illegal memory access\u000a\u000a[ Upstream commit dd006fc434e107ef90f7de0db9907cbc1c521645 ]\u000a\u000aThe frags_q is not properly initialized, it may result in illegal memory\u000aaccess when conn_info is NULL.\u000aThe \"goto free_exit\" should be replaced by \"goto exit\".\u000a\u000aSigned-off-by: Yang Wei \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:30 +0200", "id" : "e1f7bc510d84532d3140da37830e9a84e5984e65", "msg" : "nfc: fix potential illegal memory access", "paths" : [ { "editType" : "edit", "file" : "net/nfc/nci/data.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/realtek/r8169.c" ], "commitId" : "3618e5919694df536f35b53e94416cb7163606aa", "timestamp" : 1564295311000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "r8169: fix issue with confused RX unit after PHY power-down on RTL8411b\u000a\u000a[ Upstream commit fe4e8db0392a6c2e795eb89ef5fcd86522e66248 ]\u000a\u000aOn RTL8411b the RX unit gets confused if the PHY is powered-down.\u000aThis was reported in [0] and confirmed by Realtek. Realtek provided\u000aa sequence to fix the RX unit after PHY wakeup.\u000a\u000aThe issue itself seems to have been there longer, the Fixes tag\u000arefers to where the fix applies properly.\u000a\u000a[0] https://bugzilla.redhat.com/show_bug.cgi?id=1692075\u000a\u000aFixes: a99790bf5c7f (\"r8169: Reinstate ASPM Support\")\u000aTested-by: Ionut Radu \u000aSigned-off-by: Heiner Kallweit \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:31 +0200", "id" : "3618e5919694df536f35b53e94416cb7163606aa", "msg" : "r8169: fix issue with confused RX unit after PHY power-down on RTL8411b", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/realtek/r8169.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/rxrpc/af_rxrpc.c" ], "commitId" : "36febc9885c7cda0fcafadb6fc7f77deb1811902", "timestamp" : 1564295311000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "rxrpc: Fix send on a connected, but unbound socket\u000a\u000a[ Upstream commit e835ada07091f40dcfb1bc735082bd0a7c005e59 ]\u000a\u000aIf sendmsg() or sendmmsg() is called on a connected socket that hasn't had\u000abind() called on it, then an oops will occur when the kernel tries to\u000aconnect the call because no local endpoint has been allocated.\u000a\u000aFix this by implicitly binding the socket if it is in the\u000aRXRPC_CLIENT_UNBOUND state, just like it does for the RXRPC_UNBOUND state.\u000a\u000aFurther, the state should be transitioned to RXRPC_CLIENT_BOUND after this\u000ato prevent further attempts to bind it.\u000a\u000aThis can be tested with:\u000a\u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009#include \u000a\u0009static const unsigned char inet6_addr[16] = {\u000a\u0009\u00090, 0, 0, 0, 0, 0, 0, 0, 0, 0, -1, -1, 0xac, 0x14, 0x14, 0xaa\u000a\u0009};\u000a\u0009int main(void)\u000a\u0009{\u000a\u0009\u0009struct sockaddr_rxrpc srx;\u000a\u0009\u0009struct cmsghdr *cm;\u000a\u0009\u0009struct msghdr msg;\u000a\u0009\u0009unsigned char control[16];\u000a\u0009\u0009int fd;\u000a\u0009\u0009memset(&srx, 0, sizeof(srx));\u000a\u0009\u0009srx.srx_family = 0x21;\u000a\u0009\u0009srx.srx_service = 0;\u000a\u0009\u0009srx.transport_type = AF_INET;\u000a\u0009\u0009srx.transport_len = 0x1c;\u000a\u0009\u0009srx.transport.sin6.sin6_family = AF_INET6;\u000a\u0009\u0009srx.transport.sin6.sin6_port = htons(0x4e22);\u000a\u0009\u0009srx.transport.sin6.sin6_flowinfo = htons(0x4e22);\u000a\u0009\u0009srx.transport.sin6.sin6_scope_id = htons(0xaa3b);\u000a\u0009\u0009memcpy(&srx.transport.sin6.sin6_addr, inet6_addr, 16);\u000a\u0009\u0009cm = (struct cmsghdr *)control;\u000a\u0009\u0009cm->cmsg_len\u0009= CMSG_LEN(sizeof(unsigned long));\u000a\u0009\u0009cm->cmsg_level\u0009= SOL_RXRPC;\u000a\u0009\u0009cm->cmsg_type\u0009= RXRPC_USER_CALL_ID;\u000a\u0009\u0009*(unsigned long *)CMSG_DATA(cm) = 0;\u000a\u0009\u0009msg.msg_name = NULL;\u000a\u0009\u0009msg.msg_namelen = 0;\u000a\u0009\u0009msg.msg_iov = NULL;\u000a\u0009\u0009msg.msg_iovlen = 0;\u000a\u0009\u0009msg.msg_control = control;\u000a\u0009\u0009msg.msg_controllen = cm->cmsg_len;\u000a\u0009\u0009msg.msg_flags = 0;\u000a\u0009\u0009fd = socket(AF_RXRPC, SOCK_DGRAM, AF_INET);\u000a\u0009\u0009connect(fd, (struct sockaddr *)&srx, sizeof(srx));\u000a\u0009\u0009sendmsg(fd, &msg, 0);\u000a\u0009\u0009return 0;\u000a\u0009}\u000a\u000aLeading to the following oops:\u000a\u000a\u0009BUG: kernel NULL pointer dereference, address: 0000000000000018\u000a\u0009#PF: supervisor read access in kernel mode\u000a\u0009#PF: error_code(0x0000) - not-present page\u000a\u0009...\u000a\u0009RIP: 0010:rxrpc_connect_call+0x42/0xa01\u000a\u0009...\u000a\u0009Call Trace:\u000a\u0009 ? mark_held_locks+0x47/0x59\u000a\u0009 ? __local_bh_enable_ip+0xb6/0xba\u000a\u0009 rxrpc_new_client_call+0x3b1/0x762\u000a\u0009 ? rxrpc_do_sendmsg+0x3c0/0x92e\u000a\u0009 rxrpc_do_sendmsg+0x3c0/0x92e\u000a\u0009 rxrpc_sendmsg+0x16b/0x1b5\u000a\u0009 sock_sendmsg+0x2d/0x39\u000a\u0009 ___sys_sendmsg+0x1a4/0x22a\u000a\u0009 ? release_sock+0x19/0x9e\u000a\u0009 ? reacquire_held_locks+0x136/0x160\u000a\u0009 ? release_sock+0x19/0x9e\u000a\u0009 ? find_held_lock+0x2b/0x6e\u000a\u0009 ? __lock_acquire+0x268/0xf73\u000a\u0009 ? rxrpc_connect+0xdd/0xe4\u000a\u0009 ? __local_bh_enable_ip+0xb6/0xba\u000a\u0009 __sys_sendmsg+0x5e/0x94\u000a\u0009 do_syscall_64+0x7d/0x1bf\u000a\u0009 entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a\u000aFixes: 2341e0775747 (\"rxrpc: Simplify connect() implementation and simplify sendmsg() op\")\u000aReported-by: syzbot+7966f2a0b2c7da8939b4@syzkaller.appspotmail.com\u000aSigned-off-by: David Howells \u000aReviewed-by: Marc Dionne \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:31 +0200", "id" : "36febc9885c7cda0fcafadb6fc7f77deb1811902", "msg" : "rxrpc: Fix send on a connected, but unbound socket", "paths" : [ { "editType" : "edit", "file" : "net/rxrpc/af_rxrpc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/sctp/stream.c" ], "commitId" : "2a8e1d0c9646f78fdd0f00e2eadf8210bbf810a7", "timestamp" : 1564295311000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sctp: fix error handling on stream scheduler initialization\u000a\u000a[ Upstream commit 4d1415811e492d9a8238f8a92dd0d51612c788e9 ]\u000a\u000aIt allocates the extended area for outbound streams only on sendmsg\u000acalls, if they are not yet allocated. When using the priority\u000astream scheduler, this initialization may imply into a subsequent\u000aallocation, which may fail. In this case, it was aborting the stream\u000ascheduler initialization but leaving the ->ext pointer (allocated) in\u000athere, thus in a partially initialized state. On a subsequent call to\u000asendmsg, it would notice the ->ext pointer in there, and trip on\u000auninitialized stuff when trying to schedule the data chunk.\u000a\u000aThe fix is undo the ->ext initialization if the stream scheduler\u000ainitialization fails and avoid the partially initialized state.\u000a\u000aAlthough syzkaller bisected this to commit 4ff40b86262b (\"sctp: set\u000achunk transport correctly when it's a new asoc\"), this bug was actually\u000aintroduced on the commit I marked below.\u000a\u000aReported-by: syzbot+c1a380d42b190ad1e559@syzkaller.appspotmail.com\u000aFixes: 5bbbbe32a431 (\"sctp: introduce stream scheduler foundations\")\u000aTested-by: Xin Long \u000aSigned-off-by: Marcelo Ricardo Leitner \u000aAcked-by: Neil Horman \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:31 +0200", "id" : "2a8e1d0c9646f78fdd0f00e2eadf8210bbf810a7", "msg" : "sctp: fix error handling on stream scheduler initialization", "paths" : [ { "editType" : "edit", "file" : "net/sctp/stream.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/sctp/socket.c" ], "commitId" : "066992c6328c637384f82a6832016a21fcd3a089", "timestamp" : 1564295311000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sctp: not bind the socket in sctp_connect\u000a\u000a[ Upstream commit 9b6c08878e23adb7cc84bdca94d8a944b03f099e ]\u000a\u000aNow when sctp_connect() is called with a wrong sa_family, it binds\u000ato a port but doesn't set bp->port, then sctp_get_af_specific will\u000areturn NULL and sctp_connect() returns -EINVAL.\u000a\u000aThen if sctp_bind() is called to bind to another port, the last\u000aport it has bound will leak due to bp->port is NULL by then.\u000a\u000asctp_connect() doesn't need to bind ports, as later __sctp_connect\u000awill do it if bp->port is NULL. So remove it from sctp_connect().\u000aWhile at it, remove the unnecessary sockaddr.sa_family len check\u000aas it's already done in sctp_inet_connect.\u000a\u000aFixes: 644fbdeacf1d (\"sctp: fix the issue that flags are ignored when using kernel_connect\")\u000aReported-by: syzbot+079bf326b38072f849d9@syzkaller.appspotmail.com\u000aSigned-off-by: Xin Long \u000aAcked-by: Marcelo Ricardo Leitner \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:31 +0200", "id" : "066992c6328c637384f82a6832016a21fcd3a089", "msg" : "sctp: not bind the socket in sctp_connect", "paths" : [ { "editType" : "edit", "file" : "net/sctp/socket.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/marvell/sky2.c" ], "commitId" : "0558547a6e1f08862b06a75a7dec3239e2091662", "timestamp" : 1564295312000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sky2: Disable MSI on ASUS P6T\u000a\u000a[ Upstream commit a261e3797506bd561700be643fe1a85bf81e9661 ]\u000a\u000aThe onboard sky2 NIC on ASUS P6T WS PRO doesn't work after PM resume\u000adue to the infamous IRQ problem. Disabling MSI works around it, so\u000alet's add it to the blacklist.\u000a\u000aUnfortunately the BIOS on the machine doesn't fill the standard\u000aDMI_SYS_* entry, so we pick up DMI_BOARD_* entries instead.\u000a\u000aBugLink: https://bugzilla.suse.com/show_bug.cgi?id=1142496\u000aReported-and-tested-by: Marcus Seyfarth \u000aSigned-off-by: Takashi Iwai \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:32 +0200", "id" : "0558547a6e1f08862b06a75a7dec3239e2091662", "msg" : "sky2: Disable MSI on ASUS P6T", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/marvell/sky2.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv4/tcp_output.c", "include/net/tcp.h" ], "commitId" : "35618f4e85134bed345a93725a89d1e14f4fcfef", "timestamp" : 1564295312000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tcp: be more careful in tcp_fragment()\u000a\u000a[ Upstream commit b617158dc096709d8600c53b6052144d12b89fab ]\u000a\u000aSome applications set tiny SO_SNDBUF values and expect\u000aTCP to just work. Recent patches to address CVE-2019-11478\u000abroke them in case of losses, since retransmits might\u000abe prevented.\u000a\u000aWe should allow these flows to make progress.\u000a\u000aThis patch allows the first and last skb in retransmit queue\u000ato be split even if memory limits are hit.\u000a\u000aIt also adds the some room due to the fact that tcp_sendmsg()\u000aand tcp_sendpage() might overshoot sk_wmem_queued by about one full\u000aTSO skb (64KB size). Note this allowance was already present\u000ain stable backports for kernels < 4.15\u000a\u000aNote for < 4.15 backports :\u000a tcp_rtx_queue_tail() will probably look like :\u000a\u000astatic inline struct sk_buff *tcp_rtx_queue_tail(const struct sock *sk)\u000a{\u000a\u0009struct sk_buff *skb = tcp_send_head(sk);\u000a\u000a\u0009return skb ? tcp_write_queue_prev(sk, skb) : tcp_write_queue_tail(sk);\u000a}\u000a\u000aFixes: f070ef2ac667 (\"tcp: tcp_fragment() should apply sane memory limits\")\u000aSigned-off-by: Eric Dumazet \u000aReported-by: Andrew Prout \u000aTested-by: Andrew Prout \u000aTested-by: Jonathan Lemon \u000aTested-by: Michal Kubecek \u000aAcked-by: Neal Cardwell \u000aAcked-by: Yuchung Cheng \u000aAcked-by: Christoph Paasch \u000aCc: Jonathan Looney \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:32 +0200", "id" : "35618f4e85134bed345a93725a89d1e14f4fcfef", "msg" : "tcp: be more careful in tcp_fragment()", "paths" : [ { "editType" : "edit", "file" : "net/ipv4/tcp_output.c" }, { "editType" : "edit", "file" : "include/net/tcp.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv4/tcp.c", "net/ipv4/tcp_cong.c", "include/net/tcp.h", "net/core/filter.c" ], "commitId" : "dfc9148309629cd5c1f8252153496195dfc31045", "timestamp" : 1564295312000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tcp: fix tcp_set_congestion_control() use from bpf hook\u000a\u000a[ Upstream commit 8d650cdedaabb33e85e9b7c517c0c71fcecc1de9 ]\u000a\u000aNeal reported incorrect use of ns_capable() from bpf hook.\u000a\u000abpf_setsockopt(...TCP_CONGESTION...)\u000a -> tcp_set_congestion_control()\u000a -> ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN)\u000a -> ns_capable_common()\u000a -> current_cred()\u000a -> rcu_dereference_protected(current->cred, 1)\u000a\u000aAccessing 'current' in bpf context makes no sense, since packets\u000aare processed from softirq context.\u000a\u000aAs Neal stated : The capability check in tcp_set_congestion_control()\u000awas written assuming a system call context, and then was reused from\u000aa BPF call site.\u000a\u000aThe fix is to add a new parameter to tcp_set_congestion_control(),\u000aso that the ns_capable() call is only performed under the right\u000acontext.\u000a\u000aFixes: 91b5b21c7c16 (\"bpf: Add support for changing congestion control\")\u000aSigned-off-by: Eric Dumazet \u000aCc: Lawrence Brakmo \u000aReported-by: Neal Cardwell \u000aAcked-by: Neal Cardwell \u000aAcked-by: Lawrence Brakmo \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:32 +0200", "id" : "dfc9148309629cd5c1f8252153496195dfc31045", "msg" : "tcp: fix tcp_set_congestion_control() use from bpf hook", "paths" : [ { "editType" : "edit", "file" : "net/core/filter.c" }, { "editType" : "edit", "file" : "include/net/tcp.h" }, { "editType" : "edit", "file" : "net/ipv4/tcp.c" }, { "editType" : "edit", "file" : "net/ipv4/tcp_cong.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/ipv4/tcp.c" ], "commitId" : "2527ea8f115cdd0b1e8fc5cb161ff7d1a7a99351", "timestamp" : 1564295313000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "tcp: Reset bytes_acked and bytes_received when disconnecting\u000a\u000a[ Upstream commit e858faf556d4e14c750ba1e8852783c6f9520a0e ]\u000a\u000aIf an app is playing tricks to reuse a socket via tcp_disconnect(),\u000abytes_acked/received needs to be reset to 0. Otherwise tcp_info will\u000areport the sum of the current and the old connection..\u000a\u000aCc: Eric Dumazet \u000aFixes: 0df48c26d841 (\"tcp: add tcpi_bytes_acked to tcp_info\")\u000aFixes: bdd1f9edacb5 (\"tcp: add tcpi_bytes_received to tcp_info\")\u000aSigned-off-by: Christoph Paasch \u000aSigned-off-by: Eric Dumazet \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:33 +0200", "id" : "2527ea8f115cdd0b1e8fc5cb161ff7d1a7a99351", "msg" : "tcp: Reset bytes_acked and bytes_received when disconnecting", "paths" : [ { "editType" : "edit", "file" : "net/ipv4/tcp.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/vrf.c" ], "commitId" : "98ecf34e6b82d9c04bff5cb39e9ff964f505bb79", "timestamp" : 1564295313000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "vrf: make sure skb->data contains ip header to make routing\u000a\u000a[ Upstream commit 107e47cc80ec37cb332bd41b22b1c7779e22e018 ]\u000a\u000avrf_process_v4_outbound() and vrf_process_v6_outbound() do routing\u000ausing ip/ipv6 addresses, but don't make sure the header is available\u000ain skb->data[] (skb_headlen() is less then header size).\u000a\u000aCase:\u000a\u000a1) igb driver from intel.\u000a2) Packet size is greater then 255.\u000a3) MPLS forwards to VRF device.\u000a\u000aSo, patch adds pskb_may_pull() calls in vrf_process_v4/v6_outbound()\u000afunctions.\u000a\u000aSigned-off-by: Peter Kosyh \u000aReviewed-by: David Ahern \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:33 +0200", "id" : "98ecf34e6b82d9c04bff5cb39e9ff964f505bb79", "msg" : "vrf: make sure skb->data contains ip header to make routing", "paths" : [ { "editType" : "edit", "file" : "drivers/net/vrf.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlx5/core/ipoib/ipoib.c" ], "commitId" : "5a637c0b0d5e37076f5fec36879016f9308a328a", "timestamp" : 1564295313000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/mlx5e: IPoIB, Add error path in mlx5_rdma_setup_rn\u000a\u000a[ Upstream commit ef1ce7d7b67b46661091c7ccc0396186b7a247ef ]\u000a\u000aCheck return value from mlx5e_attach_netdev, add error path on failure.\u000a\u000aFixes: 48935bbb7ae8 (\"net/mlx5e: IPoIB, Add netdevice profile skeleton\")\u000aSigned-off-by: Aya Levin \u000aReviewed-by: Feras Daoud \u000aSigned-off-by: Saeed Mahameed \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:33 +0200", "id" : "5a637c0b0d5e37076f5fec36879016f9308a328a", "msg" : "net/mlx5e: IPoIB, Add error path in mlx5_rdma_setup_rn", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/ipoib/ipoib.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bridge/br_multicast.c" ], "commitId" : "aa1a26b4d8b68dda13f997b67415632c1d963e45", "timestamp" : 1564295313000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: bridge: mcast: fix stale nsrcs pointer in igmp3/mld2 report handling\u000a\u000a[ Upstream commit e57f61858b7cf478ed6fa23ed4b3876b1c9625c4 ]\u000a\u000aWe take a pointer to grec prior to calling pskb_may_pull and use it\u000aafterwards to get nsrcs so record nsrcs before the pull when handling\u000aigmp3 and we get a pointer to nsrcs and call pskb_may_pull when handling\u000amld2 which again could lead to reading 2 bytes out-of-bounds.\u000a\u000a ==================================================================\u000a BUG: KASAN: use-after-free in br_multicast_rcv+0x480c/0x4ad0 [bridge]\u000a Read of size 2 at addr ffff8880421302b4 by task ksoftirqd/1/16\u000a\u000a CPU: 1 PID: 16 Comm: ksoftirqd/1 Tainted: G OE 5.2.0-rc6+ #1\u000a Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014\u000a Call Trace:\u000a dump_stack+0x71/0xab\u000a print_address_description+0x6a/0x280\u000a ? br_multicast_rcv+0x480c/0x4ad0 [bridge]\u000a __kasan_report+0x152/0x1aa\u000a ? br_multicast_rcv+0x480c/0x4ad0 [bridge]\u000a ? br_multicast_rcv+0x480c/0x4ad0 [bridge]\u000a kasan_report+0xe/0x20\u000a br_multicast_rcv+0x480c/0x4ad0 [bridge]\u000a ? br_multicast_disable_port+0x150/0x150 [bridge]\u000a ? ktime_get_with_offset+0xb4/0x150\u000a ? __kasan_kmalloc.constprop.6+0xa6/0xf0\u000a ? __netif_receive_skb+0x1b0/0x1b0\u000a ? br_fdb_update+0x10e/0x6e0 [bridge]\u000a ? br_handle_frame_finish+0x3c6/0x11d0 [bridge]\u000a br_handle_frame_finish+0x3c6/0x11d0 [bridge]\u000a ? br_pass_frame_up+0x3a0/0x3a0 [bridge]\u000a ? virtnet_probe+0x1c80/0x1c80 [virtio_net]\u000a br_handle_frame+0x731/0xd90 [bridge]\u000a ? select_idle_sibling+0x25/0x7d0\u000a ? br_handle_frame_finish+0x11d0/0x11d0 [bridge]\u000a __netif_receive_skb_core+0xced/0x2d70\u000a ? virtqueue_get_buf_ctx+0x230/0x1130 [virtio_ring]\u000a ? do_xdp_generic+0x20/0x20\u000a ? virtqueue_napi_complete+0x39/0x70 [virtio_net]\u000a ? virtnet_poll+0x94d/0xc78 [virtio_net]\u000a ? receive_buf+0x5120/0x5120 [virtio_net]\u000a ? __netif_receive_skb_one_core+0x97/0x1d0\u000a __netif_receive_skb_one_core+0x97/0x1d0\u000a ? __netif_receive_skb_core+0x2d70/0x2d70\u000a ? _raw_write_trylock+0x100/0x100\u000a ? __queue_work+0x41e/0xbe0\u000a process_backlog+0x19c/0x650\u000a ? _raw_read_lock_irq+0x40/0x40\u000a net_rx_action+0x71e/0xbc0\u000a ? __switch_to_asm+0x40/0x70\u000a ? napi_complete_done+0x360/0x360\u000a ? __switch_to_asm+0x34/0x70\u000a ? __switch_to_asm+0x40/0x70\u000a ? __schedule+0x85e/0x14d0\u000a __do_softirq+0x1db/0x5f9\u000a ? takeover_tasklets+0x5f0/0x5f0\u000a run_ksoftirqd+0x26/0x40\u000a smpboot_thread_fn+0x443/0x680\u000a ? sort_range+0x20/0x20\u000a ? schedule+0x94/0x210\u000a ? __kthread_parkme+0x78/0xf0\u000a ? sort_range+0x20/0x20\u000a kthread+0x2ae/0x3a0\u000a ? kthread_create_worker_on_cpu+0xc0/0xc0\u000a ret_from_fork+0x35/0x40\u000a\u000a The buggy address belongs to the page:\u000a page:ffffea0001084c00 refcount:0 mapcount:-128 mapping:0000000000000000 index:0x0\u000a flags: 0xffffc000000000()\u000a raw: 00ffffc000000000 ffffea0000cfca08 ffffea0001098608 0000000000000000\u000a raw: 0000000000000000 0000000000000003 00000000ffffff7f 0000000000000000\u000a page dumped because: kasan: bad access detected\u000a\u000a Memory state around the buggy address:\u000a ffff888042130180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\u000a ffff888042130200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\u000a > ffff888042130280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\u000a ^\u000a ffff888042130300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\u000a ffff888042130380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\u000a ==================================================================\u000a Disabling lock debugging due to kernel taint\u000a\u000aFixes: bc8c20acaea1 (\"bridge: multicast: treat igmpv3 report with INCLUDE and no sources as a leave\")\u000aReported-by: Martin Weinelt \u000aSigned-off-by: Nikolay Aleksandrov \u000aTested-by: Martin Weinelt \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:33 +0200", "id" : "aa1a26b4d8b68dda13f997b67415632c1d963e45", "msg" : "net: bridge: mcast: fix stale nsrcs pointer in igmp3/mld2 report handling", "paths" : [ { "editType" : "edit", "file" : "net/bridge/br_multicast.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bridge/br_multicast.c" ], "commitId" : "0b159b8b49b7c22eb4815710f365c8a53af0f148", "timestamp" : 1564295313000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: bridge: mcast: fix stale ipv6 hdr pointer when handling v6 query\u000a\u000a[ Upstream commit 3b26a5d03d35d8f732d75951218983c0f7f68dff ]\u000a\u000aWe get a pointer to the ipv6 hdr in br_ip6_multicast_query but we may\u000acall pskb_may_pull afterwards and end up using a stale pointer.\u000aSo use the header directly, it's just 1 place where it's needed.\u000a\u000aFixes: 08b202b67264 (\"bridge br_multicast: IPv6 MLD support.\")\u000aSigned-off-by: Nikolay Aleksandrov \u000aTested-by: Martin Weinelt \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:33 +0200", "id" : "0b159b8b49b7c22eb4815710f365c8a53af0f148", "msg" : "net: bridge: mcast: fix stale ipv6 hdr pointer when handling v6 query", "paths" : [ { "editType" : "edit", "file" : "net/bridge/br_multicast.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bridge/br_input.c" ], "commitId" : "17f2557801f833007a296ce96f133c1da7e1f489", "timestamp" : 1564295313000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: bridge: don't cache ether dest pointer on input\u000a\u000a[ Upstream commit 3d26eb8ad1e9b906433903ce05f775cf038e747f ]\u000a\u000aWe would cache ether dst pointer on input in br_handle_frame_finish but\u000aafter the neigh suppress code that could lead to a stale pointer since\u000aboth ipv4 and ipv6 suppress code do pskb_may_pull. This means we have to\u000aalways reload it after the suppress code so there's no point in having\u000ait cached just retrieve it directly.\u000a\u000aFixes: 057658cb33fbf (\"bridge: suppress arp pkts on BR_NEIGH_SUPPRESS ports\")\u000aFixes: ed842faeb2bd (\"bridge: suppress nd pkts on BR_NEIGH_SUPPRESS ports\")\u000aSigned-off-by: Nikolay Aleksandrov \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:33 +0200", "id" : "17f2557801f833007a296ce96f133c1da7e1f489", "msg" : "net: bridge: don't cache ether dest pointer on input", "paths" : [ { "editType" : "edit", "file" : "net/bridge/br_input.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/bridge/br_stp_bpdu.c" ], "commitId" : "7edddedc3b87b9a2226893be6f94d06cf90d02c1", "timestamp" : 1564295314000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: bridge: stp: don't cache eth dest pointer before skb pull\u000a\u000a[ Upstream commit 2446a68ae6a8cee6d480e2f5b52f5007c7c41312 ]\u000a\u000aDon't cache eth dest pointer before calling pskb_may_pull.\u000a\u000aFixes: cf0f02d04a83 (\"[BRIDGE]: use llc for receiving STP packets\")\u000aSigned-off-by: Nikolay Aleksandrov \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:34 +0200", "id" : "7edddedc3b87b9a2226893be6f94d06cf90d02c1", "msg" : "net: bridge: stp: don't cache eth dest pointer before skb pull", "paths" : [ { "editType" : "edit", "file" : "net/bridge/br_stp_bpdu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/macsec.c" ], "commitId" : "a5e9991ff901aecead1fad8e5d31abaa8ad79856", "timestamp" : 1564295314000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "macsec: fix use-after-free of skb during RX\u000a\u000a[ Upstream commit 095c02da80a41cf6d311c504d8955d6d1c2add10 ]\u000a\u000aFix use-after-free of skb when rx_handler returns RX_HANDLER_PASS.\u000a\u000aSigned-off-by: Andreas Steinmetz \u000aAcked-by: Willem de Bruijn \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:34 +0200", "id" : "a5e9991ff901aecead1fad8e5d31abaa8ad79856", "msg" : "macsec: fix use-after-free of skb during RX", "paths" : [ { "editType" : "edit", "file" : "drivers/net/macsec.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/macsec.c" ], "commitId" : "961a727f2c1056195f8293db728d0ea9cf7c961d", "timestamp" : 1564295314000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "macsec: fix checksumming after decryption\u000a\u000a[ Upstream commit 7d8b16b9facb0dd81d1469808dd9a575fa1d525a ]\u000a\u000aFix checksumming after decryption.\u000a\u000aSigned-off-by: Andreas Steinmetz \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:34 +0200", "id" : "961a727f2c1056195f8293db728d0ea9cf7c961d", "msg" : "macsec: fix checksumming after decryption", "paths" : [ { "editType" : "edit", "file" : "drivers/net/macsec.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netrom/af_netrom.c" ], "commitId" : "897bcee6a1292b2a5d4e731ec5f12c6b97309465", "timestamp" : 1564295314000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "netrom: fix a memory leak in nr_rx_frame()\u000a\u000a[ Upstream commit c8c8218ec5af5d2598381883acbefbf604e56b5e ]\u000a\u000aWhen the skb is associated with a new sock, just assigning\u000ait to skb->sk is not sufficient, we have to set its destructor\u000ato free the sock properly too.\u000a\u000aReported-by: syzbot+d6636a36d3c34bd88938@syzkaller.appspotmail.com\u000aSigned-off-by: Cong Wang \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:34 +0200", "id" : "897bcee6a1292b2a5d4e731ec5f12c6b97309465", "msg" : "netrom: fix a memory leak in nr_rx_frame()", "paths" : [ { "editType" : "edit", "file" : "net/netrom/af_netrom.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/netrom/af_netrom.c" ], "commitId" : "1cec7a0cf072a8b0039abaa88c73256f6d82bf4e", "timestamp" : 1564295314000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "netrom: hold sock when setting skb->destructor\u000a\u000a[ Upstream commit 4638faac032756f7eab5524be7be56bee77e426b ]\u000a\u000asock_efree() releases the sock refcnt, if we don't hold this refcnt\u000awhen setting skb->destructor to it, the refcnt would not be balanced.\u000aThis leads to several bug reports from syzbot.\u000a\u000aI have checked other users of sock_efree(), all of them hold the\u000asock refcnt.\u000a\u000aFixes: c8c8218ec5af (\"netrom: fix a memory leak in nr_rx_frame()\")\u000aReported-and-tested-by: \u000aReported-and-tested-by: \u000aReported-and-tested-by: \u000aReported-and-tested-by: \u000aCc: Ralf Baechle \u000aSigned-off-by: Cong Wang \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:34 +0200", "id" : "1cec7a0cf072a8b0039abaa88c73256f6d82bf4e", "msg" : "netrom: hold sock when setting skb->destructor", "paths" : [ { "editType" : "edit", "file" : "net/netrom/af_netrom.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/testing/selftests/net/txring_overwrite.c" ], "commitId" : "d7728216dee122a21fe8732c4f202301a07cdd60", "timestamp" : 1564295314000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "selftests: txring_overwrite: fix incorrect test of mmap() return value\u000a\u000a[ Upstream commit cecaa76b2919aac2aa584ce476e9fcd5b084add5 ]\u000a\u000aIf mmap() fails it returns MAP_FAILED, which is defined as ((void *) -1).\u000aThe current if-statement incorrectly tests if *ring is NULL.\u000a\u000aFixes: 358be656406d (\"selftests/net: add txring_overwrite\")\u000aSigned-off-by: Frank de Brabander \u000aAcked-by: Willem de Bruijn \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:34 +0200", "id" : "d7728216dee122a21fe8732c4f202301a07cdd60", "msg" : "selftests: txring_overwrite: fix incorrect test of mmap() return value", "paths" : [ { "editType" : "edit", "file" : "tools/testing/selftests/net/txring_overwrite.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/tls/tls_sw.c" ], "commitId" : "53911428585db5042649fc568b2e12facc55d184", "timestamp" : 1564295315000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/tls: fix poll ignoring partially copied records\u000a\u000a[ Upstream commit 13aecb17acabc2a92187d08f7ca93bb8aad62c6f ]\u000a\u000aDavid reports that RPC applications which use epoll() occasionally\u000aget stuck, and that TLS ULP causes the kernel to not wake applications,\u000aeven though read() will return data.\u000a\u000aThis is indeed true. The ctx->rx_list which holds partially copied\u000arecords is not consulted when deciding whether socket is readable.\u000a\u000aNote that SO_RCVLOWAT with epoll() is and has always been broken for\u000akernel TLS. We'd need to parse all records from the TCP layer, instead\u000aof just the first one.\u000a\u000aFixes: 692d7b5d1f91 (\"tls: Fix recvmsg() to be able to peek across multiple records\")\u000aReported-by: David Beckett \u000aSigned-off-by: Jakub Kicinski \u000aReviewed-by: Dirk van der Merwe \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:35 +0200", "id" : "53911428585db5042649fc568b2e12facc55d184", "msg" : "net/tls: fix poll ignoring partially copied records", "paths" : [ { "editType" : "edit", "file" : "net/tls/tls_sw.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/tls/tls_device.c" ], "commitId" : "06ff90ba3c8c4ddd4d411ce5bea3a0fe3a34e0a3", "timestamp" : 1564295315000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/tls: reject offload of TLS 1.3\u000a\u000a[ Upstream commit 618bac45937a3dc6126ac0652747481e97000f99 ]\u000a\u000aNeither drivers nor the tls offload code currently supports TLS\u000aversion 1.3. Check the TLS version when installing connection\u000astate. TLS 1.3 will just fallback to the kernel crypto for now.\u000a\u000aFixes: 130b392c6cd6 (\"net: tls: Add tls 1.3 support\")\u000aSigned-off-by: Jakub Kicinski \u000aReviewed-by: Dirk van der Merwe \u000aSigned-off-by: David S. Miller \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:35 +0200", "id" : "06ff90ba3c8c4ddd4d411ce5bea3a0fe3a34e0a3", "msg" : "net/tls: reject offload of TLS 1.3", "paths" : [ { "editType" : "edit", "file" : "net/tls/tls_device.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlx5/core/lib/port_tun.c" ], "commitId" : "8c1dd131d9f818672d74e8a532e2fc5b01013b9a", "timestamp" : 1564295315000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/mlx5e: Fix port tunnel GRE entropy control\u000a\u000a[ Upstream commit 914adbb1bcf89478ac138318d28b302704564d59 ]\u000a\u000aGRE entropy calculation is a single bit per card, and not per port.\u000aForce disable GRE entropy calculation upon the first GRE encap rule,\u000aand release the force at the last GRE encap rule removal. This is done\u000aper port.\u000a\u000aFixes: 97417f6182f8 (\"net/mlx5e: Fix GRE key by controlling port tunnel entropy calculation\")\u000aSigned-off-by: Eli Britstein \u000aSigned-off-by: Saeed Mahameed \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:35 +0200", "id" : "8c1dd131d9f818672d74e8a532e2fc5b01013b9a", "msg" : "net/mlx5e: Fix port tunnel GRE entropy control", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/lib/port_tun.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlx5/core/en_rx.c", "include/linux/mlx5/mlx5_ifc.h", "drivers/net/ethernet/mellanox/mlx5/core/en.h", "drivers/net/ethernet/mellanox/mlx5/core/en_main.c" ], "commitId" : "2260ec46cd26dd98eabd16b3be183b33dde12017", "timestamp" : 1564295315000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/mlx5e: Rx, Fix checksum calculation for new hardware\u000a\u000a[ Upstream commit db849faa9bef993a1379dc510623f750a72fa7ce ]\u000a\u000aCQE checksum full mode in new HW, provides a full checksum of rx frame.\u000aCovering bytes starting from eth protocol up to last byte in the received\u000aframe (frame_size - ETH_HLEN), as expected by the stack.\u000a\u000aFixing up skb->csum by the driver is not required in such case. This fix\u000ais to avoid wrong checksum calculation in drivers which already support\u000athe new hardware with the new checksum mode.\u000a\u000aFixes: 85327a9c4150 (\"net/mlx5: Update the list of the PCI supported devices\")\u000aSigned-off-by: Saeed Mahameed \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:35 +0200", "id" : "2260ec46cd26dd98eabd16b3be183b33dde12017", "msg" : "net/mlx5e: Rx, Fix checksum calculation for new hardware", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/en.h" }, { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/en_rx.c" }, { "editType" : "edit", "file" : "include/linux/mlx5/mlx5_ifc.h" }, { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/en_main.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c" ], "commitId" : "d5596ded2ec330e3e72f5c541fc2e9eb4437275a", "timestamp" : 1564295315000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/mlx5e: Fix return value from timeout recover function\u000a\u000a[ Upstream commit 39825350ae2a52f8513741b36e42118bd80dd689 ]\u000a\u000aFix timeout recover function to return a meaningful return value.\u000aWhen an interrupt was not sent by the FW, return IO error instead of\u000a'true'.\u000a\u000aFixes: c7981bea48fb (\"net/mlx5e: Fix return status of TX reporter timeout recover\")\u000aSigned-off-by: Aya Levin \u000aAcked-by: Jiri Pirko \u000aReviewed-by: Tariq Toukan \u000aSigned-off-by: Saeed Mahameed \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:35 +0200", "id" : "d5596ded2ec330e3e72f5c541fc2e9eb4437275a", "msg" : "net/mlx5e: Fix return value from timeout recover function", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c" ], "commitId" : "2a782edf08b450b0da551802e31ab47ba4e58179", "timestamp" : 1564295315000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net/mlx5e: Fix error flow in tx reporter diagnose\u000a\u000a[ Upstream commit 99d31cbd8953c6929da978bf049ab0f0b4e503d9 ]\u000a\u000aFix tx reporter's diagnose callback. Propagate error when failing to\u000agather diagnostics information or failing to print diagnostic data per\u000aqueue.\u000a\u000aFixes: de8650a82071 (\"net/mlx5e: Add tx reporter support\")\u000aSigned-off-by: Aya Levin \u000aReviewed-by: Tariq Toukan \u000aAcked-by: Jiri Pirko \u000aSigned-off-by: Saeed Mahameed \u000aSigned-off-by: Greg Kroah-Hartman \u000a", "date" : "2019-07-28 08:28:35 +0200", "id" : "2a782edf08b450b0da551802e31ab47ba4e58179", "msg" : "net/mlx5e: Fix error flow in tx reporter diagnose", "paths" : [ { "editType" : "edit", "file" : "drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/dma-buf/dma-buf.c" ], "commitId" : "19fab82084e094800ceb5cb3e5f6411769524152", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dma-buf: balance refcount inbalance\u000a\u000acommit 5e383a9798990c69fc759a4930de224bb497e62c upstream.\u000a\u000aThe debugfs take reference on fence without dropping them.\u000a\u000aSigned-off-by: Jérôme Glisse \u000aCc: Christian König \u000aCc: Daniel Vetter \u000aCc: Sumit Semwal \u000aCc: linux-media@vger.kernel.org\u000aCc: dri-devel@lists.freedesktop.org\u000aCc: linaro-mm-sig@lists.linaro.org\u000aCc: Stéphane Marchesin \u000aCc: stable@vger.kernel.org\u000aReviewed-by: Christian König \u000aSigned-off-by: Sumit Semwal \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20181206161840.6578-1-jglisse@redhat.com\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "19fab82084e094800ceb5cb3e5f6411769524152", "msg" : "dma-buf: balance refcount inbalance", "paths" : [ { "editType" : "edit", "file" : "drivers/dma-buf/dma-buf.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/dma-buf/reservation.c" ], "commitId" : "4528cbb9659195c82bf80745e5abdc14e9ecbb79", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc\u000a\u000acommit f5b07b04e5f090a85d1e96938520f2b2b58e4a8e upstream.\u000a\u000aIf we have to drop the seqcount & rcu lock to perform a krealloc, we\u000ahave to restart the loop. In doing so, be careful not to lose track of\u000athe already acquired exclusive fence.\u000a\u000aFixes: fedf54132d24 (\"dma-buf: Restart reservation_object_get_fences_rcu() after writes\")\u000aSigned-off-by: Chris Wilson \u000aCc: Daniel Vetter \u000aCc: Maarten Lankhorst \u000aCc: Christian König \u000aCc: Alex Deucher \u000aCc: Sumit Semwal \u000aCc: stable@vger.kernel.org #v4.10\u000aReviewed-by: Christian König \u000aLink: https://patchwork.freedesktop.org/patch/msgid/20190604125323.21396-1-chris@chris-wilson.co.uk\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "4528cbb9659195c82bf80745e5abdc14e9ecbb79", "msg" : "dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc", "paths" : [ { "editType" : "edit", "file" : "drivers/dma-buf/reservation.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpiolib-of.c" ], "commitId" : "f39659f4b3b4742310550a4225bfebf41117f378", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpiolib: of: fix a memory leak in of_gpio_flags_quirks()\u000a\u000acommit 89fea04c85e85f21ef4937611055abce82330d48 upstream.\u000a\u000aEach iteration of for_each_child_of_node puts the previous node, but in\u000athe case of a break from the middle of the loop, there is no put, thus\u000acausing a memory leak. Hence add an of_node_put before the break.\u000aIssue found with Coccinelle.\u000a\u000aCc: \u000aSigned-off-by: Nishka Dasgupta \u000a[Bartosz: tweaked the commit message]\u000aSigned-off-by: Bartosz Golaszewski \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "f39659f4b3b4742310550a4225bfebf41117f378", "msg" : "gpiolib: of: fix a memory leak in of_gpio_flags_quirks()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpiolib-of.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpio/gpio-davinci.c" ], "commitId" : "dfc0a1b1013076fa14eec2fcc453e1f94d6ee400", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "gpio: davinci: silence error prints in case of EPROBE_DEFER\u000a\u000acommit 541e4095f388c196685685633c950cb9b97f8039 upstream.\u000a\u000aSilence error prints in case of EPROBE_DEFER. This avoids\u000amultiple/duplicate defer prints during boot.\u000a\u000aCc: \u000aSigned-off-by: Keerthy \u000aSigned-off-by: Bartosz Golaszewski \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "dfc0a1b1013076fa14eec2fcc453e1f94d6ee400", "msg" : "gpio: davinci: silence error prints in case of EPROBE_DEFER", "paths" : [ { "editType" : "edit", "file" : "drivers/gpio/gpio-davinci.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/mips/jz4740/board-qi_lb60.c" ], "commitId" : "8206c6c1b7745871ce9875ae4f8aa85a88022423", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "MIPS: lb60: Fix pin mappings\u000a\u000acommit 1323c3b72a987de57141cabc44bf9cd83656bc70 upstream.\u000a\u000aThe pin mappings introduced in commit 636f8ba67fb6\u000a(\"MIPS: JZ4740: Qi LB60: Add pinctrl configuration for several drivers\")\u000aare completely wrong. The pinctrl driver name is incorrect, and the\u000afunction and group fields are swapped.\u000a\u000aFixes: 636f8ba67fb6 (\"MIPS: JZ4740: Qi LB60: Add pinctrl configuration for several drivers\")\u000aCc: \u000aSigned-off-by: Paul Cercueil \u000aReviewed-by: Linus Walleij \u000aSigned-off-by: Paul Burton \u000aCc: Ralf Baechle \u000aCc: James Hogan \u000aCc: od@zcrc.me\u000aCc: linux-mips@vger.kernel.org\u000aCc: linux-kernel@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "8206c6c1b7745871ce9875ae4f8aa85a88022423", "msg" : "MIPS: lb60: Fix pin mappings", "paths" : [ { "editType" : "edit", "file" : "arch/mips/jz4740/board-qi_lb60.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "tools/perf/builtin-script.c" ], "commitId" : "5c008c97dae1933a487511672ad734a450808b4a", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf script: Assume native_arch for pipe mode\u000a\u000acommit 9d49169c5958e429ffa6874fbef734ae7502ad65 upstream.\u000a\u000aIn pipe mode, session->header.env.arch is not populated until the events\u000aare processed. Therefore, the following command crashes:\u000a\u000a perf record -o - | perf script\u000a\u000a(gdb) bt\u000a\u000aIt fails when we try to compare env.arch against uts.machine:\u000a\u000a if (!strcmp(uts.machine, session->header.env.arch) ||\u000a (!strcmp(uts.machine, \"x86_64\") &&\u000a !strcmp(session->header.env.arch, \"i386\")))\u000a native_arch = true;\u000a\u000aIn pipe mode, it is tricky to find env.arch at this stage. To keep it\u000asimple, let's just assume native_arch is always true for pipe mode.\u000a\u000aReported-by: David Carrillo Cisneros \u000aSigned-off-by: Song Liu \u000aTested-by: Arnaldo Carvalho de Melo \u000aCc: Andi Kleen \u000aCc: Jiri Olsa \u000aCc: Namhyung Kim \u000aCc: kernel-team@fb.com\u000aCc: stable@vger.kernel.org #v5.1+\u000aFixes: 3ab481a1cfe1 (\"perf script: Support insn output for normal samples\")\u000aLink: http://lkml.kernel.org/r/20190621014438.810342-1-songliubraving@fb.com\u000aSigned-off-by: Arnaldo Carvalho de Melo \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "5c008c97dae1933a487511672ad734a450808b4a", "msg" : "perf script: Assume native_arch for pipe mode", "paths" : [ { "editType" : "edit", "file" : "tools/perf/builtin-script.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/perf_event.h", "kernel/events/core.c" ], "commitId" : "421db87843e6f1885cebccd64ff29dddd1d77818", "timestamp" : 1564295316000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/core: Fix exclusive events' grouping\u000a\u000acommit 8a58ddae23796c733c5dfbd717538d89d036c5bd upstream.\u000a\u000aSo far, we tried to disallow grouping exclusive events for the fear of\u000acomplications they would cause with moving between contexts. Specifically,\u000amoving a software group to a hardware context would violate the exclusivity\u000arules if both groups contain matching exclusive events.\u000a\u000aThis attempt was, however, unsuccessful: the check that we have in the\u000aperf_event_open() syscall is both wrong (looks at wrong PMU) and\u000ainsufficient (group leader may still be exclusive), as can be illustrated\u000aby running:\u000a\u000a $ perf record -e '{intel_pt//,cycles}' uname\u000a $ perf record -e '{cycles,intel_pt//}' uname\u000a\u000aultimately successfully.\u000a\u000aFurthermore, we are completely free to trigger the exclusivity violation\u000aby:\u000a\u000a perf -e '{cycles,intel_pt//}' -e '{intel_pt//,instructions}'\u000a\u000aeven though the helpful perf record will not allow that, the ABI will.\u000a\u000aThe warning later in the perf_event_open() path will also not trigger, because\u000ait's also wrong.\u000a\u000aFix all this by validating the original group before moving, getting rid\u000aof broken safeguards and placing a useful one to perf_install_in_context().\u000a\u000aSigned-off-by: Alexander Shishkin \u000aSigned-off-by: Peter Zijlstra (Intel) \u000aCc: \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Stephane Eranian \u000aCc: Thomas Gleixner \u000aCc: Vince Weaver \u000aCc: mathieu.poirier@linaro.org\u000aCc: will.deacon@arm.com\u000aFixes: bed5b25ad9c8a (\"perf: Add a pmu capability for \"exclusive\" events\")\u000aLink: https://lkml.kernel.org/r/20190701110755.24646-1-alexander.shishkin@linux.intel.com\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:36 +0200", "id" : "421db87843e6f1885cebccd64ff29dddd1d77818", "msg" : "perf/core: Fix exclusive events' grouping", "paths" : [ { "editType" : "edit", "file" : "include/linux/perf_event.h" }, { "editType" : "edit", "file" : "kernel/events/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "kernel/events/core.c" ], "commitId" : "539f1257906624abdcc81aeb91276791e543bfac", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "perf/core: Fix race between close() and fork()\u000a\u000acommit 1cf8dfe8a661f0462925df943140e9f6d1ea5233 upstream.\u000a\u000aSyzcaller reported the following Use-after-Free bug:\u000a\u000a\u0009close()\u0009\u0009\u0009\u0009\u0009\u0009clone()\u000a\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 copy_process()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 perf_event_init_task()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 perf_event_init_context()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 mutex_lock(parent_ctx->mutex)\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009inherit_task_group()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009 inherit_group()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009 inherit_event()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009 mutex_lock(event->child_mutex)\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009 // expose event on child list\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009 list_add_tail()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009\u0009 mutex_unlock(event->child_mutex)\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 mutex_unlock(parent_ctx->mutex)\u000a\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 ...\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 goto bad_fork_*\u000a\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 bad_fork_cleanup_perf:\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 perf_event_free_task()\u000a\u000a\u0009 perf_release()\u000a\u0009 perf_event_release_kernel()\u000a\u0009 list_for_each_entry()\u000a\u0009\u0009mutex_lock(ctx->mutex)\u000a\u0009\u0009mutex_lock(event->child_mutex)\u000a\u0009\u0009// event is from the failing inherit\u000a\u0009\u0009// on the other CPU\u000a\u0009\u0009perf_remove_from_context()\u000a\u0009\u0009list_move()\u000a\u0009\u0009mutex_unlock(event->child_mutex)\u000a\u0009\u0009mutex_unlock(ctx->mutex)\u000a\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 mutex_lock(ctx->mutex)\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 list_for_each_entry_safe()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 // event already stolen\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 mutex_unlock(ctx->mutex)\u000a\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 delayed_free_task()\u000a\u0009\u0009\u0009\u0009\u0009\u0009\u0009 free_task()\u000a\u000a\u0009 list_for_each_entry_safe()\u000a\u0009 list_del()\u000a\u0009 free_event()\u000a\u0009 _free_event()\u000a\u0009\u0009 // and so event->hw.target\u000a\u0009\u0009 // is the already freed failed clone()\u000a\u0009\u0009 if (event->hw.target)\u000a\u0009\u0009 put_task_struct(event->hw.target)\u000a\u0009\u0009 // WHOOPSIE, already quite dead\u000a\u000aWhich puts the lie to the the comment on perf_event_free_task():\u000a'unexposed, unused context' not so much.\u000a\u000aWhich is a 'fun' confluence of fail; copy_process() doing an\u000aunconditional free_task() and not respecting refcounts, and perf having\u000acreative locking. In particular:\u000a\u000a 82d94856fa22 (\"perf/core: Fix lock inversion between perf,trace,cpuhp\")\u000a\u000aseems to have overlooked this 'fun' parade.\u000a\u000aSolve it by using the fact that detached events still have a reference\u000acount on their (previous) context. With this perf_event_free_task()\u000acan detect when events have escaped and wait for their destruction.\u000a\u000aDebugged-by: Alexander Shishkin \u000aReported-by: syzbot+a24c397a29ad22d86c98@syzkaller.appspotmail.com\u000aSigned-off-by: Peter Zijlstra (Intel) \u000aAcked-by: Mark Rutland \u000aCc: \u000aCc: Alexander Shishkin \u000aCc: Arnaldo Carvalho de Melo \u000aCc: Jiri Olsa \u000aCc: Linus Torvalds \u000aCc: Peter Zijlstra \u000aCc: Stephane Eranian \u000aCc: Thomas Gleixner \u000aCc: Vince Weaver \u000aFixes: 82d94856fa22 (\"perf/core: Fix lock inversion between perf,trace,cpuhp\")\u000aSigned-off-by: Ingo Molnar \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "539f1257906624abdcc81aeb91276791e543bfac", "msg" : "perf/core: Fix race between close() and fork()", "paths" : [ { "editType" : "edit", "file" : "kernel/events/core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/ext4/ioctl.c" ], "commitId" : "e5723ddf999e8dd51e6494dfe8ee39bfccac8a35", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ext4: don't allow any modifications to an immutable file\u000a\u000acommit 2e53840362771c73eb0a5ff71611507e64e8eecd upstream.\u000a\u000aDon't allow any modifications to a file that's marked immutable, which\u000ameans that we have to flush all the writable pages to make the readonly\u000aand we have to check the setattr/setflags parameters more closely.\u000a\u000aSigned-off-by: Darrick J. Wong \u000aSigned-off-by: Theodore Ts'o \u000aCc: stable@kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "e5723ddf999e8dd51e6494dfe8ee39bfccac8a35", "msg" : "ext4: don't allow any modifications to an immutable file", "paths" : [ { "editType" : "edit", "file" : "fs/ext4/ioctl.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/ext4/file.c", "fs/ext4/inode.c" ], "commitId" : "3d762b2af4824ef9e124c3c66c9eff7d2f2e470e", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ext4: enforce the immutable flag on open files\u000a\u000acommit 02b016ca7f99229ae6227e7b2fc950c4e140d74a upstream.\u000a\u000aAccording to the chattr man page, \"a file with the 'i' attribute\u000acannot be modified...\" Historically, this was only enforced when the\u000afile was opened, per the rest of the description, \"... and the file\u000acan not be opened in write mode\".\u000a\u000aThere is general agreement that we should standardize all file systems\u000ato prevent modifications even for files that were opened at the time\u000athe immutable flag is set. Eventually, a change to enforce this at\u000athe VFS layer should be landing in mainline. Until then, enforce this\u000aat the ext4 level to prevent xfstests generic/553 from failing.\u000a\u000aSigned-off-by: Theodore Ts'o \u000aCc: \"Darrick J. Wong\" \u000aCc: stable@kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "3d762b2af4824ef9e124c3c66c9eff7d2f2e470e", "msg" : "ext4: enforce the immutable flag on open files", "paths" : [ { "editType" : "edit", "file" : "fs/ext4/file.c" }, { "editType" : "edit", "file" : "fs/ext4/inode.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "mm/filemap.c", "include/linux/fs.h" ], "commitId" : "4d15f68ab90d1cb72f1834f65d35b6b4f5eae017", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mm: add filemap_fdatawait_range_keep_errors()\u000a\u000acommit aa0bfcd939c30617385ffa28682c062d78050eba upstream.\u000a\u000aIn the spirit of filemap_fdatawait_range() and\u000afilemap_fdatawait_keep_errors(), introduce\u000afilemap_fdatawait_range_keep_errors() which both takes a range upon\u000awhich to wait and does not clear errors from the address space.\u000a\u000aSigned-off-by: Ross Zwisler \u000aSigned-off-by: Theodore Ts'o \u000aReviewed-by: Jan Kara \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "4d15f68ab90d1cb72f1834f65d35b6b4f5eae017", "msg" : "mm: add filemap_fdatawait_range_keep_errors()", "paths" : [ { "editType" : "edit", "file" : "include/linux/fs.h" }, { "editType" : "edit", "file" : "mm/filemap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/jbd2/journal.c", "fs/jbd2/commit.c", "fs/jbd2/transaction.c", "include/linux/jbd2.h" ], "commitId" : "cb9663114c534c1331f3e47b11ea8a34fa78612d", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "jbd2: introduce jbd2_inode dirty range scoping\u000a\u000acommit 6ba0e7dc64a5adcda2fbe65adc466891795d639e upstream.\u000a\u000aCurrently both journal_submit_inode_data_buffers() and\u000ajournal_finish_inode_data_buffers() operate on the entire address space\u000aof each of the inodes associated with a given journal entry. The\u000aconsequence of this is that if we have an inode where we are constantly\u000aappending dirty pages we can end up waiting for an indefinite amount of\u000atime in journal_finish_inode_data_buffers() while we wait for all the\u000apages under writeback to be written out.\u000a\u000aThe easiest way to cause this type of workload is do just dd from\u000a/dev/zero to a file until it fills the entire filesystem. This can\u000acause journal_finish_inode_data_buffers() to wait for the duration of\u000athe entire dd operation.\u000a\u000aWe can improve this situation by scoping each of the inode dirty ranges\u000aassociated with a given transaction. We do this via the jbd2_inode\u000astructure so that the scoping is contained within jbd2 and so that it\u000afollows the lifetime and locking rules for that structure.\u000a\u000aThis allows us to limit the writeback & wait in\u000ajournal_submit_inode_data_buffers() and\u000ajournal_finish_inode_data_buffers() respectively to the dirty range for\u000aa given struct jdb2_inode, keeping us from waiting forever if the inode\u000ain question is still being appended to.\u000a\u000aSigned-off-by: Ross Zwisler \u000aSigned-off-by: Theodore Ts'o \u000aReviewed-by: Jan Kara \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "cb9663114c534c1331f3e47b11ea8a34fa78612d", "msg" : "jbd2: introduce jbd2_inode dirty range scoping", "paths" : [ { "editType" : "edit", "file" : "fs/jbd2/transaction.c" }, { "editType" : "edit", "file" : "include/linux/jbd2.h" }, { "editType" : "edit", "file" : "fs/jbd2/journal.c" }, { "editType" : "edit", "file" : "fs/jbd2/commit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/ext4/ext4_jbd2.h", "fs/ext4/move_extent.c", "fs/ext4/inode.c" ], "commitId" : "4c95bc41baca2a7570deb0414cf30e7c50942d5e", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ext4: use jbd2_inode dirty range scoping\u000a\u000acommit 73131fbb003b3691cfcf9656f234b00da497fcd6 upstream.\u000a\u000aUse the newly introduced jbd2_inode dirty range scoping to prevent us\u000afrom waiting forever when trying to complete a journal transaction.\u000a\u000aSigned-off-by: Ross Zwisler \u000aSigned-off-by: Theodore Ts'o \u000aReviewed-by: Jan Kara \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "4c95bc41baca2a7570deb0414cf30e7c50942d5e", "msg" : "ext4: use jbd2_inode dirty range scoping", "paths" : [ { "editType" : "edit", "file" : "fs/ext4/ext4_jbd2.h" }, { "editType" : "edit", "file" : "fs/ext4/inode.c" }, { "editType" : "edit", "file" : "fs/ext4/move_extent.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "fs/ext4/dir.c", "fs/ext4/namei.c" ], "commitId" : "7f1f86276515f6816a98f6ca3ef99c827d54642f", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "ext4: allow directory holes\u000a\u000acommit 4e19d6b65fb4fc42e352ce9883649e049da14743 upstream.\u000a\u000aThe largedir feature was intended to allow ext4 directories to have\u000aunmapped directory blocks (e.g., directory holes). And so the\u000areleased e2fsprogs no longer enforces this for largedir file systems;\u000ahowever, the corresponding change to the kernel-side code was not made.\u000a\u000aThis commit fixes this oversight.\u000a\u000aSigned-off-by: Theodore Ts'o \u000aCc: stable@kernel.org\u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "7f1f86276515f6816a98f6ca3ef99c827d54642f", "msg" : "ext4: allow directory holes", "paths" : [ { "editType" : "edit", "file" : "fs/ext4/dir.c" }, { "editType" : "edit", "file" : "fs/ext4/namei.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/nested.c" ], "commitId" : "93e7720cc238bfb9784bb2b8d340b4595e7891b1", "timestamp" : 1564295317000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: nVMX: do not use dangling shadow VMCS after guest reset\u000a\u000acommit 88dddc11a8d6b09201b4db9d255b3394d9bc9e57 upstream.\u000a\u000aIf a KVM guest is reset while running a nested guest, free_nested will\u000adisable the shadow VMCS execution control in the vmcs01. However,\u000aon the next KVM_RUN vmx_vcpu_run would nevertheless try to sync\u000athe VMCS12 to the shadow VMCS which has since been freed.\u000a\u000aThis causes a vmptrld of a NULL pointer on my machime, but Jan reports\u000athe host to hang altogether. Let's see how much this trivial patch fixes.\u000a\u000aReported-by: Jan Kiszka \u000aCc: Liran Alon \u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:37 +0200", "id" : "93e7720cc238bfb9784bb2b8d340b4595e7891b1", "msg" : "KVM: nVMX: do not use dangling shadow VMCS after guest reset", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/nested.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/vmx/nested.c" ], "commitId" : "79a431342a92c98f96a6a35ffda37b25ab0fecbe", "timestamp" : 1564295318000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested\u000a\u000acommit cf64527bb33f6cec2ed50f89182fc4688d0056b6 upstream.\u000a\u000aLetting this pend may cause nested_get_vmcs12_pages to run against an\u000ainvalid state, corrupting the effective vmcs of L1.\u000a\u000aThis was triggerable in QEMU after a guest corruption in L2, followed by\u000aa L1 reset.\u000a\u000aSigned-off-by: Jan Kiszka \u000aReviewed-by: Liran Alon \u000aCc: stable@vger.kernel.org\u000aFixes: 7f7f1ba33cf2 (\"KVM: x86: do not load vmcs12 pages while still in SMM\")\u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:38 +0200", "id" : "79a431342a92c98f96a6a35ffda37b25ab0fecbe", "msg" : "KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/vmx/nested.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/x86/kvm/x86.c", "arch/x86/include/asm/kvm_host.h" ], "commitId" : "644688604559a6db751b9f26dcc8d38b8c439b0e", "timestamp" : 1564295318000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Revert \"kvm: x86: Use task structs fpu field for user\"\u000a\u000acommit ec269475cba7bcdd1eb8fdf8e87f4c6c81a376fe upstream.\u000a\u000aThis reverts commit 240c35a3783ab9b3a0afaba0dde7291295680a6b\u000a(\"kvm: x86: Use task structs fpu field for user\", 2018-11-06).\u000aThe commit is broken and causes QEMU's FPU state to be destroyed\u000awhen KVM_RUN is preempted.\u000a\u000aFixes: 240c35a3783a (\"kvm: x86: Use task structs fpu field for user\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Paolo Bonzini \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:38 +0200", "id" : "644688604559a6db751b9f26dcc8d38b8c439b0e", "msg" : "Revert \"kvm: x86: Use task structs fpu field for user\"", "paths" : [ { "editType" : "edit", "file" : "arch/x86/kvm/x86.c" }, { "editType" : "edit", "file" : "arch/x86/include/asm/kvm_host.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/scsi/sd_zbc.c" ], "commitId" : "fda734287b0d0cf9a303c29e85fdc7f0b044f26d", "timestamp" : 1564295318000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "sd_zbc: Fix report zones buffer allocation\u000a\u000acommit b091ac616846a1da75b1f2566b41255ce7f0e0a6 upstream.\u000a\u000aDuring disk scan and revalidation done with sd_revalidate(), the zones\u000aof a zoned disk are checked using the helper function\u000ablk_revalidate_disk_zones() if a configuration change is detected\u000a(change in the number of zones or zone size). The function\u000ablk_revalidate_disk_zones() issues report_zones calls that are very\u000alarge, that is, to obtain zone information for all zones of the disk\u000awith a single command. The size of the report zones command buffer\u000anecessary for such large request generally is lower than the disk\u000amax_hw_sectors and KMALLOC_MAX_SIZE (4MB) and succeeds on boot (no\u000amemory fragmentation), but often fail at run time (e.g. hot-plug\u000aevent). This causes the disk revalidation to fail and the disk\u000acapacity to be changed to 0.\u000a\u000aThis problem can be avoided by using vmalloc() instead of kmalloc() for\u000athe buffer allocation. To limit the amount of memory to be allocated,\u000athis patch also introduces the arbitrary SD_ZBC_REPORT_MAX_ZONES\u000amaximum number of zones to report with a single report zones command.\u000aThis limit may be lowered further to satisfy the disk max_hw_sectors\u000alimit. Finally, to ensure that the vmalloc-ed buffer can always be\u000amapped in a request, the buffer size is further limited to at most\u000aqueue_max_segments() pages, allowing successful mapping of the buffer\u000aeven in the worst case scenario where none of the buffer pages are\u000acontiguous.\u000a\u000aFixes: 515ce6061312 (\"scsi: sd_zbc: Fix sd_zbc_report_zones() buffer allocation\")\u000aFixes: e76239a3748c (\"block: add a report_zones method\")\u000aCc: stable@vger.kernel.org\u000aReviewed-by: Christoph Hellwig \u000aReviewed-by: Martin K. Petersen \u000aSigned-off-by: Damien Le Moal \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a\u000a", "date" : "2019-07-28 08:28:38 +0200", "id" : "fda734287b0d0cf9a303c29e85fdc7f0b044f26d", "msg" : "sd_zbc: Fix report zones buffer allocation", "paths" : [ { "editType" : "edit", "file" : "drivers/scsi/sd_zbc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "include/linux/blkdev.h", "block/blk-zoned.c" ], "commitId" : "14700c35fb6b7ef42189f79f9b5e0613629c6deb", "timestamp" : 1564295318000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "block: Limit zone array allocation size\u000a\u000acommit 26202928fafad8bda8b478edb7e62c885be623d7 upstream.\u000a\u000aLimit the size of the struct blk_zone array used in\u000ablk_revalidate_disk_zones() to avoid memory allocation failures leading\u000ato disk revalidation failure. Also further reduce the likelyhood of\u000asuch failures by using kvcalloc() (that is vmalloc()) instead of\u000aallocating contiguous pages with alloc_pages().\u000a\u000aFixes: 515ce6061312 (\"scsi: sd_zbc: Fix sd_zbc_report_zones() buffer allocation\")\u000aFixes: e76239a3748c (\"block: add a report_zones method\")\u000aCc: stable@vger.kernel.org\u000aReviewed-by: Christoph Hellwig \u000aReviewed-by: Martin K. Petersen \u000aSigned-off-by: Damien Le Moal \u000aSigned-off-by: Jens Axboe \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:38 +0200", "id" : "14700c35fb6b7ef42189f79f9b5e0613629c6deb", "msg" : "block: Limit zone array allocation size", "paths" : [ { "editType" : "edit", "file" : "block/blk-zoned.c" }, { "editType" : "edit", "file" : "include/linux/blkdev.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "mm/vmscan.c" ], "commitId" : "b4dd6aae6f930e5d4b02d4b34489621c38ea3158", "timestamp" : 1564295318000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "mm: vmscan: scan anonymous pages on file refaults\u000a\u000acommit 2c012a4ad1a2cd3fb5a0f9307b9d219f84eda1fa upstream.\u000a\u000aWhen file refaults are detected and there are many inactive file pages,\u000athe system never reclaim anonymous pages, the file pages are dropped\u000aaggressively when there are still a lot of cold anonymous pages and\u000asystem thrashes. This issue impacts the performance of applications\u000awith large executable, e.g. chrome.\u000a\u000aWith this patch, when file refault is detected, inactive_list_is_low()\u000aalways returns true for file pages in get_scan_count() to enable\u000ascanning anonymous pages.\u000a\u000aThe problem can be reproduced by the following test program.\u000a\u000a---8<---\u000avoid fallocate_file(const char *filename, off_t size)\u000a{\u000a\u0009struct stat st;\u000a\u0009int fd;\u000a\u000a\u0009if (!stat(filename, &st) && st.st_size >= size)\u000a\u0009\u0009return;\u000a\u000a\u0009fd = open(filename, O_WRONLY | O_CREAT, 0600);\u000a\u0009if (fd < 0) {\u000a\u0009\u0009perror(\"create file\");\u000a\u0009\u0009exit(1);\u000a\u0009}\u000a\u0009if (posix_fallocate(fd, 0, size)) {\u000a\u0009\u0009perror(\"fallocate\");\u000a\u0009\u0009exit(1);\u000a\u0009}\u000a\u0009close(fd);\u000a}\u000a\u000along *alloc_anon(long size)\u000a{\u000a\u0009long *start = malloc(size);\u000a\u0009memset(start, 1, size);\u000a\u0009return start;\u000a}\u000a\u000along access_file(const char *filename, long size, long rounds)\u000a{\u000a\u0009int fd, i;\u000a\u0009volatile char *start1, *end1, *start2;\u000a\u0009const int page_size = getpagesize();\u000a\u0009long sum = 0;\u000a\u000a\u0009fd = open(filename, O_RDONLY);\u000a\u0009if (fd == -1) {\u000a\u0009\u0009perror(\"open\");\u000a\u0009\u0009exit(1);\u000a\u0009}\u000a\u000a\u0009/*\u000a\u0009 * Some applications, e.g. chrome, use a lot of executable file\u000a\u0009 * pages, map some of the pages with PROT_EXEC flag to simulate\u000a\u0009 * the behavior.\u000a\u0009 */\u000a\u0009start1 = mmap(NULL, size / 2, PROT_READ | PROT_EXEC, MAP_SHARED,\u000a\u0009\u0009 fd, 0);\u000a\u0009if (start1 == MAP_FAILED) {\u000a\u0009\u0009perror(\"mmap\");\u000a\u0009\u0009exit(1);\u000a\u0009}\u000a\u0009end1 = start1 + size / 2;\u000a\u000a\u0009start2 = mmap(NULL, size / 2, PROT_READ, MAP_SHARED, fd, size / 2);\u000a\u0009if (start2 == MAP_FAILED) {\u000a\u0009\u0009perror(\"mmap\");\u000a\u0009\u0009exit(1);\u000a\u0009}\u000a\u000a\u0009for (i = 0; i < rounds; ++i) {\u000a\u0009\u0009struct timeval before, after;\u000a\u0009\u0009volatile char *ptr1 = start1, *ptr2 = start2;\u000a\u0009\u0009gettimeofday(&before, NULL);\u000a\u0009\u0009for (; ptr1 < end1; ptr1 += page_size, ptr2 += page_size)\u000a\u0009\u0009\u0009sum += *ptr1 + *ptr2;\u000a\u0009\u0009gettimeofday(&after, NULL);\u000a\u0009\u0009printf(\"File access time, round %d: %f (sec)\u000a\", i,\u000a\u0009\u0009 (after.tv_sec - before.tv_sec) +\u000a\u0009\u0009 (after.tv_usec - before.tv_usec) / 1000000.0);\u000a\u0009}\u000a\u0009return sum;\u000a}\u000a\u000aint main(int argc, char *argv[])\u000a{\u000a\u0009const long MB = 1024 * 1024;\u000a\u0009long anon_mb, file_mb, file_rounds;\u000a\u0009const char filename[] = \"large\";\u000a\u0009long *ret1;\u000a\u0009long ret2;\u000a\u000a\u0009if (argc != 4) {\u000a\u0009\u0009printf(\"usage: thrash ANON_MB FILE_MB FILE_ROUNDS\u000a\");\u000a\u0009\u0009exit(0);\u000a\u0009}\u000a\u0009anon_mb = atoi(argv[1]);\u000a\u0009file_mb = atoi(argv[2]);\u000a\u0009file_rounds = atoi(argv[3]);\u000a\u000a\u0009fallocate_file(filename, file_mb * MB);\u000a\u0009printf(\"Allocate %ld MB anonymous pages\u000a\", anon_mb);\u000a\u0009ret1 = alloc_anon(anon_mb * MB);\u000a\u0009printf(\"Access %ld MB file pages\u000a\", file_mb);\u000a\u0009ret2 = access_file(filename, file_mb * MB, file_rounds);\u000a\u0009printf(\"Print result to prevent optimization: %ld\u000a\",\u000a\u0009 *ret1 + ret2);\u000a\u0009return 0;\u000a}\u000a---8<---\u000a\u000aRunning the test program on 2GB RAM VM with kernel 5.2.0-rc5, the program\u000afills ram with 2048 MB memory, access a 200 MB file for 10 times. Without\u000athis patch, the file cache is dropped aggresively and every access to the\u000afile is from disk.\u000a\u000a $ ./thrash 2048 200 10\u000a Allocate 2048 MB anonymous pages\u000a Access 200 MB file pages\u000a File access time, round 0: 2.489316 (sec)\u000a File access time, round 1: 2.581277 (sec)\u000a File access time, round 2: 2.487624 (sec)\u000a File access time, round 3: 2.449100 (sec)\u000a File access time, round 4: 2.420423 (sec)\u000a File access time, round 5: 2.343411 (sec)\u000a File access time, round 6: 2.454833 (sec)\u000a File access time, round 7: 2.483398 (sec)\u000a File access time, round 8: 2.572701 (sec)\u000a File access time, round 9: 2.493014 (sec)\u000a\u000aWith this patch, these file pages can be cached.\u000a\u000a $ ./thrash 2048 200 10\u000a Allocate 2048 MB anonymous pages\u000a Access 200 MB file pages\u000a File access time, round 0: 2.475189 (sec)\u000a File access time, round 1: 2.440777 (sec)\u000a File access time, round 2: 2.411671 (sec)\u000a File access time, round 3: 1.955267 (sec)\u000a File access time, round 4: 0.029924 (sec)\u000a File access time, round 5: 0.000808 (sec)\u000a File access time, round 6: 0.000771 (sec)\u000a File access time, round 7: 0.000746 (sec)\u000a File access time, round 8: 0.000738 (sec)\u000a File access time, round 9: 0.000747 (sec)\u000a\u000aChecked the swap out stats during the test [1], 19006 pages swapped out\u000awith this patch, 3418 pages swapped out without this patch. There are\u000amore swap out, but I think it's within reasonable range when file backed\u000adata set doesn't fit into the memory.\u000a\u000a$ ./thrash 2000 100 2100 5 1 # ANON_MB FILE_EXEC FILE_NOEXEC ROUNDS\u000aPROCESSES Allocate 2000 MB anonymous pages active_anon: 1613644,\u000ainactive_anon: 348656, active_file: 892, inactive_file: 1384 (kB)\u000apswpout: 7972443, pgpgin: 478615246 Access 100 MB executable file pages\u000aAccess 2100 MB regular file pages File access time, round 0: 12.165,\u000a(sec) active_anon: 1433788, inactive_anon: 478116, active_file: 17896,\u000ainactive_file: 24328 (kB) File access time, round 1: 11.493, (sec)\u000aactive_anon: 1430576, inactive_anon: 477144, active_file: 25440,\u000ainactive_file: 26172 (kB) File access time, round 2: 11.455, (sec)\u000aactive_anon: 1427436, inactive_anon: 476060, active_file: 21112,\u000ainactive_file: 28808 (kB) File access time, round 3: 11.454, (sec)\u000aactive_anon: 1420444, inactive_anon: 473632, active_file: 23216,\u000ainactive_file: 35036 (kB) File access time, round 4: 11.479, (sec)\u000aactive_anon: 1413964, inactive_anon: 471460, active_file: 31728,\u000ainactive_file: 32224 (kB) pswpout: 7991449 (+ 19006), pgpgin: 489924366\u000a(+ 11309120)\u000a\u000aWith 4 processes accessing non-overlapping parts of a large file, 30316\u000apages swapped out with this patch, 5152 pages swapped out without this\u000apatch. The swapout number is small comparing to pgpgin.\u000a\u000a[1]: https://github.com/vovo/testing/blob/master/mem_thrash.c\u000a\u000aLink: http://lkml.kernel.org/r/20190701081038.GA83398@google.com\u000aFixes: e9868505987a (\"mm,vmscan: only evict file pages when we have plenty\")\u000aFixes: 7c5bd705d8f9 (\"mm: memcg: only evict file pages when we have plenty\")\u000aSigned-off-by: Kuo-Hsin Yang \u000aAcked-by: Johannes Weiner \u000aCc: Michal Hocko \u000aCc: Sonny Rao \u000aCc: Mel Gorman \u000aCc: Rik van Riel \u000aCc: Vladimir Davydov \u000aCc: Minchan Kim \u000aCc: \u0009[4.12+]\u000aSigned-off-by: Andrew Morton \u000aSigned-off-by: Linus Torvalds \u000a[backported to 4.14.y, 4.19.y, 5.1.y: adjust context]\u000aSigned-off-by: Kuo-Hsin Yang \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:38 +0200", "id" : "b4dd6aae6f930e5d4b02d4b34489621c38ea3158", "msg" : "mm: vmscan: scan anonymous pages on file refaults", "paths" : [ { "editType" : "edit", "file" : "mm/vmscan.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "net/sched/cls_api.c" ], "commitId" : "51d036eb719b258bd5bc2be3a243a22c7368abad", "timestamp" : 1564295318000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "net: sched: verify that q!=NULL before setting q->flags\u000a\u000acommit 503d81d428bd598430f7f9d02021634e1a8139a0 upstream.\u000a\u000aIn function int tc_new_tfilter() q pointer can be NULL when adding filter\u000aon a shared block. With recent change that resets TCQ_F_CAN_BYPASS after\u000afilter creation, following NULL pointer dereference happens in case parent\u000ablock is shared:\u000a\u000a[ 212.925060] BUG: kernel NULL pointer dereference, address: 0000000000000010\u000a[ 212.925445] #PF: supervisor write access in kernel mode\u000a[ 212.925709] #PF: error_code(0x0002) - not-present page\u000a[ 212.925965] PGD 8000000827923067 P4D 8000000827923067 PUD 827924067 PMD 0\u000a[ 212.926302] Oops: 0002 [#1] SMP KASAN PTI\u000a[ 212.926539] CPU: 18 PID: 2617 Comm: tc Tainted: G B 5.2.0+ #512\u000a[ 212.926938] Hardware name: Supermicro SYS-2028TP-DECR/X10DRT-P, BIOS 2.0b 03/30/2017\u000a[ 212.927364] RIP: 0010:tc_new_tfilter+0x698/0xd40\u000a[ 212.927633] Code: 74 0d 48 85 c0 74 08 48 89 ef e8 03 aa 62 00 48 8b 84 24 a0 00 00 00 48 8d 78 10 48 89 44 24 18 e8 4d 0c 6b ff 48 8b 44 24 18 <83> 60 10 f\u000ab 48 85 ed 0f 85 3d fe ff ff e9 4f fe ff ff e8 81 26 f8\u000a[ 212.928607] RSP: 0018:ffff88884fd5f5d8 EFLAGS: 00010296\u000a[ 212.928905] RAX: 0000000000000000 RBX: 0000000000000000 RCX: dffffc0000000000\u000a[ 212.929201] RDX: 0000000000000007 RSI: 0000000000000004 RDI: 0000000000000297\u000a[ 212.929402] RBP: ffff88886bedd600 R08: ffffffffb91d4b51 R09: fffffbfff7616e4d\u000a[ 212.929609] R10: fffffbfff7616e4c R11: ffffffffbb0b7263 R12: ffff88886bc61040\u000a[ 212.929803] R13: ffff88884fd5f950 R14: ffffc900039c5000 R15: ffff88835e927680\u000a[ 212.929999] FS: 00007fe7c50b6480(0000) GS:ffff88886f980000(0000) knlGS:0000000000000000\u000a[ 212.930235] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\u000a[ 212.930394] CR2: 0000000000000010 CR3: 000000085bd04002 CR4: 00000000001606e0\u000a[ 212.930588] Call Trace:\u000a[ 212.930682] ? tc_del_tfilter+0xa40/0xa40\u000a[ 212.930811] ? __lock_acquire+0x5b5/0x2460\u000a[ 212.930948] ? find_held_lock+0x85/0xa0\u000a[ 212.931081] ? tc_del_tfilter+0xa40/0xa40\u000a[ 212.931201] rtnetlink_rcv_msg+0x4ab/0x5f0\u000a[ 212.931332] ? rtnl_dellink+0x490/0x490\u000a[ 212.931454] ? lockdep_hardirqs_on+0x260/0x260\u000a[ 212.931589] ? netlink_deliver_tap+0xab/0x5a0\u000a[ 212.931717] ? match_held_lock+0x1b/0x240\u000a[ 212.931844] netlink_rcv_skb+0xd0/0x200\u000a[ 212.931958] ? rtnl_dellink+0x490/0x490\u000a[ 212.932079] ? netlink_ack+0x440/0x440\u000a[ 212.932205] ? netlink_deliver_tap+0x161/0x5a0\u000a[ 212.932335] ? lock_downgrade+0x360/0x360\u000a[ 212.932457] ? lock_acquire+0xe5/0x210\u000a[ 212.932579] netlink_unicast+0x296/0x350\u000a[ 212.932705] ? netlink_attachskb+0x390/0x390\u000a[ 212.932834] ? _copy_from_iter_full+0xe0/0x3a0\u000a[ 212.932976] netlink_sendmsg+0x394/0x600\u000a[ 212.937998] ? netlink_unicast+0x350/0x350\u000a[ 212.943033] ? move_addr_to_kernel.part.0+0x90/0x90\u000a[ 212.948115] ? netlink_unicast+0x350/0x350\u000a[ 212.953185] sock_sendmsg+0x96/0xa0\u000a[ 212.958099] ___sys_sendmsg+0x482/0x520\u000a[ 212.962881] ? match_held_lock+0x1b/0x240\u000a[ 212.967618] ? copy_msghdr_from_user+0x250/0x250\u000a[ 212.972337] ? lock_downgrade+0x360/0x360\u000a[ 212.976973] ? rwlock_bug.part.0+0x60/0x60\u000a[ 212.981548] ? __mod_node_page_state+0x1f/0xa0\u000a[ 212.986060] ? match_held_lock+0x1b/0x240\u000a[ 212.990567] ? find_held_lock+0x85/0xa0\u000a[ 212.994989] ? do_user_addr_fault+0x349/0x5b0\u000a[ 212.999387] ? lock_downgrade+0x360/0x360\u000a[ 213.003713] ? find_held_lock+0x85/0xa0\u000a[ 213.007972] ? __fget_light+0xa1/0xf0\u000a[ 213.012143] ? sockfd_lookup_light+0x91/0xb0\u000a[ 213.016165] __sys_sendmsg+0xba/0x130\u000a[ 213.020040] ? __sys_sendmsg_sock+0xb0/0xb0\u000a[ 213.023870] ? handle_mm_fault+0x337/0x470\u000a[ 213.027592] ? page_fault+0x8/0x30\u000a[ 213.031316] ? lockdep_hardirqs_off+0xbe/0x100\u000a[ 213.034999] ? mark_held_locks+0x24/0x90\u000a[ 213.038671] ? do_syscall_64+0x1e/0xe0\u000a[ 213.042297] do_syscall_64+0x74/0xe0\u000a[ 213.045828] entry_SYSCALL_64_after_hwframe+0x49/0xbe\u000a[ 213.049354] RIP: 0033:0x7fe7c527c7b8\u000a[ 213.052792] Code: 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 8d 05 65 8f 0c 00 8b 00 85 c0 75 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f\u000a0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 89 54\u000a[ 213.060269] RSP: 002b:00007ffc3f7908a8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\u000a[ 213.064144] RAX: ffffffffffffffda RBX: 000000005d34716f RCX: 00007fe7c527c7b8\u000a[ 213.068094] RDX: 0000000000000000 RSI: 00007ffc3f790910 RDI: 0000000000000003\u000a[ 213.072109] RBP: 0000000000000000 R08: 0000000000000001 R09: 00007fe7c5340cc0\u000a[ 213.076113] R10: 0000000000404ec2 R11: 0000000000000246 R12: 0000000000000080\u000a[ 213.080146] R13: 0000000000480640 R14: 0000000000000080 R15: 0000000000000000\u000a[ 213.084147] Modules linked in: act_gact cls_flower sch_ingress nfsv3 nfs_acl nfs lockd grace fscache bridge stp llc sunrpc intel_rapl_msr intel_rapl_common\u000a\u001b[<1;69;32Msb_edac rdma_ucm rdma_cm x86_pkg_temp_thermal iw_cm intel_powerclamp ib_cm coretemp kvm_intel kvm irqbypass mlx5_ib ib_uverbs ib_core crct10dif_pclmul crc32_pc\u000almul crc32c_intel ghash_clmulni_intel mlx5_core intel_cstate intel_uncore iTCO_wdt igb iTCO_vendor_support mlxfw mei_me ptp ses intel_rapl_perf mei pcspkr ipmi\u000a_ssif i2c_i801 joydev enclosure pps_core lpc_ich ioatdma wmi dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad ast i2c_algo_bit drm_vram_helpe\u000ar ttm drm_kms_helper drm mpt3sas raid_class scsi_transport_sas\u000a[ 213.112326] CR2: 0000000000000010\u000a[ 213.117429] ---[ end trace adb58eb0a4ee6283 ]---\u000a\u000aVerify that q pointer is not NULL before setting the 'flags' field.\u000a\u000aFixes: 3f05e6886a59 (\"net_sched: unset TCQ_F_CAN_BYPASS when adding filters\")\u000aSigned-off-by: Vlad Buslov \u000aAcked-by: Jiri Pirko \u000aSigned-off-by: David S. Miller \u000aCc: Sasha Levin \u000aSigned-off-by: Greg Kroah-Hartman \u000a\u000a", "date" : "2019-07-28 08:28:38 +0200", "id" : "51d036eb719b258bd5bc2be3a243a22c7368abad", "msg" : "net: sched: verify that q!=NULL before setting q->flags", "paths" : [ { "editType" : "edit", "file" : "net/sched/cls_api.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "Makefile" ], "commitId" : "4a9b1eb8bc3ba4ad8b3b1aa3317cf8d4a3aaad83", "timestamp" : 1564295319000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, "authorEmail" : "gregkh@linuxfoundation.org", "comment" : "Linux 5.1.21\u000a", "date" : "2019-07-28 08:28:39 +0200", "id" : "4a9b1eb8bc3ba4ad8b3b1aa3317cf8d4a3aaad83", "msg" : "Linux 5.1.21", "paths" : [ { "editType" : "edit", "file" : "Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Kconfig", "drivers/gpu/pvr/tools/hostfunc.h", "drivers/gpu/pvr/device.h", "drivers/gpu/pvr/bufferclass_example_linux.c", "drivers/gpu/pvr/bufferclass_example_linux.h", "drivers/gpu/pvr/deviceclass.c", "drivers/gpu/pvr/COPYING", "drivers/gpu/pvr/pvrconfig.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/mm.c", "drivers/gpu/pvr/ioctldef.h", "drivers/gpu/pvr/queue.c", "drivers/gpu/pvr/sysutils.c", "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/bufferclass_example.c", "drivers/gpu/pvr/sgxfeaturedefs.h", "drivers/gpu/pvr/osfunc.c", "drivers/gpu/pvr/kernelbuffer.h", "drivers/gpu/pvr/devicemem.c", "drivers/gpu/pvr/mm.h", "drivers/gpu/pvr/osfunc.h", "drivers/gpu/pvr/pvrversion.h", "drivers/gpu/pvr/pdump_km.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/tools/Makefile", "drivers/gpu/pvr/bufferclass_example.h", "drivers/gpu/pvr/sgx_options.h", "drivers/gpu/pvr/tools/hostfunc.c", "drivers/gpu/pvr/pvrmmap.h", "drivers/gpu/pvr/ocpdefs.h", "drivers/gpu/pvr/proc.c", "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/sgx_bridge.h", "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/private_data.h", "drivers/gpu/pvr/sgxpower.c", "drivers/gpu/pvr/services_headers.h", "drivers/gpu/pvr/queue.h", "drivers/gpu/pvr/pvr_bridge.h", "drivers/gpu/pvr/sgxtransfer.c", "drivers/gpu/pvr/dbgdrvif.h", "drivers/gpu/pvr/bufferclass_example_private.h", "drivers/gpu/pvr/ra.c", "drivers/gpu/pvr/sgxinfo.h", "drivers/gpu/pvr/bufferclass_example_private.c", "drivers/gpu/pvr/sgxutils.h", "drivers/gpu/pvr/omaplfb_linux.c", "drivers/gpu/pvr/oemfuncs.h", "drivers/gpu/pvr/README", "drivers/gpu/pvr/hash.h", "drivers/gpu/pvr/hash.c", "drivers/gpu/pvr/handle.h", "drivers/gpu/pvr/sgxmmu.h", "drivers/gpu/pvr/handle.c", "drivers/gpu/pvr/pb.c", "drivers/gpu/pvr/ra.h", "drivers/gpu/pvr/sgxapi_km.h", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/mutex.h", "drivers/gpu/pvr/srvkm.h", "drivers/gpu/pvr/pvrsrv.c", "drivers/gpu/pvr/event.c", "drivers/gpu/pvr/sgxdefs.h", "drivers/gpu/pvr/pdump_common.c", "drivers/gpu/pvr/env_data.h", "drivers/gpu/pvr/env_perproc.h", "drivers/video/Kconfig", "drivers/gpu/pvr/event.h", "drivers/gpu/pvr/sgxscript.h", "drivers/gpu/pvr/sgxconfig.h", "drivers/gpu/pvr/sgxerrata.h", "drivers/gpu/pvr/tools/dbgdriv.h", "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/sgxkick.c", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/servicesint.h", "drivers/gpu/pvr/sgxreset.c", "drivers/gpu/pvr/sgx530defs.h", "drivers/gpu/pvr/img_defs.h", "drivers/gpu/pvr/syscommon.h", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/bridged_support.c", "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/bridged_support.h", "drivers/gpu/pvr/omaplfb.h", "drivers/gpu/pvr/mutils.h", "drivers/gpu/pvr/buffer_manager.h", "drivers/gpu/pvr/tools/dbgdriv.c", "include/video/sgx-util.h", "drivers/gpu/pvr/tools/linuxsrv.h", "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/osperproc.h", "drivers/gpu/pvr/osperproc.c", "drivers/gpu/pvr/sgxcoretypes.h", "drivers/gpu/pvr/omaplfb_displayclass.c", "drivers/gpu/pvr/mmap.h", "drivers/gpu/pvr/pvr_debug.c", "drivers/gpu/pvr/kerneldisplay.h", "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/perproc.h", "drivers/gpu/pvr/power.h", "drivers/gpu/pvr/mmu.h", "drivers/gpu/pvr/mem.c", "drivers/gpu/pvr/tools/ioctl.c", "drivers/gpu/pvr/tools/main.c", "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/services.h", "drivers/gpu/pvr/tools/hotkey.c", "drivers/gpu/pvr/pvrmodule.h", "drivers/gpu/pvr/sysinfo.h", "drivers/gpu/pvr/tools/ioctl.h", "drivers/gpu/pvr/bridged_sgx_bridge.c", "drivers/gpu/pvr/servicesext.h", "drivers/gpu/pvr/bridged_sgx_bridge.h", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/tools/hotkey.h", "drivers/gpu/pvr/sysconfig.c", "drivers/gpu/pvr/pdumpdefs.h", "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/sysconfig.h", "drivers/gpu/pvr/syslocal.h", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/bridged_pvr_bridge.h", "drivers/gpu/Makefile", "drivers/gpu/pvr/resman.h", "drivers/gpu/pvr/img_types.h", "drivers/gpu/pvr/perproc.c", "drivers/gpu/pvr/resman.c", "drivers/gpu/pvr/lock.h" ], "commitId" : "92cd90b027b355d18cc7421a9927693af190d44e", "timestamp" : 1579843575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Add PVR GPU driver\u000a\u000aPatch-Mainline: not sure\u000aAdd the SGX PVR driver.\u000a\u000aSigned-off-by: Imre Deak \u000aSigned-off-by: Felipe Balbi \u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Ville Syrjälä \u000aSigned-off-by: Mark Underwood \u000aSigned-off-by: Phil Carmody \u000aSigned-off-by: Tomi Valkeinen \u000aSigned-off-by: Sami Kyöstilä \u000aSigned-off-by: Mark Riding \u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Roger Quadros \u000a", "date" : "2020-01-24 08:26:15 +0300", "id" : "92cd90b027b355d18cc7421a9927693af190d44e", "msg" : "gpu: pvr: Add PVR GPU driver", "paths" : [ { "editType" : "add", "file" : "drivers/gpu/pvr/COPYING" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sysinfo.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/perproc.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mutils.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/Kconfig" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mutex.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgx_bridge.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgx530defs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxcoretypes.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/dbgdriv.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/env_perproc.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/img_defs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/devicemem.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bufferclass_example_linux.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sysconfig.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/syslocal.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/omaplfb_displayclass.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pdump_common.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/resman.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxconfig.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/syscommon.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/handle.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxpower.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/lock.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bufferclass_example.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_bridge.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxerrata.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/device.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/queue.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/osfunc.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/buffer_manager.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/queue.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/kernelbuffer.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvrconfig.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/img_types.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/handle.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/Makefile" }, { "editType" : "add", "file" : "drivers/gpu/pvr/omaplfb_linux.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/osperproc.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/ra.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/hostfunc.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/servicesext.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/ra.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/README" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mmu.h" }, { "editType" : "add", "file" : "include/video/sgx-util.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxapi_km.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/kerneldisplay.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/oemfuncs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxdefs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/proc.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/linuxsrv.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/servicesint.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/dbgdriv.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bufferclass_example_private.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxmmu.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mmap.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/Makefile" }, { "editType" : "add", "file" : "drivers/gpu/pvr/srvkm.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/hotkey.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bufferclass_example.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/event.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/power.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/ioctl.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/dbgdrvif.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgx_options.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxreset.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/env_data.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mmap.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pdumpdefs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxkick.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/hash.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/services_headers.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mem.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvrmmap.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/proc.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/omaplfb.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/deviceclass.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxfeaturedefs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bridged_support.c" }, { "editType" : "edit", "file" : "drivers/video/Kconfig" }, { "editType" : "add", "file" : "drivers/gpu/pvr/buffer_manager.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/main.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bufferclass_example_private.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mm.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvrmodule.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/hostfunc.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxutils.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mm.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/perproc.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvrversion.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxscript.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sysconfig.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/services.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/hotkey.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/resman.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/private_data.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bufferclass_example_linux.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/ioctldef.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/tools/ioctl.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pb.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/osperproc.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxtransfer.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/hash.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/bridged_support.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/ocpdefs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/event.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/sgxinfo.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/resman.c", "drivers/gpu/pvr/mm.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "1123da23da28a5443a642ccf329709c5c7c95cd0", "timestamp" : 1579843575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: compilation fixes for kernel > 2.6.33\u000a\u000aSigned-off-by: Ameya Palande \u000a", "date" : "2020-01-24 08:26:15 +0300", "id" : "1123da23da28a5443a642ccf329709c5c7c95cd0", "msg" : "gpu: pvr: compilation fixes for kernel > 2.6.33", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c" ], "commitId" : "58ce399cc09bf48f61621f57df1a868340fc358d", "timestamp" : 1579843575000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: move device registration into board file\u000a\u000aNeeded by an upcoming patch adding board specific device parameters.\u000a\u000aSigned-off-by: Imre Deak \u000aSigned-off-by: Tomi Valkeinen \u000a\u000aAdapt for Nokia N900 MeeGo kernel\u000a\u000aSigned-off-by: Carsten Munk \u000a", "date" : "2020-01-24 08:26:15 +0300", "id" : "58ce399cc09bf48f61621f57df1a868340fc358d", "msg" : "gpu: pvr: move device registration into board file", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.c", "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/sysutils.c", "drivers/gpu/pvr/syscommon.h", "drivers/gpu/pvr/syslocal.h", "include/linux/pvr.h" ], "commitId" : "daf1afdbd906d344df3d3b8f2fa5324c060bee0b", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add support to set board specific max SGX functional clk rate\u000a\u000aSigned-off-by: Imre Deak \u000aSigned-off-by: Tomi Valkeinen \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "daf1afdbd906d344df3d3b8f2fa5324c060bee0b", "msg" : "gpu: pvr: add support to set board specific max SGX functional clk rate", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/syscommon.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "add", "file" : "include/linux/pvr.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/syslocal.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/event.c", "drivers/gpu/pvr/osfunc.c", "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/mm.c", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/mutex.h", "drivers/gpu/pvr/lock.h", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "203597b3b89a965f0780fae88a69243f0fdef277", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add pvr_lock/remove unneeded lock headers\u000a\u000a- Add a public interface for accessing this lock. It has been used\u000a as a public interface anyway and an upcoming patch needs to access\u000a it as well.\u000a\u000a- Remove headers becoming unnecessary by this refactoring.\u000a\u000aNote:\u000a Currently this lock provides for a course level locking protecting\u000a all HW and SW state tracking objects. We'll need to revise the use\u000a of the following additional locks in the driver. Their existance\u000a might not be justified, in which case we could just substitute\u000a them with pvr_lock:\u000a\u000a PVRSRVDvfsLock\u000a PVRSRVPowerLock\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "203597b3b89a965f0780fae88a69243f0fdef277", "msg" : "gpu: pvr: add pvr_lock/remove unneeded lock headers", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/mutex.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/lock.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/event.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "fb565094635c9d9dd041f2eb468c77c51ff46806", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: bail out from SGXOSTimer if it's been canceled\u000a\u000aAt the moment cancelling the timer is done in a synchronous way, so\u000awe don't need to have the extra check. But a later patch will add\u000aadditional locking around the HW interrupt from where the timer can\u000abe cancelled as well. Because of lock dependency issues described\u000ain that patch we have to switch to an asynchronous way of cancelling\u000athis timer and it means we need to have the extra check.\u000a\u000aAlso reset the flag indicating that the timer is cancelled when\u000adestroying it. Currently we are both cancelling and destroying the\u000atimer, but we really should just require calling the destroy function.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "fb565094635c9d9dd041f2eb468c77c51ff46806", "msg" : "gpu: pvr: bail out from SGXOSTimer if it's been canceled", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "b7f0b47d6ae3c817cdb657a28b236e4a28bae1c9", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix locking on the HW interrupt path\u000a\u000a- take pvr_lock in the interrupt handling work (MISR) thread, as from\u000a there we can call functions accessing HW and SW state tracking objects.\u000a An example is the SGX HW recovery function.\u000a\u000a- make SGXOSTimerCancel asynchronous. This is safe now as a previous\u000a patch made sure that the timer will not run after cancelled. We can't\u000a do synchronous cancellation, because there would be an ABBA lockdep\u000a problem involving the SGXOSTimer's mutex and pvr_lock:\u000a\u000a MISR / IOCTL thread:\u000a 1. pvr_lock in PVRSRV_BridgeDispatchKM\u000a 2. timer's lock through SGXPrePowerState -> SGXOSTimerCancel\u000a\u000a SGXOSTimer's thread:\u000a 1. timer's lock already taken when SGXOSTimer is called\u000a 2. pvr_lock in SGXOSTimer\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "b7f0b47d6ae3c817cdb657a28b236e4a28bae1c9", "msg" : "gpu: pvr: fix locking on the HW interrupt path", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "54068b8b1f3bab631570ffb91b0735b081a6988a", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: acquire the pvr lock on the SGX HW recovery path\u000a\u000aWe need to take the lock protecting all SW and HW state tracking\u000aobjects on the recovery reset path, since we are accessing objects\u000alike the SGX command queue, or the per process memory and resource\u000amanagement contexts.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "54068b8b1f3bab631570ffb91b0735b081a6988a", "msg" : "gpu: pvr: acquire the pvr lock on the SGX HW recovery path", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "67bd78ffc49b77b2b01ed953267d761e41674503", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix locking in pvr_dbg_reset\u000a\u000aHWRecoverResetSGX needs to be called with the pvr_lock held.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "67bd78ffc49b77b2b01ed953267d761e41674503", "msg" : "gpu: pvr: fix locking in pvr_dbg_reset", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "2e0e5066974f74ba1f90d53f5201b1169072773a", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: BUG if pvr_lock is not held in HWRecoveryResetSGX\u000a\u000aAdding the check only to this one place, more can be added later.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "2e0e5066974f74ba1f90d53f5201b1169072773a", "msg" : "gpu: pvr: BUG if pvr_lock is not held in HWRecoveryResetSGX", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/omaplfb_displayclass.c" ], "commitId" : "be26ad37cc12ebeaf5d7560235d32211e7bb6f54", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix indent error\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "be26ad37cc12ebeaf5d7560235d32211e7bb6f54", "msg" : "gpu: pvr: fix indent error", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/omaplfb_displayclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/queue.c", "drivers/gpu/pvr/syscommon.h" ], "commitId" : "8106d5f07b8b0f7df0b6710a564524dcd600eff8", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused per device variable\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "8106d5f07b8b0f7df0b6710a564524dcd600eff8", "msg" : "gpu: pvr: remove unused per device variable", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/queue.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/syscommon.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "322d81257d8c1e146a66de66e5c983d94706e841", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: make sure the device is powered on in SGX_MISRHandler\u000a\u000aWhile SGX_MISRHandler is scheduled another code path of the driver\u000a(IOCTL, SGXOSTimer) can race with it and turn the power off before\u000ait starts to execute.\u000a\u000aWhen this happens we get the following oops backtrace:\u000a\u000a HWRecoveryResetSGX: SGX Hardware Recovery triggered\u000a Unhandled fault: external abort on non-linefetch (0x1008)\u000a PC is at HWRecoveryResetSGX+0x74/0x1b8 [pvrsrvkm]\u000a LR is at preempt_schedule+0x44/0x54\u000a (HWRecoveryResetSGX+0x0/0x1b8) from (SGX_MISRHandler+0x5c/0x60)\u000a (SGX_MISRHandler+0x0/0x60) from (PVRSRVMISR+0x44/0xa0)\u000a r5:bf0a29cc r4:dfbbbcc0\u000a (PVRSRVMISR+0x0/0xa0) from (MISRWrapper+0x14/0x18)\u000a r5:00000002 r4:00000000\u000a (MISRWrapper+0x0/0x18) from (worker_thread+0x1d0/0x2cc)\u000a (worker_thread+0x0/0x2cc) from (kthread+0x88/0x90)\u000a (kthread+0x0/0x90) from (do_exit+0x0/0x680)\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "322d81257d8c1e146a66de66e5c983d94706e841", "msg" : "gpu: pvr: make sure the device is powered on in SGX_MISRHandler", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.h", "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/buffer_manager.h", "drivers/gpu/pvr/mmu.c" ], "commitId" : "b2b56de7ad6c7a41230b75625ac00fba1602ca13", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add support for finding the BM context from the DL\u000a\u000aThis allows us to find the BM context from the value of the directory list.\u000aThis is required for the next patch.\u000a\u000aSigned-off-by: Mark Underwood \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "b2b56de7ad6c7a41230b75625ac00fba1602ca13", "msg" : "gpu: pvr: add support for finding the BM context from the DL", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/resman.c" ], "commitId" : "7191ae9cd3b1d8500b719a218500fb987f9cce85", "timestamp" : 1579843576000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: clean up FreeResourceByCriteria\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:16 +0300", "id" : "7191ae9cd3b1d8500b719a218500fb987f9cce85", "msg" : "gpu: pvr: clean up FreeResourceByCriteria", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/resman.h", "drivers/gpu/pvr/resman.c" ], "commitId" : "bc7b57aaefc31ec7f804d1961a2853aacfd7915f", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add helpers to look up resource context and proc info\u000a\u000aThese are needed by an upcoming patch showing process info.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "bc7b57aaefc31ec7f804d1961a2853aacfd7915f", "msg" : "gpu: pvr: add helpers to look up resource context and proc info", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "244dc231483b71f4a496dfef1293ff556c631d6b", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: dump process info at HW recovery reset\u000a\u000aPrint process ID and command name during HW recovery reset.\u000a\u000aBased on a patch from Mark Underwood .\u000a\u000aForward port to 2.6.35\u000a\u000aSigned-off-by: Imre Deak \u000aSigned-off-by: Carsten Munk \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "244dc231483b71f4a496dfef1293ff556c631d6b", "msg" : "gpu: pvr: dump process info at HW recovery reset", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Kconfig", "drivers/gpu/pvr/event.c", "drivers/gpu/pvr/sysutils.c", "drivers/gpu/pvr/ra.c", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/syslocal.h", "drivers/gpu/pvr/proc.c", "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/osfunc.c", "drivers/gpu/pvr/bufferclass_example_linux.c", "drivers/gpu/pvr/omaplfb.h", "drivers/gpu/pvr/mm.h", "drivers/gpu/pvr/bridged_pvr_bridge.h", "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/pvrconfig.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/handle.c", "drivers/gpu/pvr/pb.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/sgx_options.h", "drivers/gpu/pvr/resman.c" ], "commitId" : "3952af7a27b317f7ee9c23a442181ac4e69993af", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add option for extra debugging information\u000a\u000aThis is basically a sed -i 's/\\/CONFIG_PVR_DEBUG_EXTRA' *.[ch] .\u000a\u000aCurrently a driver built in debug mode will only work together with the\u000arelevant PVR/OGLES user space libraries being built in debug mode too.\u000aThis is becuase the ABI is different in debug and release build.\u000a\u000aThis is not very flexible when one wants to only debug the kernel driver\u000aand not care about the user space part, let alone figuring out where to\u000aget the sources for that and rebuild it in debug mode too.\u000a\u000aMark the current user space dependent debug code parts with a new\u000aCONFIG_PVR_DEBUG_EXTRA option instead of DEBUG, so that later we can\u000aselectively add back basic debugging facilities like debug traces and\u000amark them with CONFIG_PVR_DEBUG.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "3952af7a27b317f7ee9c23a442181ac4e69993af", "msg" : "gpu: pvr: add option for extra debugging information", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/syslocal.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/ra.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/handle.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pb.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/event.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/omaplfb.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_options.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrconfig.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bufferclass_example_linux.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/handle.c", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/resman.c" ], "commitId" : "9066b719e7678d0ba4dfbc121025d49337d9b452", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: enable debug trace for basic debug build\u000a\u000aEnable debug messages for basic debug type builds.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "9066b719e7678d0ba4dfbc121025d49337d9b452", "msg" : "gpu: pvr: enable debug trace for basic debug build", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/handle.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "21c608b3e0929c588499fb687b95e59d9237763e", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix locking on SGX load calculating thread\u000a\u000apsDeviceNodeList et al is protected by pvr_lock, so we need to\u000aacquire it here.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "21c608b3e0929c588499fb687b95e59d9237763e", "msg" : "gpu: pvr: fix locking on SGX load calculating thread", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/power.h", "drivers/gpu/pvr/sysutils.c" ], "commitId" : "d6289ab9d0871e3f2c2dc5c60a91376d035b65b1", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix locking on the DVFS path\u000a\u000aThe HW state is protected by pvr_lock(), so acquire it for the\u000aduration of clock rate changes. We can also remove PVRSRVDvfsLock()\u000athat thus becomes unneded.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "d6289ab9d0871e3f2c2dc5c60a91376d035b65b1", "msg" : "gpu: pvr: fix locking on the DVFS path", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/power.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/power.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "1a84cb3451aff02e2019507e0e320ca8fe62c343", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove PVRSRVPowerLock()\u000a\u000aFor the relevant paths we already hold pvr_lock(), so we this lock\u000ais unnecessary.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "1a84cb3451aff02e2019507e0e320ca8fe62c343", "msg" : "gpu: pvr: remove PVRSRVPowerLock()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/power.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/syscommon.h", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "5dfa0c05f4cf36377df0bd9aeb32e919d3c8aeba", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove sPowerStateChangeResource lock\u000a\u000aThis lock was only created / destroyed, but nowhere actually used.\u000aRemove it.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "5dfa0c05f4cf36377df0bd9aeb32e919d3c8aeba", "msg" : "gpu: pvr: remove sPowerStateChangeResource lock", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/syscommon.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/queue.c", "drivers/gpu/pvr/syscommon.h", "drivers/gpu/pvr/osfunc.h", "drivers/gpu/pvr/osfunc.c" ], "commitId" : "df1d86752baa30d51a1f5d15d105f82707f6c953", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove sQProcessResource/OSLockResource interface\u000a\u000aThe relevent parts are already protected by pvr_lock(), so no\u000aneed for sQProcessResource, which was anyway racy and required\u000athe occasional retrying of any operations performed on the\u000aprotected object.\u000a\u000aThe OSLockResource interface thus becomes unused, so remove it\u000atoo.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "df1d86752baa30d51a1f5d15d105f82707f6c953", "msg" : "gpu: pvr: remove sQProcessResource/OSLockResource interface", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/queue.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/syscommon.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/power.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/pvrsrv.c", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "45b30aaf222894e112d36ee059b32cd1f4bda4c3", "timestamp" : 1579843577000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused function args from PVRSRVSetDevicePowerStateKM\u000a\u000aThe CallerID parameter was anyway a horrible concept in terms of\u000aunderstanding what the function is supposed to do when ISR_ID, KERNEL_ID\u000aor TIMER_ID is passed. Function arguments should never have such \"high\u000alevel\" meaning, but rather denote much more concrete things. In this case\u000afor example whether we should mutex_lock() or mutex_trylock() for a\u000acertain lock. Better yet we should have separate functions for the two\u000acases to keep the function body as simple as possible.\u000a\u000aHappily the CallerID and RetainMutex arguments are unused now, so they\u000acan be removed.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:17 +0300", "id" : "45b30aaf222894e112d36ee059b32cd1f4bda4c3", "msg" : "gpu: pvr: remove unused function args from PVRSRVSetDevicePowerStateKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/power.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/queue.c", "drivers/gpu/pvr/queue.h", "drivers/gpu/pvr/deviceclass.c", "drivers/gpu/pvr/pvrsrv.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "9e78855bb028848f9d5f2155a0785e2d3664f805", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused function args from PVRSRVProcessQueues\u000a\u000aSee the earlier commit with a similar change on why this is justified.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "9e78855bb028848f9d5f2155a0785e2d3664f805", "msg" : "gpu: pvr: remove unused function args from PVRSRVProcessQueues", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/queue.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/queue.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "e173e5401862fca0c33bd8d96f849b0ff4f6742c", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: no need to check for retry failures in PVRSRVMISR\u000a\u000aProcessQueues can't fail any more with a 'retry' error, so checking for\u000athis is not needed. Previously ProcessQueues could fail if sQProcessResource\u000ais locked by someone else. Since sQProcessResource is removed by a previous\u000achange in this patchset that race condition can't happen.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "e173e5401862fca0c33bd8d96f849b0ff4f6742c", "msg" : "gpu: pvr: no need to check for retry failures in PVRSRVMISR", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/pvr_debug.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "7c838694a3fc4ba416fe89f0efb72acf0c1561f0", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused function args from HWRecoveryResetSGX\u000a\u000aSee the similar commits earlier in the patchset on why this is\u000ajustified.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "7c838694a3fc4ba416fe89f0efb72acf0c1561f0", "msg" : "gpu: pvr: remove unused function args from HWRecoveryResetSGX", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "f144df5b3ba8f7ccaa315c8b0671e529ac067146", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: no need to check for retry failures in SGXScheduleCCBCommandKM\u000a\u000aPowering on the device can't fail any more with a 'retry' error so we can't\u000ahave the corresponding condition here. See the similar commit earlier in the\u000apatchset for a more detailed explanation.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "f144df5b3ba8f7ccaa315c8b0671e529ac067146", "msg" : "gpu: pvr: no need to check for retry failures in SGXScheduleCCBCommandKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/osfunc.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "ffd2af9e2c64f8c465948b3bda5479e577d4c3b6", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: no need to check for IRQ context in SGXCommandComplete\u000a\u000aThis function isn't called in IRQ context from anywhere, so remove\u000athe related checks.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "ffd2af9e2c64f8c465948b3bda5479e577d4c3b6", "msg" : "gpu: pvr: no need to check for IRQ context in SGXCommandComplete", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "90299f31f18f1b6195958f8473a18b19decec8bf", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: no need to check for retry failures in SGXTestActivePowerEvent\u000a\u000aPowering off can't fail now with a 'retry' error, so we can't have the\u000acorresponding condition here. See the similar commits earlier in the\u000apatchset for a more detailed explanation.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "90299f31f18f1b6195958f8473a18b19decec8bf", "msg" : "gpu: pvr: no need to check for retry failures in SGXTestActivePowerEvent", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "696ad6349a9efda0258ee819a384647b9acdc1f5", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: no need to delay queue processing in SGXPostActivePowerEvent\u000a\u000aAt the moment processing of the command queue is delayed in case\u000aSGXPostActivePowerEvent in the HW interrupt code path. This would be\u000aonly justified in case of being in interrupt context. This might have\u000abeen the case at one point in the history, but now HW interrupts\u000aresult in a work scheduled and thus calling the queue processing\u000afunction is safe in all cases.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "696ad6349a9efda0258ee819a384647b9acdc1f5", "msg" : "gpu: pvr: no need to delay queue processing in SGXPostActivePowerEvent", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "b2575adffe481fc64d5b36c0bc6799a5166f1986", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused function args from SGXPostActivePowerEvent\u000a\u000aSee the similar commits earlier on why this is justified.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "b2575adffe481fc64d5b36c0bc6799a5166f1986", "msg" : "gpu: pvr: remove unused function args from SGXPostActivePowerEvent", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/sgxutils.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "a338e0f7b54a7df154a07d8222dc2cac75b10522", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused function args from SGXTestActivePowerEvent\u000a\u000aSee the similar commits earlier in the patchset to see why this is\u000ajustified.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "a338e0f7b54a7df154a07d8222dc2cac75b10522", "msg" : "gpu: pvr: remove unused function args from SGXTestActivePowerEvent", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debug.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "cb4e239634ef854424c72d5ca1948b8e6e37f487", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unrelevant comments about caller ID\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "cb4e239634ef854424c72d5ca1948b8e6e37f487", "msg" : "gpu: pvr: remove unrelevant comments about caller ID", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvrconfig.h" ], "commitId" : "34b95b1f0438b8fcd855843b370fec16dd916c1c", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix PDUMP configuartion in release build\u000a\u000aPDUMP can be enabled in release builds too, but so far it was only enabled\u000ain debug builds, so fix this.\u000a\u000aSigned-off-by: Imre Deak \u000aCC: Mark Underwood \u000aCC: Mark Riding \u000aReviewed-by: Topi Pohjolainen \u000aReviewed-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "34b95b1f0438b8fcd855843b370fec16dd916c1c", "msg" : "gpu: pvr: fix PDUMP configuartion in release build", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrconfig.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mm.h", "drivers/gpu/pvr/osfunc.c" ], "commitId" : "d2555e328923dace7b86d92b246ca6b69b8a1998", "timestamp" : 1579843578000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove support for broken LINUX_MEM_AREAS_DEBUG\u000a\u000aSince implementation of the relevant function is missing, enabling\u000athis will lead to a build problem. Hence removing it.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:18 +0300", "id" : "d2555e328923dace7b86d92b246ca6b69b8a1998", "msg" : "gpu: pvr: remove support for broken LINUX_MEM_AREAS_DEBUG", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "ac287aa6f12316d619663882329f8f0f19a7fa4e", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: round the SGX fclock rate to the nearest supported\u000a\u000aThis is needed since clk_set_rate accepts only exact values.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "ac287aa6f12316d619663882329f8f0f19a7fa4e", "msg" : "gpu: pvr: round the SGX fclock rate to the nearest supported", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgx_bridge.h", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "585aa5570183d77b9fd98e5557380743b6a48309", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: replace boolean by flags in blits complete query\u000a\u000aIn preparation for adding third mode of query. In DRM one\u000ahas a specific IOCTL for requesting the DRM kernel driver to\u000aissue events when a particular vertical blanking period\u000apasses. Here one aims to introduce similar IOCTL for requesting\u000aPVR kernel driver to issue events whenever a particular frame\u000agets rendered in full. And instead of introducing entirely new\u000aIOCTL, one instead aims to extend an existing call with a new\u000amode. This is accomplished by replacing the boolean selector\u000awith an integer.\u000a\u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "585aa5570183d77b9fd98e5557380743b6a48309", "msg" : "gpu: pvr: replace boolean by flags in blits complete query", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/private_data.h", "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "d48551c29d97d459ba2c015c9708fa2d72dce51a", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: support for events\u000a\u000aIn DRM vertical blank event style, introduce support for the\u000adriver to issue and for the userspace to read events. Driver\u000afile node is extended with a list holding unread events and\u000awith a wait queue representing processes interested receiving\u000aevents.\u000a\u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "d48551c29d97d459ba2c015c9708fa2d72dce51a", "msg" : "gpu: pvr: support for events", "paths" : [ { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_events.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/private_data.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "c989104deaa76e589dfa524b54d6533930012dcd", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: support for polling events\u000a\u000aIn DRM style provide means for userspace to monitor availability\u000aof events via the poll syscall.\u000a\u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "c989104deaa76e589dfa524b54d6533930012dcd", "msg" : "gpu: pvr: support for polling events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "17f5a8e63732860a0cf5234a7d4d08a4df1b6349", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: support for render complete events\u000a\u000aIn DRM vertical blank event style, add support for userspace\u000ato register for events signaling completion of rendering.\u000aDriver is augmented with a list of pending events each\u000arepresenting request to monitor a particular render completion.\u000aInterrupt handler checks for the list and for the corresponding\u000astate of the target surface. Once a complete render is\u000aencountered, the handler simply moves the corresponding event\u000afrom the pending list to the unread list.\u000a\u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "17f5a8e63732860a0cf5234a7d4d08a4df1b6349", "msg" : "gpu: pvr: support for render complete events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c", "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/bridged_sgx_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.h", "drivers/gpu/pvr/sgx_bridge.h", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "c318b43e84fa703dc7fa8e9a004c201c70dd66c0", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: enable render complete events\u000a\u000aIn DRM style events are associated with the driver private\u000apart of the driver file descriptor. In order for the poll\u000aand read methods to access the event list one needs to pass\u000athe file private through the IOCTL stack.\u000a\u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "c318b43e84fa703dc7fa8e9a004c201c70dd66c0", "msg" : "gpu: pvr: enable render complete events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/sgx_bridge.h", "drivers/gpu/pvr/pvr_events.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "dabc04222e47f87cdf1b1e764bf8d1d9fc5e30ef", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: support for user data in events\u000a\u000aSigned-off-by: Topi Pohjolainen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "dabc04222e47f87cdf1b1e764bf8d1d9fc5e30ef", "msg" : "gpu: pvr: support for user data in events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "a2f7ea350ae667c7d21fb7446b3b576e9191e50d", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: more accurate error reporting when clk_set_rate fails\u000a\u000aWe reported a rounded-down MHz value when clk_set_rate failed,\u000abut this didn't make the reason clear when the Hz value didn't\u000amatch exactly any supported rate. So report Hz values instead.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "a2f7ea350ae667c7d21fb7446b3b576e9191e50d", "msg" : "gpu: pvr: more accurate error reporting when clk_set_rate fails", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/sysutils.c" ], "commitId" : "f752e6bcaab5b7f2913ac5ca19eddf6191374878", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix lockdep problem\u000a\u000aOn the CLK_PRE_RATE_CHANGE:\u000a1. lock A <- __blocking_notifier_call_chain:nh->rwsem\u000a2. lock B <- vdd2_pre_post_func:gPVRSRVLock\u000a3. unlock A\u000a\u000aOn the CLK_POST_RATE_CHANGE/CLK_ABORT_RATE_CHANGE:\u000a4. lock A\u000a5. unlock B\u000a6. unlock A\u000a\u000aThe above has an ABA lock pattern which triggers the warning. This can't\u000alead to a dead lock though since at 3. we always release A, before it's\u000aagain acquired at 4. To avoid the warning use a wait queue based approach\u000aso that we can unlock B before 3.\u000a\u000aFixes: NB#166168 - PVR: possible circular locking dependency detected\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "f752e6bcaab5b7f2913ac5ca19eddf6191374878", "msg" : "gpu: pvr: fix lockdep problem", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.c" ], "commitId" : "3c33d74d57482c2c7aefe3a60e2b08e678c419ef", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: move ocp_cleanup() later during device deinit\u000a\u000aUnmap the OCP register range only after it's not needed any more.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "3c33d74d57482c2c7aefe3a60e2b08e678c419ef", "msg" : "gpu: pvr: move ocp_cleanup() later during device deinit", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/pvr_bridge_km.h" ], "commitId" : "645c824f601cc9d5d31c31a7d6b684df6b55dd2e", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: optimize pvr_lock() by inlining it\u000a\u000aAlso replace pvr_init_lock() by a static initializer.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "645c824f601cc9d5d31c31a7d6b684df6b55dd2e", "msg" : "gpu: pvr: optimize pvr_lock() by inlining it", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/event.c", "drivers/gpu/pvr/sysutils.c", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/pvr_debug.c", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "0ffdfb0871da6c788c66ee086702df8732d3ff48", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Disable driver if SGX HW recovery fails\u000a\u000aAt the moment SGX HW recovery doesn't succeed always and keeps the\u000aprocesses using the driver blocked. To avoid this give up after a\u000anumber of retries and disable further IOCTLs or interaction with\u000athe HW. This would still allow a complete restart of the graphics\u000astack including reloading the drivers and restarting the relevant\u000aprocesses.\u000a\u000aThe final fix is of course to find out why the recovery doesn't\u000asucceed.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "0ffdfb0871da6c788c66ee086702df8732d3ff48", "msg" : "gpu: pvr: Disable driver if SGX HW recovery fails", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/event.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/devicemem.c", "drivers/gpu/pvr/device.h", "drivers/gpu/pvr/pvrsrv.c", "drivers/gpu/pvr/servicesint.h" ], "commitId" : "dca40b25d8c7f1d20ebbe9cd59e6792f86e93e96", "timestamp" : 1579843579000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Reuse the same syncobject across all wraps\u000a\u000aCreate a hash table and store all the syncobjects that we create for\u000awrapped memory using the address of the buffer as the key. When a wrap\u000ahappens we check the hash table to see if the buffer has already been\u000awrapped and if so we retrieve the sync object and reuse it. When the\u000alast wrap that is using a syncobject is freed then we remove the\u000asyncobject from the hash table and free it.\u000a\u000aSigned-off-by: Mark Underwood \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:19 +0300", "id" : "dca40b25d8c7f1d20ebbe9cd59e6792f86e93e96", "msg" : "gpu: pvr: Reuse the same syncobject across all wraps", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/device.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/devicemem.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/servicesint.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "9e8f3684b348ae9030fae2b5e123667d2cb48bdc", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix handle allocation when sharing sync objects\u000a\u000aThis is needed by an upcoming patch fixing sync object sharing, which\u000arequires support for multiple sync object handles pointing to the same\u000async object. This will work if the handles are allocated in different\u000aprocesses, but will fail if allocted within a single process. Fix this\u000aby explicitly allowing the handle framework to allocate multiple\u000ahandles for the same object within a single process.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "9e8f3684b348ae9030fae2b5e123667d2cb48bdc", "msg" : "gpu: pvr: fix handle allocation when sharing sync objects", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/pvr_events.c", "drivers/gpu/pvr/sgx_bridge.h", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "0767f914de58d16400dd924ca38c76a046602bbe", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Add support for flip complete events\u000a\u000aAdd framework for flip complete events. The events are supposed\u0009to be\u000asignalled when a flip has completed. For now signal them immediately\u000ato avoid clients blocking indefinitely.\u000a\u000aSigned-off-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "0767f914de58d16400dd924ca38c76a046602bbe", "msg" : "gpu: pvr: Add support for flip complete events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "ee070f2945ac423cbf2a355a9c36d6f5fa0077d2", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Reduce code duplication\u000a\u000apvr_signal_sync_event() can be used twice with just a tiny\u000amodification to the list handling.\u000a\u000aSigned-off-by: Ville Syrjälä \u000aReviewed-by: Topi Pohjolainen \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "ee070f2945ac423cbf2a355a9c36d6f5fa0077d2", "msg" : "gpu: pvr: Reduce code duplication", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "2e84da3ef29e3ef19d52d764ec5d51c7d0da24f4", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Use DSS notifier to signal flip complete events\u000a\u000aUtilize to the DSS GO notifier to get callbacks when the flip\u000ahas completed.\u000a\u000aSigned-off-by: Ville Syrjälä \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "2e84da3ef29e3ef19d52d764ec5d51c7d0da24f4", "msg" : "gpu: pvr: Use DSS notifier to signal flip complete events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/omaplfb_displayclass.c" ], "commitId" : "a734a1b3aba05c7cd2c753d284112accabbe862e", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: omaplfb: remove unnecessary fb unblanking\u000a\u000aThis is unnecessary and is causing a lockdep problem with the DSS\u000adriver.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "a734a1b3aba05c7cd2c753d284112accabbe862e", "msg" : "gpu: pvr: omaplfb: remove unnecessary fb unblanking", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/omaplfb_displayclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "f42c77f05cbed680165d731e36d521d06ef56cc3", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add SGXScheduleProcessQueues to prepare for pvr_dev_lock\u000a\u000aThis will be needed to do things done in SGXScheduleProcessQueuesKM\u000alocklessly when pvr_dev_lock is added.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "f42c77f05cbed680165d731e36d521d06ef56cc3", "msg" : "gpu: pvr: add SGXScheduleProcessQueues to prepare for pvr_dev_lock", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "1942e4aa1abda1c2a76f456a2e7bf11fd6c2fd6e", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add dvfs lock\u000a\u000aWe need to protect the SGX HW access with a separate lock as the\u000apvr_lock. This is to overcome a lockdep issue between the clock\u000achange notification lock and pvr_lock.\u000a\u000aFixes: NB#181087 - pvrsrvkm: possible circular locking dependency detected\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "1942e4aa1abda1c2a76f456a2e7bf11fd6c2fd6e", "msg" : "gpu: pvr: add dvfs lock", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "b80f398e8af8a6fc6a2324974fb5515468937bc4", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: rename pvr_dvfs_lock to pvr_dev_lock\u000a\u000aThe new name better reflects what is actually protected.\u000a\u000aNo fuctional change.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "b80f398e8af8a6fc6a2324974fb5515468937bc4", "msg" : "gpu: pvr: rename pvr_dvfs_lock to pvr_dev_lock", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "526976db543140a84e124573939660ae00d9dc06", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix locking around HWRecoveryResetSGX\u000a\u000aOn the MISR / HW recovery path the pvr_dev_lock was taken twice\u000aleading to a dead-lock. This regression was introduced by commit\u000a\"gpu: pvr: add dvfs lock\".\u000a\u000aSpotted-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "526976db543140a84e124573939660ae00d9dc06", "msg" : "gpu: pvr: fix locking around HWRecoveryResetSGX", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c" ], "commitId" : "fa2f127a3df91b6afc65124b75da11242ff35bce", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove needless NULL check in BM_ImportMemory.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "fa2f127a3df91b6afc65124b75da11242ff35bce", "msg" : "gpu: pvr: Remove needless NULL check in BM_ImportMemory.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c" ], "commitId" : "08fe02508f6ec260f6fe9570bc6cf2eb5a8e4ebf", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove needless NULL check in BM_DestroyHeap.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "08fe02508f6ec260f6fe9570bc6cf2eb5a8e4ebf", "msg" : "gpu: pvr: Remove needless NULL check in BM_DestroyHeap.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c" ], "commitId" : "5b9d19b41d7ff7c2db00a42d3983434876d4d5ff", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Fixed formatting in buffer_manager.c\u000a\u000aFixed indentation and mixed code and declarations.\u000aNo functional change.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "5b9d19b41d7ff7c2db00a42d3983434876d4d5ff", "msg" : "gpu: pvr: Fixed formatting in buffer_manager.c", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c" ], "commitId" : "d5ce682e4a1ab627fb0ccef109350882224f8af4", "timestamp" : 1579843580000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove needless NULL check in WrapMemory.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:20 +0300", "id" : "d5ce682e4a1ab627fb0ccef109350882224f8af4", "msg" : "gpu: pvr: Remove needless NULL check in WrapMemory.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c" ], "commitId" : "a306e27cd21b6673c5d9c85c5515e9837cf78a0f", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove needless NULL check in BM_CreateHeap.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "a306e27cd21b6673c5d9c85c5515e9837cf78a0f", "msg" : "gpu: pvr: Remove needless NULL check in BM_CreateHeap.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/devicemem.c" ], "commitId" : "0723faf3101587770e9df6c6f54e789f796e48dd", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove needless NULL check in PVRSRVWrapExtMemoryKM.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "0723faf3101587770e9df6c6f54e789f796e48dd", "msg" : "gpu: pvr: Remove needless NULL check in PVRSRVWrapExtMemoryKM.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/devicemem.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/devicemem.c" ], "commitId" : "3074f4e7a9dd82a5d2557853e4710c1537f806ba", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Changed error-path condtion.\u000a\u000aChanged the condition to equivalent but less confusing one.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "3074f4e7a9dd82a5d2557853e4710c1537f806ba", "msg" : "gpu: pvr: Changed error-path condtion.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/devicemem.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/handle.c" ], "commitId" : "c3c4dde67a3727c54b6134f552761b7f6199f502", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Changed ReallocMem.\u000a\u000aA static analysis tool showed a possible defect in ReallocMem() -\u000aderefencing a null pointer. It was a false positive.\u000a\u000aThis patch slightly modifies ReallocMem() to avoid this warning.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "c3c4dde67a3727c54b6134f552761b7f6199f502", "msg" : "gpu: pvr: Changed ReallocMem.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/handle.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/hash.c" ], "commitId" : "1f67d728d27a782383912b2c24738fe5bead8322", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Check OSAllocMem return value.\u000a\u000aCheck OSAllocMem() return value instead of checking the pointer returned\u000aas a positional parameter.\u000a\u000aThis change makes static analysis tool happy.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "1f67d728d27a782383912b2c24738fe5bead8322", "msg" : "gpu: pvr: Check OSAllocMem return value.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/hash.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/hash.c" ], "commitId" : "aee8741611cea59a2bed6e641ad6651a96778aab", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Check OSAllocMem return value.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "aee8741611cea59a2bed6e641ad6651a96778aab", "msg" : "gpu: pvr: Check OSAllocMem return value.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/hash.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmap.c" ], "commitId" : "b34d16ec24ea312a586dc81b062c8ef62a6231c3", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove FIRST_PHYSICAL_PFN define.\u000a\u000aThe unsigned comparison pfn >= 0 is always true.\u000aRemoved FIRST_PHYSICAL_PFN define and simplified the condition.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "b34d16ec24ea312a586dc81b062c8ef62a6231c3", "msg" : "gpu: pvr: Remove FIRST_PHYSICAL_PFN define.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c" ], "commitId" : "3dcff984dd7317dfd07adcaa4d4ad6a897a874e3", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Removed needless NULL check in MMU_BIFResetPDAlloc.\u000a\u000apui8MemBlock cannot be NULL, so remove the check.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "3dcff984dd7317dfd07adcaa4d4ad6a897a874e3", "msg" : "gpu: pvr: Removed needless NULL check in MMU_BIFResetPDAlloc.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c" ], "commitId" : "6a52a2e68bff4ebb85f92eb596805ed3e834967b", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Check OSAllocMem return value.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "6a52a2e68bff4ebb85f92eb596805ed3e834967b", "msg" : "gpu: pvr: Check OSAllocMem return value.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c" ], "commitId" : "57a9e24a29122ed156bfe4a13efb89ad2d8ce508", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Check OSAllocMem return value.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "57a9e24a29122ed156bfe4a13efb89ad2d8ce508", "msg" : "gpu: pvr: Check OSAllocMem return value.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c" ], "commitId" : "bac03680dd8d936ec2ddad14e2974c11d4db7536", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Check OSAllocMem return value.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "bac03680dd8d936ec2ddad14e2974c11d4db7536", "msg" : "gpu: pvr: Check OSAllocMem return value.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c" ], "commitId" : "1d9941f35a0b438489ff325efb4c96c438027685", "timestamp" : 1579843581000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Remove SysAcquireData call in pvr_cleanup.\u000a\u000aRemove obsolete SysAcquireData() call.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:21 +0300", "id" : "1d9941f35a0b438489ff325efb4c96c438027685", "msg" : "gpu: pvr: Remove SysAcquireData call in pvr_cleanup.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "9362c39b61891423f14558f55d35836009527430", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Check SysAcquireData return value.\u000a\u000aSysAcquireData() could theoretically fail.\u000aThis patch adds missing return value check in SGXReadDiffCountersKM().\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "9362c39b61891423f14558f55d35836009527430", "msg" : "gpu: pvr: Check SysAcquireData return value.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_sgx_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "98dfb3e1c94a9b21c9fd88ad6c89afa050a07f2a", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pass IOCTL in param size to dispatch func\u000a\u000aThis is needed by an upcoming patch that differentiates between\u000aIOCTL parameter format based on it's size.\u000a\u000aAlso some ws change to silence checkpatch.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "98dfb3e1c94a9b21c9fd88ad6c89afa050a07f2a", "msg" : "gpu: pvr: pass IOCTL in param size to dispatch func", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxapi_km.h", "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/sgxkick.c", "drivers/gpu/pvr/sgxinfo.h", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "e2e17d19ebb2e336c7482d9d283ea14daf8d48ea", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Increase the max number of 3D TA status vals in kick requests\u000a\u000aThis is needed to support the to-be-added fence sync mechanism in\u000athe user space part. The change involves an ABI change, to make\u000athe transition smooth keep support for the old format as well.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "e2e17d19ebb2e336c7482d9d283ea14daf8d48ea", "msg" : "gpu: pvr: Increase the max number of 3D TA status vals in kick requests", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfo.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxapi_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "e0dd4f7ed308a25366d9e51d1f110f5b12ccb38b", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Fixed error path in cache flush function.\u000a\u000aPVRSRVCacheFlushDRIBW returns in the error path without releasing\u000acurrent->mm->mmap_sem semaphore.\u000aThe client application stalls forever and cannot be killed.\u000a\u000aSigned-off-by: Janusz Sobczak \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "e0dd4f7ed308a25366d9e51d1f110f5b12ccb38b", "msg" : "gpu: pvr: Fixed error path in cache flush function.", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "bf306b4323512a5f375f5cdd3aa5a48e0423ba75", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix locking on the HW recovery reset error path\u000a\u000apvr_dev_lock is unbalanced on the code path where HW recovery reset\u000afails.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "bf306b4323512a5f375f5cdd3aa5a48e0423ba75", "msg" : "gpu: pvr: fix locking on the HW recovery reset error path", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "e1913f07eee6d1ed2cdb2e6becf99c51ed23a4f7", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unnecessary udelay from the HW poll loop\u000a\u000aAt the moment the HW polling loop does a 50 usec delay between\u000aeach reading of the HW flag in question. Since this delay is no\u000aworse than just reading the HW flag continuously, get rid of it.\u000a\u000aThis will reduce the wait time from 50 usec to 25 usec in the\u000ageneral case.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "e1913f07eee6d1ed2cdb2e6becf99c51ed23a4f7", "msg" : "gpu: pvr: remove unnecessary udelay from the HW poll loop", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "62eee04a63fd1daab9a1f30fa3ea6b0d7efcd669", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix typo in SGXDoKickBW\u000a\u000aThis leads to the IOCTL failing in case the new structure format is used\u000awith it. Also fixes bounds checking for the old format.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "62eee04a63fd1daab9a1f30fa3ea6b0d7efcd669", "msg" : "gpu: pvr: fix typo in SGXDoKickBW", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/sgxpower.c" ], "commitId" : "06356669a37c6427fb57b20adeaea249b71f2341", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: split out setting power down delay into its own function\u000a\u000aThis will be needed by an upcoming patch setting the power-down delay\u000adynamically.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "06356669a37c6427fb57b20adeaea249b71f2341", "msg" : "gpu: pvr: split out setting power down delay into its own function", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "4aacfef93e1443635b3b0e288158b72feac9e9e9", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix SysGetSGXTimingInformation for cases when the HW is off\u000a\u000aThis function doesn't do anything that requires the HW to be on, so\u000aremove the assert about it. This will be needed by an upcoming patch,\u000arequiring this information with HW off.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "4aacfef93e1443635b3b0e288158b72feac9e9e9", "msg" : "gpu: pvr: fix SysGetSGXTimingInformation for cases when the HW is off", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/sgxpower.c" ], "commitId" : "04ae370d239ead99dc9bab435dac92bcf5906e84", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add support for dynamic timing of SGX HW power down\u000a\u000aThis is needed by the next patch, which actually enables the support.\u000a\u000aCurrently the driver implements an aggressive power management policy\u000aand powers down the HW very shortly (1 ms) after each completed command.\u000aThe resulting power-down and -up sequence between commands are relatively\u000along (~250usec), causing a delayed command execution and unnecessary CPU\u000aload.\u000a\u000aThere is a deadline at the end of each display Vsync period, by which\u000aall commands for the next frame must be completed. If the deadline is\u000amissed FPS goes down. To increase the chance that we meet the deadline\u000awe want to cut down on the above overhead.\u000a\u000aOne way to reduce the overhead is to get rid of the power-down/up\u000asequences between commands. The downside is the possibly higher power\u000aconsumption, so a solution has to minimize this side effect. Simply\u000aincreasing the power-down delay would result in a constant power\u000aconsumption increase. To see this let's consider the following two\u000acases given a 16 ms Vsync period.\u000a\u000aCase a:\u000a\u000a1. SGX command#1 for frame#N - 3 ms\u000a2. SGX idle - 3 ms\u000a3. SGX command#2 for frame#N - 3 ms\u000a4. SGX idle - 3 ms\u000a5. SGX command#3 for frame#N - 3 ms\u000a6. SGX idle - 1 ms\u000a7. Vsync\u000a8. SGX command#1 for frame#N+1 - 3 ms\u000a9. SGX idle - 3 ms\u000a10. SGX command#2 for frame#N+1 - 3 ms\u000a11. SGX idle - 3 ms\u000a12. SGX command#3 for frame#N+1 - 3 ms\u000a13. SGX idle - 1 ms\u000a14. Vsync\u000a... same pattern repeating for several frames\u000a\u000aHere we need to increase the power-down delay to 4 ms, to avoid the\u000aoverhead at 2.,4.,9.,11. and to increase the chance to meet the deadlines\u000aat 7. and 14.\u000a\u000aCase b:\u000a\u000a1. SGX command#1 for frame#N - 1 ms\u000a2. SGX idle - 1 ms\u000a3. SGX command#2 for frame#N - 1 ms\u000a4. SGX idle - 1 ms\u000a5. SGX command#3 for frame#N - 1 ms\u000a6. SGX idle - 11 ms\u000a7. Vsync\u000a8. SGX command#1 for frame#N+1 - 1 ms\u000a9. SGX idle - 1 ms\u000a10. SGX command#2 for frame#N+1 - 1 ms\u000a11. SGX idle - 1 ms\u000a12. SGX command#3 for frame#N+1 - 1 ms\u000a13. SGX idle - 11 ms\u000a14. Vsync\u000a... same pattern repeating for several frames\u000a\u000aHere we don't have a risk of missing the deadlines, so we could\u000apower-down immediately after 5. and 12. but we will delay the power-down\u000aby 4 ms due to the constraint in case a. This energy waste will be\u000aincured in each of the following frames having a similar command\u000ascheduling pattern.\u000a\u000aThe solution in the following patch minimizes the energy waste while\u000aachieving the original goal, by tracking \"command bursts\". In a burst\u000acommand execution periods are separated by idle periods of less than a\u000afixed amount of time (3 ms). Power-down is avoided between commands\u000awithin one burst, but it's performed immediately after the last command\u000aof the burst. For example all commands in case a constitute one burst,\u000aso we won't have any power-down there. In case b we have two bursts:\u000afirst burst consisting of 1.,3.,5. second burst consisting of 8.,10.,12.,\u000aso we will power down immediately after 5. and 12.\u000a\u000aIn cases where commands are interleaved (well behaving applications)\u000awe'll see power consumption decreasing due to the immediate power down\u000avs. the current 1ms delay. For other cases we might see a slight\u000aincrease in power consumption due to not powering down between commands,\u000abut these are the very cases where we have a risk of not meeting the frame\u000adeadlines, so the compromise looks like justified.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "04ae370d239ead99dc9bab435dac92bcf5906e84", "msg" : "gpu: pvr: add support for dynamic timing of SGX HW power down", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxtransfer.c", "drivers/gpu/pvr/sgxpower.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/sgxkick.c" ], "commitId" : "62ec0849ed86813c6a21e29a70896e06a34f59e7", "timestamp" : 1579843582000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: wire in the dynamic power-down delay calculation\u000a\u000aSupport for this was added in the previous patch.\u000a\u000aWe're considering only the TA/3D and 2D blit commands to be part of a\u000acommand burst. The rest of the commands are power management related and\u000awe can ignore them when detecting repeated burst patterns.\u000a\u000aFixes: NB#195379 - SGX sleep causes performance penalty\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:22 +0300", "id" : "62ec0849ed86813c6a21e29a70896e06a34f59e7", "msg" : "gpu: pvr: wire in the dynamic power-down delay calculation", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxtransfer.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/pvr_events.c", "drivers/gpu/pvr/bridged_sgx_bridge.c", "drivers/gpu/pvr/sgx_bridge.h" ], "commitId" : "388395ae3913142522619407df1d520eff3b82dd", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Expose new display events to user space\u000a\u000aThis exposes the new dss event that can be used for more fine grained\u000asynchronization with display updates.\u000a\u000aThis change is backward compatible with old user space.\u000a\u000aSigned-off-by: Pauli Nieminen \u000aSigned-off-by: Ville Syrjälä \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "388395ae3913142522619407df1d520eff3b82dd", "msg" : "gpu: pvr: Expose new display events to user space", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.h", "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "ee52d297188d448d6843018fb027d17aa36ddfae", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Snapshot pending write ops during event request\u000a\u000aThe render sync event should only wait until write operations\u000athat are pending when the event is requested have completed.\u000aNew operations started after requesting the event should not\u000adelay the event delivery, nor should any read operations.\u000a\u000aSigned-off-by: Ville Syrjälä \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "ee52d297188d448d6843018fb027d17aa36ddfae", "msg" : "gpu: pvr: Snapshot pending write ops during event request", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgx_options.h", "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/sgxinfo.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "6d60255d14a1bafe8110c20216707de1f877c6e6", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove build time ABI dependency on the EDM trace option\u000a\u000aSo that we can build user / kernel space independently on the EDM\u000atracing option being configured or not.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "6d60255d14a1bafe8110c20216707de1f877c6e6", "msg" : "gpu: pvr: remove build time ABI dependency on the EDM trace option", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfo.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_options.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/perproc.h", "drivers/gpu/pvr/bridged_sgx_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "25e33c1b48b564685317076b815589051fb91745", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: make the IOCTL i/f compatible for old ABI users\u000a\u000aThe previous patch breaks the IOCTL i/f for current user space code.\u000aThis change will notice such calls based on the IOCTL parameter size and\u000afix up the param struct accordingly.\u000a\u000aThis patch can be reverted once applications are converted to use the new\u000aABI.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "25e33c1b48b564685317076b815589051fb91745", "msg" : "gpu: pvr: make the IOCTL i/f compatible for old ABI users", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/perproc.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Kconfig" ], "commitId" : "29752a53d7dd2a1d6a2ab2d8c5a38d9b2ca85721", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix Kconfig description for EDM tracing\u000a\u000aWe don't have a dependency on user space configuration any more, so\u000afix the description accordingly.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "29752a53d7dd2a1d6a2ab2d8c5a38d9b2ca85721", "msg" : "gpu: pvr: fix Kconfig description for EDM tracing", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "9285c2fb7181c0693eb0efbce7b55a0b2b7eaf60", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove runtime dependency on the EDM trace option\u000a\u000aSo that we can use the same kernel driver with user space having the\u000aoption either configured or not.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "9285c2fb7181c0693eb0efbce7b55a0b2b7eaf60", "msg" : "gpu: pvr: remove runtime dependency on the EDM trace option", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "d13f932a0b94b083de631ff0dfd709e11440f8ed", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: move debugfs entries under a new pvr dir\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "d13f932a0b94b083de631ff0dfd709e11440f8ed", "msg" : "gpu: pvr: move debugfs entries under a new pvr dir", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "e76e7e4134ad845c6b9981893a4c0038c7427b0e", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: make debugfs available in release build too\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "e76e7e4134ad845c6b9981893a4c0038c7427b0e", "msg" : "gpu: pvr: make debugfs available in release build too", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "05e0524b273d754bce4b8b38f43680039b4175b9", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add snprint_edm_trace\u000a\u000aNeeded by an upcoming patch adding a debugfs entry to dump the trace.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "05e0524b273d754bce4b8b38f43680039b4175b9", "msg" : "gpu: pvr: add snprint_edm_trace", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "012af4442a0f46b7920d98a311a33b4c23c84b7c", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add debugfs entry to read the EDM trace\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "012af4442a0f46b7920d98a311a33b4c23c84b7c", "msg" : "gpu: pvr: add debugfs entry to read the EDM trace", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "98857aea82e58add61ccd2bda685ffeb69ce3e57", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: print some init failure messages in release mode too\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "98857aea82e58add61ccd2bda685ffeb69ce3e57", "msg" : "gpu: pvr: print some init failure messages in release mode too", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/perproc.h", "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/bridged_sgx_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "7926cc8563adefdaa57c2999dfbfc2d87dca0758", "timestamp" : 1579843583000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove ABI compatibility hack from SGXInitPart2 IOCTL\u000a\u000aBy now everyone should have a recent enough kernel/user space library,\u000aso this isn't needed.\u000a\u000aThis reverts commit \"gpu: pvr: make the IOCTL i/f compatible for old ABI users\".\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:23 +0300", "id" : "7926cc8563adefdaa57c2999dfbfc2d87dca0758", "msg" : "gpu: pvr: remove ABI compatibility hack from SGXInitPart2 IOCTL", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/perproc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxapi_km.h", "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/sgxkick.c", "drivers/gpu/pvr/sgxinfo.h", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "c8732082ac73ba74454447fb0ad5de1da1e36b3d", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove ABI compatibility hack from SGXKick IOCTL\u000a\u000aBy now everyone should have a recent enough kernel/user space library,\u000aso this isn't needed.\u000a\u000aThis will revert the compatibility fixup parts of the following commit:\u000a\"gpu: pvr: Increase the max number of 3D TA status vals in kick requests\"\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "c8732082ac73ba74454447fb0ad5de1da1e36b3d", "msg" : "gpu: pvr: remove ABI compatibility hack from SGXKick IOCTL", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxapi_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfo.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "e29d1d467bc309d73d15c0d28c5b2120d769e133", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: refactor dump_process_info\u000a\u000aSplit out from the function the part getting the process data based on\u000athe current SHX HW memory context. This functionality will be needed by\u000aan upcoming patch.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "e29d1d467bc309d73d15c0d28c5b2120d769e133", "msg" : "gpu: pvr: refactor dump_process_info", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxapi_km.h", "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/sgxinfo.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "f72994cdef2793326a8a3bb9aed819485ee068d0", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: dump render status buffers during SGX HW recovery\u000a\u000aTo aid debugging, dump any status buffers that are provided by the\u000aogles user space library for the rendering context that was active\u000aat the time of recovery. At the moment the USSE final patched\u000aversions of vertex and fragment shaders that were bound within the\u000aframe causing the HWRec are provided, but later on more types can be\u000aadded.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "f72994cdef2793326a8a3bb9aed819485ee068d0", "msg" : "gpu: pvr: dump render status buffers during SGX HW recovery", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxapi_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfo.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/ra.c", "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/proc.c" ], "commitId" : "937ea7906dfed8fbd08ca9c2e54d2daf6222fe8e", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: improve per process procfs entry/dir handling\u000a\u000aWhen building with full debug, a lot of \"Resource Arena\" (ra) data is\u000abeing made available in the rather painful procfs, including per process\u000ara info, kept in process specific subdirectories.\u000a\u000aAdding and removing process specific entries from procfs took the PID of\u000athe currently running process; which sometimes failed during cleanup,\u000awhen the current process might no longer be anything tracked by the\u000adriver. This then resulted in some strange behaviour, where it was\u000aimpossible to cleanup a process specific procfs directory, resulting\u000ain an endless loop.\u000a\u000aSince process specific procfs entries are only created in the RA code,\u000awe now track the pid in the RA struct. When we pass this pid to\u000aboth the procfs entry creation and removal functions, we now do\u000areliably clean up the procfs entries.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "937ea7906dfed8fbd08ca9c2e54d2daf6222fe8e", "msg" : "gpu: pvr: improve per process procfs entry/dir handling", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/ra.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "e404384d66604414eb588973c62266b4d2deb4b5", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: disable sgx active power management while pvrtune is running\u000a\u000aDisable sgx active power management while sgxPerfServer is running.\u000aThis enables pvrtune to run correctly without data loss.\u000a\u000aSigned-off-by: Alex Crowther \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "e404384d66604414eb588973c62266b4d2deb4b5", "msg" : "gpu: pvr: disable sgx active power management while pvrtune is running", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "545bfc29966893b48b3367c243a0c483edc4c4da", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path during SGX device initialization\u000a\u000aThis also fixes some coverity reports.\u000a\u000aFixes: NB#233667 - Dereferencing possibly NULL pointer in sgxinit.c\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "545bfc29966893b48b3367c243a0c483edc4c4da", "msg" : "gpu: pvr: fix error path during SGX device initialization", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/pvr_debugfs.h", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "ad6645261575481a04a2e1bf02bc6b14ee39c075", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: move debugfs infrastructure to its own files\u000a\u000apvr_debug.* originally only provided some contrived code (which needs\u000asanitation) to do debug printing.\u000a\u000aFuture HW Recovery code will also be using debugfs and it makes sense\u000ato lump all of them together in pvr_debugfs.*\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "ad6645261575481a04a2e1bf02bc6b14ee39c075", "msg" : "gpu: pvr: move debugfs infrastructure to its own files", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_debugfs.h" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.h", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "3241b4e26fd1d4f935fe806ffa7db82fd6441eab", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: add initial hwrec dumping infrastructure\u000a\u000aCurrently contains hwrec_event and hwrec_time.\u000a\u000ahwrec_event blocks the reader until a hwrec event happens. This allows\u000aa simple shell application to sleep until a hwrec happens.\u000a\u000ahwrec_time contains a timestamp to enable a simple shell application\u000ato create unique dumps.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "3241b4e26fd1d4f935fe806ffa7db82fd6441eab", "msg" : "gpu: pvr: debugfs: add initial hwrec dumping infrastructure", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.h", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "66a6851c199198a3e621d76f7486d2eb30c67139", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: add hwrec register dump\u000a\u000aFull register dump available after hwrec event in the file hwrec_regs.\u000a\u000aThe full register page is read out, except [0xA08,0xA50] as this range\u000aresults in a SIGBUS.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "66a6851c199198a3e621d76f7486d2eb30c67139", "msg" : "gpu: pvr: debugfs: add hwrec register dump", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.h", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/pvr_debugfs.h" ], "commitId" : "611a965fc417e1ca1c2971c2173846fe8f695e22", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: add hwrec context dump\u000a\u000aA full context is now provided through hwrec_mem. This includes\u000apage directory, page tables and all mapped pages.\u000a\u000aThis code is only built when debugfs is enabled, and when build type\u000ais \"Debug\".\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "611a965fc417e1ca1c2971c2173846fe8f695e22", "msg" : "gpu: pvr: debugfs: add hwrec context dump", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "58ece4599bcb2905e20230e1244d2a71094b8160", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: add hwrec edm trace\u000a\u000aAnd move all edm trace printing code to pvr_debugfs.c; since now only\u000adebugfs/pvr/edm_trace and debugfs/pvr/hwrec_edm use it.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "58ece4599bcb2905e20230e1244d2a71094b8160", "msg" : "gpu: pvr: debugfs: add hwrec edm trace", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/sgxinfokm.h", "drivers/gpu/pvr/pvr_debugfs.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "429fead988523e7a406a0baaabebbfb77c2ca5a4", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: add hwrec status buffer dumping\u000a\u000aMove code over from sgxinit.c, and dump status buffers in binary format\u000ato a debugfs file instead of sending it as %08X's to syslog.\u000a\u000aShares process info from the top level now, instead of acquiring this\u000ainformation several times. This now also prints the caller of the\u000aHWRecovery routine.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "429fead988523e7a406a0baaabebbfb77c2ca5a4", "msg" : "gpu: pvr: debugfs: add hwrec status buffer dumping", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinfokm.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/syscommon.h", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "01dcb1ab93cc2feb62af694c6dffc4375b400026", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: SYS_DATA::bPowerUpPDumped is unused\u000a\u000aNothing in the graphics stack uses this.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "01dcb1ab93cc2feb62af694c6dffc4375b400026", "msg" : "gpu: pvr: pdump: SYS_DATA::bPowerUpPDumped is unused", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/syscommon.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/pdump_km.h" ], "commitId" : "26dc785566eb771e575fc9e56a64272e364a8b54", "timestamp" : 1579843584000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: consolidate some code inside PDUMP defines\u000a\u000aNo functional changes.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:24 +0300", "id" : "26dc785566eb771e575fc9e56a64272e364a8b54", "msg" : "gpu: pvr: pdump: consolidate some code inside PDUMP defines", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/pdump_km.h", "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "f10a8a9aae56b56e3206f7449083d88e79095736", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove unused bridge calls\u000a\u000aUserspace never calls _PDUMP_DRIVERINFO, _PDUMP_DUMPREADREG,\u000a_PDUMP_STARTINITPHASE, or _PDUMP_STOPINITPHASE. So remove the\u000arespective handlers and the pdump code.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "f10a8a9aae56b56e3206f7449083d88e79095736", "msg" : "gpu: pvr: pdump: remove unused bridge calls", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/dbgdrvif.h", "drivers/gpu/pvr/pdump_common.c", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/pdump_km.h" ], "commitId" : "f549077a0cd8527afdb8e1ba251e2b04bc60dc3d", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove unused pdump functions\u000a\u000aChecked symbols and defines in pdump_km.h, and removed them when unused.\u000asparse then flagged the unused functions in pdump.c and pdump_common.c\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "f549077a0cd8527afdb8e1ba251e2b04bc60dc3d", "msg" : "gpu: pvr: pdump: remove unused pdump functions", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_common.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/dbgdrvif.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxpower.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/pdump_km.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "1b23629ab5a7909d524e2b89451166509e1c7778", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove lastframe support\u000a\u000aUserspace does not use this, so no functional change.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "1b23629ab5a7909d524e2b89451166509e1c7778", "msg" : "gpu: pvr: pdump: remove lastframe support", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "892fc99a5b5761de4671ef1d9a0b194a49036346", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: stop depending on dbgdrvif.h\u000a\u000aStop including dbgdrvif.h in pdump.c and add empty skeleton for\u000aformer dbgdrv functionality.\u000a\u000aSo replace the pointer with callbacks with locally defined, mostly\u000aempty, functions. Provide stripped down struct DBG_STREAM and define\u000athe still referenced flags inside pdump.c.\u000a\u000aOnly functional change is that the dbgdrv module and the pdump\u000auserspace utility are now completely useless.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "892fc99a5b5761de4671ef1d9a0b194a49036346", "msg" : "gpu: pvr: pdump: stop depending on dbgdrvif.h", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Kconfig", "drivers/gpu/pvr/dbgdrvif.h", "drivers/gpu/pvr/tools/hostfunc.h", "drivers/gpu/pvr/tools/ioctl.c", "drivers/gpu/pvr/tools/main.c", "drivers/gpu/pvr/tools/dbgdriv.c", "drivers/gpu/pvr/tools/linuxsrv.h", "drivers/gpu/pvr/tools/hotkey.c", "drivers/gpu/pvr/pvrconfig.h", "drivers/gpu/pvr/tools/ioctl.h", "drivers/gpu/pvr/tools/dbgdriv.h", "drivers/gpu/pvr/tools/Makefile", "drivers/gpu/pvr/ioctldef.h", "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/tools/hotkey.h", "drivers/gpu/pvr/tools/hostfunc.c" ], "commitId" : "564e32e4948fc7db4522fd30bf02d6d6add6a787", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove dbgdrv\u000a\u000aRemove now unused dbgdrv files, and set the pdump Kconfig option to bool.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "564e32e4948fc7db4522fd30bf02d6d6add6a787", "msg" : "gpu: pvr: pdump: remove dbgdrv", "paths" : [ { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/hostfunc.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/hotkey.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/hostfunc.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/main.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrconfig.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/Makefile" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/ioctldef.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/ioctl.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/ioctl.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/dbgdrvif.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/hotkey.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/linuxsrv.h" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/dbgdriv.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/tools/dbgdriv.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "5ad21c9216e6f5725834d5bc989faea5303dd901", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove wrapping of globals in pdump.c\u000a\u000aThe gsDBGPdumpState struct just clutters up the place.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "5ad21c9216e6f5725834d5bc989faea5303dd901", "msg" : "gpu: pvr: pdump: remove wrapping of globals in pdump.c", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "7d735aa52d6cae541623535ae72fdf6f982d9ac6", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove pdump marker code\u000a\u000aThis was used to signal to the userspace tool that the parameter stream\u000ahas grown beyond 1GB. We can handle files bigger than that in our world.\u000a\u000aNo functional change, as far as the services module is concerned.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "7d735aa52d6cae541623535ae72fdf6f982d9ac6", "msg" : "gpu: pvr: pdump: remove pdump marker code", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "5c925e6695e65b52804e0a4922a5fcc2560367ab", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: move functions around to better reflect dependencies\u000a\u000aThis way, no prototypes have to be provided, and the use of PDUMP\u000amacros is also avoided.\u000a\u000aNo functional changes.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "5c925e6695e65b52804e0a4922a5fcc2560367ab", "msg" : "gpu: pvr: pdump: move functions around to better reflect dependencies", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump_common.c", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/pdump_km.h", "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "0ad7e264c30ceb17fb2731b88f68438de3007c71", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: reduce error propagation from pdump to userspace\u000a\u000aWhen pdump logging fails, the driver should, as much as possible,\u000acontinue working. Bad arguments should however be flagged.\u000a\u000aThis allows for a rewrite of DbgWrite()/PdumpWriteILock() to pdump_write().\u000a\u000aAlso remove the parameter write in PDumpPDDevPAddrKM, this parameter data\u000ais simply not referenced and the data sent to the script anyway.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "0ad7e264c30ceb17fb2731b88f68438de3007c71", "msg" : "gpu: pvr: pdump: reduce error propagation from pdump to userspace", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_common.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "bcf6e25dfec1f7182c1b7cf4008d43b5eee4c11e", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: rewrite PDumpWriteString2() to pdump_print()\u000a\u000aMaking pdump_print accept variable arguments directly significantly\u000asimplifies string printing to script, throughout the whole of pdump.c\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "bcf6e25dfec1f7182c1b7cf4008d43b5eee4c11e", "msg" : "gpu: pvr: pdump: rewrite PDumpWriteString2() to pdump_print()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "4810481606f954dba17da20412a7101d1fcc657a", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: rewrite PDumpCommentKM\u000a\u000aAnd turn some standard printing where the strings starts with \"--\"\u000ainto comments.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "4810481606f954dba17da20412a7101d1fcc657a", "msg" : "gpu: pvr: pdump: rewrite PDumpCommentKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "90a19398cfdcde740c5bb59682a6c239c53c9a28", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove param offset handling\u000a\u000aCurrently, we are not storing any data, but in future, we will be\u000astoring both script and param to the same stream. This removes the\u000aneed to reference the param stream from the script stream, and the\u000alogical issues that arise from this, especially in light of frame\u000abased storage, with frame culling happening.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "90a19398cfdcde740c5bb59682a6c239c53c9a28", "msg" : "gpu: pvr: pdump: remove param offset handling", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "21ff47e16bea51c30a4f92d2480a769fbfe07eba", "timestamp" : 1579843585000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: review use of PDumpSuspended\u000a\u000aPDumpSuspended is handled by pdump_write() now.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:25 +0300", "id" : "21ff47e16bea51c30a4f92d2480a769fbfe07eba", "msg" : "gpu: pvr: pdump: review use of PDumpSuspended", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/pdump_km.h" ], "commitId" : "b2b4e66d9b32653c1c8c663e3d6d260eef7046bd", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: assume that SGX_MMU_PAGE_SIZE equals PAGE_SIZE\u000a\u000aThis way, the address mangling code becomes a lot clearer.\u000a\u000aThe following changes are made:\u000aSGX_MMU_PAGE_SIZE -> PAGE_SIZE.\u000aSGX_MMU_PDE_ADDR_MASK -> PAGE_MASK\u000a~(PAGE_SIZE - 1) -> PAGE_MASK\u000a(Address >> SGX_MMU_PAGE_SHIFT) * PAGE_SIZE -> Address & PAGE_MASK\u000a\u000aA few functions which get SGX_MMU_PAGE_SIZE passed lose this\u000aargument and use PAGE_SIZE internally.\u000a\u000aNo functional changes on machines where PAGE_SIZE is the same for\u000athe host as for the sgx.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "b2b4e66d9b32653c1c8c663e3d6d260eef7046bd", "msg" : "gpu: pvr: pdump: assume that SGX_MMU_PAGE_SIZE equals PAGE_SIZE", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "e18b8365e3db7b10b20c8f65a6e2274ae4d9f9db", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: clean up logic across pdump.c\u000a\u000aThis patch is the least obvious of the set. It removes useless\u000avariables, superfluous calculations, cleans up loops, and makes a few\u000afunctions wrap others instead of copying them.\u000a\u000aShould be no functional change, but as said, very non-obvious.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "e18b8365e3db7b10b20c8f65a6e2274ae4d9f9db", "msg" : "gpu: pvr: pdump: clean up logic across pdump.c", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/buffer_manager.c" ], "commitId" : "1595ee706f80528914737d8d036dbc6c3117bc0a", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove page offset juggling\u000a\u000aThe offset from the start of the page never changes when changing\u000aaddress spaces, just the page address changes.\u000a\u000aIf an out of place assert is removed, (as all it could change is\u000athe address printed in an error message), then BM_GetPhysPageAddr()\u000atakes any address, and returns the physical address of the page.\u000aIt can deal with an offset, and will return the page address\u000awithout offset.\u000a\u000aThese two facts were used to reduce the address wrangling logic even\u000afurther.\u000a\u000aAn obviously wrong masking was fixed in PDumpMem2KM.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "1595ee706f80528914737d8d036dbc6c3117bc0a", "msg" : "gpu: pvr: pdump: remove page offset juggling", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pdump.c" ], "commitId" : "63d0c03f3f2b0755542c0ca9472acdf9613e82b6", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: sanitise stream handling\u000a\u000aUpper level pdump calls now have pdump_print and pdump_dump to their\u000adisposal. The former dumps strings, the second dumps raw data to\u000athe pdump stream.\u000a\u000aThis commit also sanitises debug mode handling to have disabled,\u000astandard and full modes only.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "63d0c03f3f2b0755542c0ca9472acdf9613e82b6", "msg" : "gpu: pvr: pdump: sanitise stream handling", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pdump_common.c", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/pdump_km.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "74f9bda2f9fc152c09350a1f9553b311ce4529f2", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: rewrite PDumpMemUM()\u000a\u000aNow that we have cleared up the streams, we can delay the copy_from_user()\u000auntil copying into the streams. This makes PDumpMemUM highly similar to\u000aPDumpMemKM.\u000a\u000aSo, split out the printing part from PDumpMemKM, and handle parameter\u000astream dumping separately for PDumpMemKM and PDumpMemUM.\u000a\u000aIn turn, this allows the removal of the separate buffer which was the\u000aheart of pdump_common.c, which is removed as well.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "74f9bda2f9fc152c09350a1f9553b311ce4529f2", "msg" : "gpu: pvr: pdump: rewrite PDumpMemUM()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/pdump_common.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxtransfer.c", "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/sysconfig.c", "drivers/gpu/pvr/devicemem.c", "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/pvr_pdump.c", "drivers/gpu/pvr/sgxpower.c", "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/pvr_pdump.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/pdump_km.h", "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/bridged_sgx_bridge.c", "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pb.c", "drivers/gpu/pvr/sgxutils.c", "drivers/gpu/pvr/pdump.c", "drivers/gpu/pvr/sgxkick.c", "drivers/gpu/pvr/sgxreset.c", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "3fc4af418dfc8b0c3817547177795aa0cffcd998", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: move pdump.c and pdump_km.h to pvr_pdump.[ch]\u000a\u000aAlso make pvr_pdump.c build fully conditional.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "3fc4af418dfc8b0c3817547177795aa0cffcd998", "msg" : "gpu: pvr: pdump: move pdump.c and pdump_km.h to pvr_pdump.[ch]", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxtransfer.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxreset.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/devicemem.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "delete", "file" : "drivers/gpu/pvr/pdump_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pb.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_pdump.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/pvr_pdump.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c", "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/pvr_pdump.c", "drivers/gpu/pvr/sgxreset.c" ], "commitId" : "b610dfd0f857e767df9e510b5a92c8745b8867b3", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: remove unused arguments\u000a\u000aThe eDeviceType passed to SysCpuPAddrToDevPAddr is not used by\u000aSysCpuPAddrToDevPAddr at all. So stop passing eDeviceType to pdump\u000afunctions.\u000a\u000aIn the other cases, hUniqueTag is very unique indeed.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "b610dfd0f857e767df9e510b5a92c8745b8867b3", "msg" : "gpu: pvr: pdump: remove unused arguments", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxreset.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c", "drivers/gpu/pvr/pvr_pdump.c", "drivers/gpu/pvr/pvr_pdump.h" ], "commitId" : "52351fedf1deca80019066db41df2f2d9916e953", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: rename PDumpMem2KM to PDumpPageTableKM\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "52351fedf1deca80019066db41df2f2d9916e953", "msg" : "gpu: pvr: pdump: rename PDumpMem2KM to PDumpPageTableKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgx_bridge.h" ], "commitId" : "9178e3b06cb0fc8f088aa7e2a4e781b4ca449eb1", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: silence sparse warnings in sgx_bridge pdump code\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "9178e3b06cb0fc8f088aa7e2a4e781b4ca449eb1", "msg" : "gpu: pvr: pdump: silence sparse warnings in sgx_bridge pdump code", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pvr_pdumpfs.h", "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/pvr_pdump.c" ], "commitId" : "f61810b2b047fee031a5887565b92799c596fb84", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdump: move empty back-end into pvr_pdumpfs.[ch]\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "f61810b2b047fee031a5887565b92799c596fb84", "msg" : "gpu: pvr: pdump: move empty back-end into pvr_pdumpfs.[ch]", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_pdumpfs.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/pvr_pdump.c", "drivers/gpu/pvr/pvr_pdumpfs.h" ], "commitId" : "6949a68830f2d0d4555f7675684f53c533f98a4a", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add pdumpfs_mutex\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "6949a68830f2d0d4555f7675684f53c533f98a4a", "msg" : "gpu: pvr: pdumpfs: add pdumpfs_mutex", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Kconfig", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/pvr_debugfs.h" ], "commitId" : "cba23bc648a4bd457df24e15ee046eecba7bc38c", "timestamp" : 1579843586000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add Kconfig and debugfs pdump mode handling\u000a\u000aThis adds the pvr/pdump debugfs subdirectory, and adds two files there:\u000amode and modes_possible. The modes_possible file is read-only and\u000alists the different modes (disabled, standard, full). The mode file\u000ais where we read and set the current mode.\u000a\u000aKconfig now provides an option to select the initial mode pdump\u000ais in.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:26 +0300", "id" : "cba23bc648a4bd457df24e15ee046eecba7bc38c", "msg" : "gpu: pvr: pdumpfs: add Kconfig and debugfs pdump mode handling", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.h", "drivers/gpu/pvr/pvr_pdump.h", "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/pvr_pdump.c", "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "7eba286e3db089a857350b037860d0d0f5388757", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add frame struct and initial frame handling code\u000a\u000aNow we are tracking frames correctly, but we are not accepting any data\u000ayet. frame_current is the last of frame_stream, and the frame that we\u000awould be writing to.\u000a\u000aNew frames are created when userspace flags the start of a new frame\u000awith PDumpSetFrameKM. This is also where we deliberately change the\u000apdump content by adding two comments. One for flagging the end of the\u000aprevious frame, one for the start of the new frame.\u000a\u000aWe keep at most frame_count_max frames around, older frames will be\u000aremoved by frame_cull() which gets called when a new frame gets\u000acreated.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "7eba286e3db089a857350b037860d0d0f5388757", "msg" : "gpu: pvr: pdumpfs: add frame struct and initial frame handling code", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/Kconfig" ], "commitId" : "a9652568955d3311d71ca4809d9478aa0738e267", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: make frame_count_max configurable\u000a\u000aBoth through a Kconfig option and through debugfs.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "a9652568955d3311d71ca4809d9478aa0738e267", "msg" : "gpu: pvr: pdumpfs: make frame_count_max configurable", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/pvr_pdump.c" ], "commitId" : "5d6540a442f1092bda8e7d5bf841a4f91d3d7aca", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: start storing pdump data\u000a\u000aPage based allocation, with built in copy_from_user to minimise buffer\u000acopies. Up to 2040 pages of data are kept per frame, if this amount is\u000aexceeded, an error message is printed, and a new frame is created\u000aautomatically.\u000a\u000aParameter data is stored inside the same stream as script data, but\u000ais encapsulated in \"BIN %08X:\"...\"-- BIN END\".\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "5d6540a442f1092bda8e7d5bf841a4f91d3d7aca", "msg" : "gpu: pvr: pdumpfs: start storing pdump data", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdump.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c" ], "commitId" : "ac6265d3fcfec41f762c6d3bd0d7495b9303d061", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add initial frame handling and debugfs support\u000a\u000aThis adds the separate handling of the initial frame, and adds\u000adebugfs support for this initial frame.\u000a\u000aThe initial frame is the frame started when the driver is initialised.\u000aOnce userspace flags the first frame, the initial frame is ended, and\u000aa new frame started, but the initial frame is not part of the stream\u000alist. The initial frame therefor does not get culled as part of\u000astandard frame culling and is kept around for the life of the driver.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "ac6265d3fcfec41f762c6d3bd0d7495b9303d061", "msg" : "gpu: pvr: pdumpfs: add initial frame handling and debugfs support", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c" ], "commitId" : "1a34bf0e39752a10b345c5fc4baf189639601342", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add debugfs entries for the current frame\u000a\u000aWe keep another pointer to the current_frame around, so that the\u000adata in our debugfs files is predictable.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "1a34bf0e39752a10b345c5fc4baf189639601342", "msg" : "gpu: pvr: pdumpfs: add debugfs entries for the current frame", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c" ], "commitId" : "cc03630ee39f48280dbc14c78327f948db24bb3e", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add stream offset tracking\u000a\u000aTrack the size of the stored data, this is split in start and end,\u000aso that the next commit can use the start and end to read out the\u000astream correctly, even with vanishing frames (where the missing\u000adata can be clearly marked).\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "cc03630ee39f48280dbc14c78327f948db24bb3e", "msg" : "gpu: pvr: pdumpfs: add stream offset tracking", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c" ], "commitId" : "efc0b8a53cb827ff37cb70fcd055c2aaa46e13f5", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: add stream_frames debugfs entry\u000a\u000aA mechanism to read out this data reliably is put in place. And data\u000ais only lost when the stream is no longer being read or when a hard\u000alimit of 1024 frames has been reached when the stream is still open.\u000aIn case of missing data, the buffer is padded with \"...\" to make\u000aup for the missing bytes and to clear mark them.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "efc0b8a53cb827ff37cb70fcd055c2aaa46e13f5", "msg" : "gpu: pvr: pdumpfs: add stream_frames debugfs entry", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c" ], "commitId" : "05599fca91ed41ec1a906b92b07855c8ef501121", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pdumpfs: fix for imgtec simulator\u000a\u000aWhen full dumping is enabled through init, the simulator throws in the\u000atowel on the dumped CCB wait at the end of initialisation.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "05599fca91ed41ec1a906b92b07855c8ef501121", "msg" : "gpu: pvr: pdumpfs: fix for imgtec simulator", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "14b98ab10ae955b2de5ec0d891a403ca21673b98", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: change snprintf to scnprintf\u000a\u000asnprintf returns how many characters _would_ have been written if there\u000ahad been enough space, whereas scnprintf returns the actual numer of\u000awritten characters. The latter fits better our use case.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "14b98ab10ae955b2de5ec0d891a403ca21673b98", "msg" : "gpu: pvr: change snprintf to scnprintf", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/pvr_debugfs.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "83768dff8b41267caa7326b7459f6545ec85ae0b", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: reinstate dumping EDM trace to syslog\u000a\u000aSince at the moment we don't have any other means to get the EDM trace\u000afor core-matic reports, dump the trace to syslog, which will be picked\u000aup by the core-matic report generating tool.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "83768dff8b41267caa7326b7459f6545ec85ae0b", "msg" : "gpu: pvr: reinstate dumping EDM trace to syslog", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/deviceclass.c" ], "commitId" : "1c46a54fc430c25e071a94fbbfdf80cd0d221a9a", "timestamp" : 1579843587000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path in PVRSRVRegisterBCDeviceKM\u000a\u000aFixing a free with incorrect size and converting another one to use\u000afree(p, sizeof(*p)) instead of free(p, sizeof(typeof(*p)).\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:27 +0300", "id" : "1c46a54fc430c25e071a94fbbfdf80cd0d221a9a", "msg" : "gpu: pvr: fix error path in PVRSRVRegisterBCDeviceKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/deviceclass.c" ], "commitId" : "81628b84410aaac76cefe8c7f424d890d191f339", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: refactor error path in PVRSRVOpenBCDeviceKM\u000a\u000aNeeded by the next 2 patches fixing the error path.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "81628b84410aaac76cefe8c7f424d890d191f339", "msg" : "gpu: pvr: refactor error path in PVRSRVOpenBCDeviceKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/deviceclass.c" ], "commitId" : "460366175e8c3ce26e65710d289d9249f3938b3e", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix incorrect free size in PVRSRVOpenBCDeviceKM\u000a\u000aAlso remove the always true condition.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "460366175e8c3ce26e65710d289d9249f3938b3e", "msg" : "gpu: pvr: fix incorrect free size in PVRSRVOpenBCDeviceKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/deviceclass.c" ], "commitId" : "95b35b2d7defc26878a502ff3495766cb2263719", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path in PVRSRVOpenBCDeviceKM\u000a\u000aAdd missing frees / ref count rollback.\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "95b35b2d7defc26878a502ff3495766cb2263719", "msg" : "gpu: pvr: fix error path in PVRSRVOpenBCDeviceKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/deviceclass.c" ], "commitId" : "f3aa22e59309b26732f7a227fef31b2e39cf3282", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: refactor error path in PVRSRVOpenDCDeviceKM\u000a\u000aNeeded by the next patch fixing the error path.\u000a\u000aNo functional change.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "f3aa22e59309b26732f7a227fef31b2e39cf3282", "msg" : "gpu: pvr: refactor error path in PVRSRVOpenDCDeviceKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/deviceclass.c" ], "commitId" : "3122e742d429981453307dfa6292c83b907a7020", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path in PVRSRVOpenDCDeviceKM\u000a\u000aAdd missing free.\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "3122e742d429981453307dfa6292c83b907a7020", "msg" : "gpu: pvr: fix error path in PVRSRVOpenDCDeviceKM", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/deviceclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/devicemem.c" ], "commitId" : "39ae43751226eac2392f56dec565efdbb7b3037c", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix PVRSRVWrapExtMemoryKM for user provided physical pages\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "39ae43751226eac2392f56dec565efdbb7b3037c", "msg" : "gpu: pvr: fix PVRSRVWrapExtMemoryKM for user provided physical pages", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/devicemem.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/hash.c" ], "commitId" : "a7c5d59dd756f9f55dbd192e8d4e74646e1fbded", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path in hash _Resize\u000a\u000aAdd missing free in case of _Rehash fails.\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "a7c5d59dd756f9f55dbd192e8d4e74646e1fbded", "msg" : "gpu: pvr: fix error path in hash _Resize", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/hash.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/hash.c" ], "commitId" : "b4619d82bb8baa7f10b5b825a049828198601989", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: optimize mem clear in hash _Resize\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "b4619d82bb8baa7f10b5b825a049828198601989", "msg" : "gpu: pvr: optimize mem clear in hash _Resize", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/hash.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmu.c" ], "commitId" : "8135202b407855eba8e414e3fc56a0a398d7ceba", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path in MMU_Initialise\u000a\u000aAdd missing frees / unmapping at various failure points.\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "8135202b407855eba8e414e3fc56a0a398d7ceba", "msg" : "gpu: pvr: fix error path in MMU_Initialise", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmu.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "3b3ad81d98eb2718f2f356857efdc0b7c3df2074", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix state buffer validation\u000a\u000aThe incorrect comparison size could cause a corrupted buffer info to be\u000aregarded as valid.\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "3b3ad81d98eb2718f2f356857efdc0b7c3df2074", "msg" : "gpu: pvr: fix state buffer validation", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.c" ], "commitId" : "4b1313b047e79949e2eb6c49df100ce949246962", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix error path in SysInitialise\u000a\u000aAdd missing check for the mem allocation result.\u000a\u000aFixes: NB#241787 - missing check of return value of OSReservePhys()\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "4b1313b047e79949e2eb6c49df100ce949246962", "msg" : "gpu: pvr: fix error path in SysInitialise", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/buffer_manager.c", "drivers/gpu/pvr/pvrsrv.c" ], "commitId" : "1c46c6886652e134ca5bb1aff1298c005f1b24cd", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove dead code from the PVRSRVGetFBStatsKM code path\u000a\u000aReported-by: Coverity\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Pauli Nieminen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "1c46c6886652e134ca5bb1aff1298c005f1b24cd", "msg" : "gpu: pvr: remove dead code from the PVRSRVGetFBStatsKM code path", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvrsrv.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/private_data.h", "drivers/gpu/pvr/pvr_bridge_k.c" ], "commitId" : "e5270b272d4e967d8dcf13eb1b4a6d12eedb3f9f", "timestamp" : 1579843588000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: get rid of unnecessary hash lookups for the proc object\u000a\u000aWe already are passed a pointer to the process specific data, so no\u000aneed to do an extra hash lookup just for this purpose.\u000a\u000aNote that this lookup overhead was incured in each IOCTL command.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:28 +0300", "id" : "e5270b272d4e967d8dcf13eb1b4a6d12eedb3f9f", "msg" : "gpu: pvr: get rid of unnecessary hash lookups for the proc object", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/private_data.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/osfunc.h" ], "commitId" : "ee6356412300dd534d37c25a89b155b941b3dde3", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add missing headers to osfunc.h\u000a\u000aHeaders should include all type info used within the header.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "ee6356412300dd534d37c25a89b155b941b3dde3", "msg" : "gpu: pvr: add missing headers to osfunc.h", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/perproc.h", "drivers/gpu/pvr/osfunc.h", "drivers/gpu/pvr/perproc.c", "drivers/gpu/pvr/osfunc.c" ], "commitId" : "c61875903c04bb80fe9085bc6effeb188419e584", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: get proc name during process attach time\u000a\u000aThis will be needed by the upcoming patches where we need a cheap way\u000ato get to the current process name.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "c61875903c04bb80fe9085bc6effeb188419e584", "msg" : "gpu: pvr: get proc name during process attach time", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/perproc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/perproc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "92e9c4053235537781188d78c0da635b5a58bbb3", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: use already existing proc name in pr_err_process info\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "92e9c4053235537781188d78c0da635b5a58bbb3", "msg" : "gpu: pvr: use already existing proc name in pr_err_process info", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_trace_cmd.c", "drivers/gpu/pvr/Kconfig", "drivers/gpu/pvr/Makefile", "drivers/gpu/pvr/pvr_trace_cmd.h" ], "commitId" : "09a5a7581e66391aec784388813f2ac609b527b6", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add command tracing support\u000a\u000aAdd a lightweight tracer to track commands submitted by clients. This\u000acan help for example to debug dead-lock situations where command\u000asynchronization counters form a circular dependency.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "09a5a7581e66391aec784388813f2ac609b527b6", "msg" : "gpu: pvr: add command tracing support", "paths" : [ { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_trace_cmd.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/Makefile" }, { "editType" : "add", "file" : "drivers/gpu/pvr/pvr_trace_cmd.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxtransfer.c", "drivers/gpu/pvr/sgx_bridge_km.h", "drivers/gpu/pvr/sgxkick.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "75dbc9dbc12d8c47465e594271286b5a40608679", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: pass proc info to sgxkick and sgxtransfer\u000a\u000aNeeded by the next patch adding tracing to these commands.\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "75dbc9dbc12d8c47465e594271286b5a40608679", "msg" : "gpu: pvr: pass proc info to sgxkick and sgxtransfer", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxtransfer.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxkick.c", "drivers/gpu/pvr/sgxtransfer.c" ], "commitId" : "fb9734a1a3a2cf61fe5b519b35e23f2159f54903", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add tracing to the SGX kick and transfer commands\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "fb9734a1a3a2cf61fe5b519b35e23f2159f54903", "msg" : "gpu: pvr: add tracing to the SGX kick and transfer commands", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxtransfer.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "5f250fc06c06b37acad578a089d001b2767013d2", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add tracing to the SGX queryblits command\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "5f250fc06c06b37acad578a089d001b2767013d2", "msg" : "gpu: pvr: add tracing to the SGX queryblits command", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "3a66f2b83689426c72e84626ef5ca54a9644fa05", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add tracing for PVR events\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "3a66f2b83689426c72e84626ef5ca54a9644fa05", "msg" : "gpu: pvr: add tracing for PVR events", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "706716c5eb234affb1518664a6eae055668c346e", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add debugfs interface for the command trace\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "706716c5eb234affb1518664a6eae055668c346e", "msg" : "gpu: pvr: add debugfs interface for the command trace", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "1de2321b1fa914724d5ce5b4b45fe292d7bfbd88", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: print the command trace to syslog during HWrec\u000a\u000aSigned-off-by: Imre Deak \u000aReviewed-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "1de2321b1fa914724d5ce5b4b45fe292d7bfbd88", "msg" : "gpu: pvr: print the command trace to syslog during HWrec", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/devicemem.c", "drivers/gpu/pvr/buffer_manager.h", "drivers/gpu/pvr/pvr_bridge_km.h", "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "eb3eaa0048186a324330162e80fa7f50d2dcdc1f", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix memory context refcount problem leading to leaked handle\u000a\u000aAlthough there is an IOCTL interface for creating memory contexts, in\u000areality processes can create only a single context. Subsequent create\u000acommands will return the same context _and_ the same handle, so this\u000aresembles more of an 'open' command, except the somewhat orthodox way of\u000areturning the same handle.\u000a\u000aIn addition there can be kernel only users of the context accounted for\u000aby the current reference count of the context (ui32RefCount).\u000a\u000aRemoving the user handle should happen when the last process opening\u000a(creating) the context calls the close (destroy) command on the handle.\u000aAt the moment the handle is removed only if there are no kernel side or\u000auser space users of the context, which can lead to the handle being\u000aleaked in the following case:\u000a\u000a1. create memory context -> ctx_handle created, ctx_refcount=1\u000a2. create buffer -> ctx_refcount=2\u000a3. destroy memory context -> ctx_refcount=1, ctx_handle not removed\u000a4. destroy buffer -> ctx_refcount=0, ctx_handle not removed\u000a\u000aTo avoid this add a counter tracking the number of opens, so we know\u000awhen to remove the handle.\u000a\u000aFixes: NB#245525 - Return value of pvr_put_ctx is not checked\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "eb3eaa0048186a324330162e80fa7f50d2dcdc1f", "msg" : "gpu: pvr: fix memory context refcount problem leading to leaked handle", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/devicemem.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/buffer_manager.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_km.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "9cb03c14a84e8488d5400613f1d6dbcfa0c91d8e", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: report IOCTL failures\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "9cb03c14a84e8488d5400613f1d6dbcfa0c91d8e", "msg" : "gpu: pvr: report IOCTL failures", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/bridged_sgx_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "a6c8bea094685beb13106d6dc0d387cc624debcb", "timestamp" : 1579843589000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove CommonBridgeInit()\u000a\u000aBy dynamically assigning the function names in the BridgeDispatchTable, an\u000aextra layer of potential errors (when CommonBridgeInit or\u000aSetSGXDispatchTableEntry is not in full sync with the switch statement in\u000abridged_ioctl()) is removed.\u000a\u000a/proc/pvr/bridge_stats now no longer shows IOCTL names and the function\u000athey are supposed to be mapped to. It now shows actual IOCTL numbers, and\u000athe functions called for them (when called at all). It can debated which is\u000amore useful, but the removal of the extra layer of potential errors wins.\u000a\u000aCrucially though, we stop caring about \"holes\" in IOCTL assignment, which\u000amakes it much easier for me to move pdump ioctls to their own range.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:29 +0300", "id" : "a6c8bea094685beb13106d6dc0d387cc624debcb", "msg" : "gpu: pvr: remove CommonBridgeInit()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "3f7daf3020b2c10159751e05b244ea503965e71c", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: move ioctl checking error messagess to pr_err()\u000a\u000aThis way, we get to actually see ioctls failing.\u000a\u000aAlso, a pointless check is removed: the switch statement that follows\u000awill take care of unhandled cases for us anyway (and now complain about\u000athem verbosely).\u000a\u000aFixes: NB#251136 - PVR: fix IOCTL command ID range checking\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "3f7daf3020b2c10159751e05b244ea503965e71c", "msg" : "gpu: pvr: move ioctl checking error messagess to pr_err()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxinit.c", "drivers/gpu/pvr/sgxscript.h" ], "commitId" : "20191acebe6d614a492dfc5f4c6e2a8614e54f1a", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix init script handling for pdump/non-pdump\u000a\u000aA PDUMP enabled build has SGX_INIT_OP_HALT shift one up in the enum, as its\u000aformer position is replaced with SGX_INIT_OP_PDUMP_HW_REG. When kernel and\u000auserspace are out of sync, this leads to rather interesting results since\u000athe init script is run _before_ userspace build options are compared with the\u000akernel build options.\u000a\u000aBy moving SGX_INIT_OP_PDUMP_HW_REG, and not masking it behind #ifdef PDUMP,\u000awe get around this issue for good, without in anyway altering the behavior\u000aof a current non-pdump build.\u000a\u000aSome extra checking of the init script is now also included to catch and warn\u000aabout all possible cases of kernel and userspace being out of sync, with\u000arespect to pdump support (and the new difference in OP_PDUMP_HW_REG). This\u000away, even if we do not make it to the build option checking, we still know\u000awhat went wrong.\u000a\u000aThis patch requires matching userspace, but only when pdump is enabled.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "20191acebe6d614a492dfc5f4c6e2a8614e54f1a", "msg" : "gpu: pvr: fix init script handling for pdump/non-pdump", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxscript.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_bridge.h", "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/sgx_bridge.h" ], "commitId" : "a659c904c5e81604432721b5f51f22db35b2ac4f", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: move pdump ioctls to its own range at 192\u000a\u000aThis removes the shifting of ioctls when enabling pdump builds.\u000a\u000aFixes: NB#247418 - PVR kernel driver IOCTL IDs depend on build configuration\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "a659c904c5e81604432721b5f51f22db35b2ac4f", "msg" : "gpu: pvr: move pdump ioctls to its own range at 192", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgx_bridge.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "9e2f640af9eaafd5dffdbdb662e72283d8c3bb1c", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: add registers file\u000a\u000aSwitches to power state D0 before capturing all registers on open.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "9e2f640af9eaafd5dffdbdb662e72283d8c3bb1c", "msg" : "gpu: pvr: debugfs: add registers file", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "cf2774cda85d77f240da9eaf6686d5391c340106", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: hwrec: fix hwrec_mem_pages type change warnings\u000a\u000aLast minute change of hwrec_mem_pages, from u32 to unsigned long, was not\u000abuild tested due to hwrec_mem dumping now only happening inside\u000aCONFIG_PVR_DEBUG, which was not given a spin before submission.\u000a\u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "cf2774cda85d77f240da9eaf6686d5391c340106", "msg" : "gpu: pvr: hwrec: fix hwrec_mem_pages type change warnings", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c" ], "commitId" : "6eeff2cca6304ffc5b38bdf9e3f5ed3847e56c3f", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix pdumpfs_stream_buffer_clear\u000a\u000aFix tmp[] filling loop so that size == sizeof(tmp) also functions\u000acorrectly.\u000a\u000aSpotted-by: Phil Carmody \u000aSigned-off-by: Luc Verhaegen \u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "6eeff2cca6304ffc5b38bdf9e3f5ed3847e56c3f", "msg" : "gpu: pvr: fix pdumpfs_stream_buffer_clear", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.c", "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "a80b4ef79eb960db51e5a632ba4355dc91a57662", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix missing return value warning when CONFIG_BUG=n\u000a\u000aAlthough the behaviour after these functions return in a BUG() condition\u000ais undefined, we could still make things somewhat more predictable by\u000areturning the same value every time. Also this way we get rid of the\u000awarning.\u000a\u000aSigned-off-by: Imre Deak \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "a80b4ef79eb960db51e5a632ba4355dc91a57662", "msg" : "gpu: pvr: fix missing return value warning when CONFIG_BUG=n", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxutils.c" ], "commitId" : "4455fe0c063d8ed3f82e7953388fb028afc5d4a2", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: V2: Find and fix all incorrect sync counter completion checks\u000a\u000aBugfix for a very rare buffer wrap issue on sync counters\u000athough the use of the wrap safe sync_cnt_after_eq function\u000a\u000aFixes: NB#233069\u000aSigned-off-by: Alex Crowther \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "4455fe0c063d8ed3f82e7953388fb028afc5d4a2", "msg" : "gpu: pvr: V2: Find and fix all incorrect sync counter completion checks", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxkick.c" ], "commitId" : "14b2868593a88d4b137274047b2a603799c4386e", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: kick: check for duplicate src syncs\u000a\u000aWhen duplicate syncs are present, we deadlock; so check and throw an error\u000amessage. Was already fixed in userspace as part of #253237, this now shores\u000aup the kernel too.\u000a\u000aFixes: NB#254225\u000a\u000aSigned-off-by: Luc Verhaegen \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "14b2868593a88d4b137274047b2a603799c4386e", "msg" : "gpu: pvr: kick: check for duplicate src syncs", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxkick.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "bf4578b1b9b841da2a9fcb52bb887b4f498a297a", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add slab.h include in order to make driver build on 2.6.35.3\u000a\u000aForward port to 2.6.35.3\u000a\u000aSigned-off-by: Carsten Munk \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "bf4578b1b9b841da2a9fcb52bb887b4f498a297a", "msg" : "gpu: pvr: add slab.h include in order to make driver build on 2.6.35.3", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/omaplfb_linux.c", "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "b7bd76fa2fcfcbd69ce1d5f6870c4fbe353f0f0c", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "SGX: display.h -> omapdss.h\u000a\u000aFix SGX PVR driver to use correct include with linux 3.0.\u000a\u000aSigned-off-by: Kimmo Jukarainen \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "b7bd76fa2fcfcbd69ce1d5f6870c4fbe353f0f0c", "msg" : "SGX: display.h -> omapdss.h", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/omaplfb_linux.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/omaplfb_displayclass.c" ], "commitId" : "9d4b527f5513b74ba9ebb4254d30cd8b18a4018d", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "SGX: console_sem -> console_lock\u000a\u000aFix SGX PVR driver to use correct function names with linux 3.0.\u000a\u000aSigned-off-by: Kimmo Jukarainen \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "9d4b527f5513b74ba9ebb4254d30cd8b18a4018d", "msg" : "SGX: console_sem -> console_lock", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/omaplfb_displayclass.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "c4cba7985b005bae4197cba644a2074804a08506", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "SGX: clk_notifier_register -> cpufreq_register_notifier\u000a\u000aFix SGX PVR driver to use correct function names and macros with linux 3.0.\u000a\u000aSigned-off-by: Kimmo Jukarainen \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "c4cba7985b005bae4197cba644a2074804a08506", "msg" : "SGX: clk_notifier_register -> cpufreq_register_notifier", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "b75fbccc7ae88dd8cdad5b2260ee23302c42501d", "timestamp" : 1579843590000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "SGX: Add export.h include to pvr_debugfs.c\u000a\u000aSigned-off-by: Jarkko Nikula \u000a", "date" : "2020-01-24 08:26:30 +0300", "id" : "b75fbccc7ae88dd8cdad5b2260ee23302c42501d", "msg" : "SGX: Add export.h include to pvr_debugfs.c", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mm.c" ], "commitId" : "4f478fb306c3dd210b6e57aca96929a86740b7d6", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: Use DMA mapping API for cache invalidation\u000a\u000a___dma_single_dev_to_cpu (and dma_cache_maint before it) is not available\u000aanymore so use standard DMA mapping API methods for cache invalidation.\u000a\u000aSigned-off-by: Jarkko Nikula \u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "4f478fb306c3dd210b6e57aca96929a86740b7d6", "msg" : "gpu: pvr: Use DMA mapping API for cache invalidation", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/Kconfig" ], "commitId" : "6aefe2fe407389542bd6e65014d55c1c8602eb53", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: update config dependency name\u000a\u000aRenaming occured in commit 35b522cfb (\"omapfb/dss: change CONFIG_OMAP*\u000ato CONFIG_FB_OMAP*\").\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "6aefe2fe407389542bd6e65014d55c1c8602eb53", "msg" : "gpu: pvr: update config dependency name", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/Kconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.c", "drivers/gpu/pvr/omaplfb_linux.c" ], "commitId" : "be34424916917aa269ee01919bccb5513648944e", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: use video/omapfb_dss.h header file\u000a\u000aThe header file name was changed after splitting omapdss to omapfb and\u000aomapdrm. This driver uses omapfb.\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "be34424916917aa269ee01919bccb5513648944e", "msg" : "gpu: pvr: use video/omapfb_dss.h header file", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/omaplfb_linux.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/event.c", "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/osfunc.c" ], "commitId" : "29c96f6ee8a02cc5e14e7299f6509a1cc202d530", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove includes for asm/system.h\u000a\u000aThe file was removed in commit 74c4137b2 (\"ARM: 7989/1: Delete\u000aasm/system.h\").\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "29c96f6ee8a02cc5e14e7299f6509a1cc202d530", "msg" : "gpu: pvr: remove includes for asm/system.h", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/event.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_pdumpfs.c", "drivers/gpu/pvr/proc.c", "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "be26975c4f53f681642f2717cb550d828c4f2d5c", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: convert file permissions to numeric\u000a\u000aSee https://lwn.net/Articles/696227/\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "be26975c4f53f681642f2717cb550d828c4f2d5c", "msg" : "gpu: pvr: convert file permissions to numeric", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_pdumpfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/queue.c", "drivers/gpu/pvr/ra.c", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/proc.c", "drivers/gpu/pvr/mm.c", "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/queue.h", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "def1f0b21f5397aacec12d6e24fce371a1ca98c6", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: convert proc files to seq_file interface\u000a\u000aFor good manual on using seq_files interface follow link:\u000ahttps://www.linux.com/learn/kernel-newbie-corner-kernel-debugging-proc-sequence-files-part-3\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "def1f0b21f5397aacec12d6e24fce371a1ca98c6", "msg" : "gpu: pvr: convert proc files to seq_file interface", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/ra.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/queue.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/queue.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/proc.c" ], "commitId" : "93c572a52a76eb32c664c0bf49262c7b7fa6877c", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: proc: use file_inode() macro\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "93c572a52a76eb32c664c0bf49262c7b7fa6877c", "msg" : "gpu: pvr: proc: use file_inode() macro", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/proc.c", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "0511b1e33ba6f06300ffe69e806f413af5617f44", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: update write handlers for proc files\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "0511b1e33ba6f06300ffe69e806f413af5617f44", "msg" : "gpu: pvr: update write handlers for proc files", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/osfunc.c" ], "commitId" : "33039d98ab63478e122d14ffbb103c95909a919c", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: convert timer to use timer_setup()\u000a\u000ainit_timer() interface was removed from kernel since v4.15\u000aFor background check https://lwn.net/Articles/735887/\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "33039d98ab63478e122d14ffbb103c95909a919c", "msg" : "gpu: pvr: convert timer to use timer_setup()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/osfunc.c", "drivers/gpu/pvr/mmap.c" ], "commitId" : "4b141ed94d939f882093a7af76e3b946631913c4", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: kill vma flag VM_RESERVED\u000a\u000aThe flag was removed in commit 314e51b98 (\"mm: kill vma flag VM_RESERVED\u000aand mm->reserved_vm counter\").\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "4b141ed94d939f882093a7af76e3b946631913c4", "msg" : "gpu: pvr: kill vma flag VM_RESERVED", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_bridge_k.c", "drivers/gpu/pvr/osfunc.h", "drivers/gpu/pvr/osfunc.c", "drivers/gpu/pvr/bridged_sgx_bridge.c" ], "commitId" : "871935ae6ce0aad09601d34d45430519ff43559c", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove the first parameter of OSAccessOK()\u000a\u000aThis function follows access_ok() kernel function which was changed by\u000acommit 96d4f267e (\"Remove 'type' argument from access_ok() function\").\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "871935ae6ce0aad09601d34d45430519ff43559c", "msg" : "gpu: pvr: remove the first parameter of OSAccessOK()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_sgx_bridge.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_bridge_k.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/osfunc.c" ], "commitId" : "71bd4331e7b57db33213b38ce7322ba286a8e9eb", "timestamp" : 1579843591000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: page_cache_release() -> put_page()\u000a\u000aThe function was dropped in commit 1fa64f198 (\"mm: drop PAGE_CACHE_* and\u000apage_cache_{get,release} definition\").\u000a\u000aExplanations can be found in commit 09cbfeaf1 (\"mm, fs: get rid of\u000aPAGE_CACHE_* and page_cache_{get,release} macros\").\u000a", "date" : "2020-01-24 08:26:31 +0300", "id" : "71bd4331e7b57db33213b38ce7322ba286a8e9eb", "msg" : "gpu: pvr: page_cache_release() -> put_page()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/osfunc.c" ], "commitId" : "d58c20970bd3d244cfb16c933ca7c52a685db07e", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: update get_user_pages() for changed API\u000a\u000aThe API changes were introduced in the following commits:\u000a\u000a* c12d2da56 (\"mm/gup: Remove the macro overload API migration helpers\u000a from the get_user*() APIs\")\u000a\u000a* 768ae309a (\"mm: replace get_user_pages() write/force parameters with\u000a gup_flags\")\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "d58c20970bd3d244cfb16c933ca7c52a685db07e", "msg" : "gpu: pvr: update get_user_pages() for changed API", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/osfunc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c" ], "commitId" : "7b373ea27f69f33260e9ad7e5004f5d9c9c69229", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove __dev* attributes\u000a\u000aCONFIG_HOTPLUG is gone away as an option. As a result, the __dev*\u000amarkings need to be removed.\u000a\u000aChange forced by commit 54b956b90 (\"Remove __dev* markings from init.h\")\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "7b373ea27f69f33260e9ad7e5004f5d9c9c69229", "msg" : "gpu: pvr: remove __dev* attributes", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c" ], "commitId" : "2858a8a71b8d26d84a8384d7d053e6037d96cc14", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: ignore return value of misc_deregister()\u000a\u000aIt returns nothing since commit f368ed608 (\"char: make misc_deregister a\u000avoid function\").\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "2858a8a71b8d26d84a8384d7d053e6037d96cc14", "msg" : "gpu: pvr: ignore return value of misc_deregister()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/proc.c" ], "commitId" : "9743e5eb1dfa1a3db86238d35b540e3e9383e6c1", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: proc: rename variables\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "9743e5eb1dfa1a3db86238d35b540e3e9383e6c1", "msg" : "gpu: pvr: proc: rename variables", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/proc.h", "drivers/gpu/pvr/pvr_debug.h", "drivers/gpu/pvr/proc.c", "drivers/gpu/pvr/pvr_debug.c" ], "commitId" : "ef226650355bb7815c41a37532e7ac7c4430d0da", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: rewrite proc files write handling\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "ef226650355bb7815c41a37532e7ac7c4430d0da", "msg" : "gpu: pvr: rewrite proc files write handling", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debug.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/proc.c" ], "commitId" : "392ecd7b5a7a9ed5e423e2c77b86994b9a24e8c8", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: don't dereference pointers to proc_dir_entry\u000a\u000aMembers of struct proc_dir_entry are not public anymore. Trying to\u000adereference pointers to the structure produces compilation errors.\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "392ecd7b5a7a9ed5e423e2c77b86994b9a24e8c8", "msg" : "gpu: pvr: don't dereference pointers to proc_dir_entry", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/proc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/bridged_pvr_bridge.c", "drivers/gpu/pvr/dma.h" ], "commitId" : "5f216d91f37d90b43dd9283235f52541690ac82b", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: include dma.h for dmac_map_area()\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "5f216d91f37d90b43dd9283235f52541690ac82b", "msg" : "gpu: pvr: include dma.h for dmac_map_area()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/dma.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/mm/dma-mapping.c" ], "commitId" : "7d39924ec97c26285fb753badc39a0dc1c4bfb34", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: export cache flush management symbols when !MULTI_CACHE\u000a\u000aFixes:\u000aERROR: \"v7_dma_map_area\" [drivers/gpu/pvr/pvrsrvkm.ko] undefined!\u000a\u000aOrigin:\u000ahttps://github.com/RobertCNelson/stable-kernel/commit/b00edc3576118e9ed3e987f9a2a3499b7dd792f5\u000ahttp://www.spinics.net/lists/arm-kernel/msg214633.html\u000a\u000aAuthor: Pantelis Antoniou \u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "7d39924ec97c26285fb753badc39a0dc1c4bfb34", "msg" : "ARM: export cache flush management symbols when !MULTI_CACHE", "paths" : [ { "editType" : "edit", "file" : "arch/arm/mm/dma-mapping.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "413dbda62407c90a1b0f7e91e2dbc7bf1d00574b", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove unused omap_pm_set_min_bus_tput()\u000a\u000aSee commit 44773ba17 (\"ARM: OMAP2+: Drop unused pm-noop\").\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "413dbda62407c90a1b0f7e91e2dbc7bf1d00574b", "msg" : "gpu: pvr: remove unused omap_pm_set_min_bus_tput()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mach-omap2", "drivers/gpu/pvr/sysutils.c" ], "commitId" : "3a965a198177d528f5497fd2b657916fff71a36a", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: make sysutils.o build\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "3a965a198177d528f5497fd2b657916fff71a36a", "msg" : "gpu: pvr: make sysutils.o build", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "add", "file" : "drivers/gpu/pvr/mach-omap2" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sgxpower.c" ], "commitId" : "a77fea353280fa6692dc885f8f3d29dddef97de9", "timestamp" : 1579843592000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add header for cpu_clock()\u000a", "date" : "2020-01-24 08:26:32 +0300", "id" : "a77fea353280fa6692dc885f8f3d29dddef97de9", "msg" : "gpu: pvr: add header for cpu_clock()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "c17fd644071904cc2c9f89df07d4d809dbd45e96", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: events: remove unused do_gettimeofday()\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "c17fd644071904cc2c9f89df07d4d809dbd45e96", "msg" : "gpu: pvr: events: remove unused do_gettimeofday()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_debugfs.c" ], "commitId" : "19a13a0dbbe26829004ab21c46a7c9c444365075", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debugfs: get rid of do_gettimeofday()\u000a\u000aThe function was removed in commit e4b92b108 (\"timekeeping: remove\u000aobsolete time accessors\").\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "19a13a0dbbe26829004ab21c46a7c9c444365075", "msg" : "gpu: pvr: debugfs: get rid of do_gettimeofday()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_events.c" ], "commitId" : "31628630fe09c5fe3a9d13b9333fbe5b1f1fd0ca", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: events: get rid of do_gettimeofday()\u000a\u000aThe function was removed in commit e4b92b108 (\"timekeeping: remove\u000aobsolete time accessors\").\u000a\u000aUse ktime_get_ts64() for monotonic timestamps.\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "31628630fe09c5fe3a9d13b9333fbe5b1f1fd0ca", "msg" : "gpu: pvr: events: get rid of do_gettimeofday()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_events.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.h" ], "commitId" : "155c31f4d6ef340c5c6e22d4f6f26bd986a08c33", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: set proper SGX maximum clock rate\u000a\u000aThe value was taken from Maemo Fremantle kernel driver.\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "155c31f4d6ef340c5c6e22d4f6f26bd986a08c33", "msg" : "gpu: pvr: set proper SGX maximum clock rate", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.c", "drivers/gpu/pvr/module.c" ], "commitId" : "de44246e02c1ac0ea000f0bec57ea6a4517fa155", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: add device tree support\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "de44246e02c1ac0ea000f0bec57ea6a4517fa155", "msg" : "gpu: pvr: add device tree support", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/omap34xx.dtsi" ], "commitId" : "d6d473c180ed7cb3627bd1bf5dd1213684447521", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: dts: omap34xx: add GPU entry\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "d6d473c180ed7cb3627bd1bf5dd1213684447521", "msg" : "ARM: dts: omap34xx: add GPU entry", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/omap34xx.dtsi" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysconfig.c", "drivers/gpu/pvr/sysutils.c" ], "commitId" : "deca375bd717d2820ba79fe789bacff989a73b10", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: update for common clk framework\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "deca375bd717d2820ba79fe789bacff989a73b10", "msg" : "gpu: pvr: update for common clk framework", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysconfig.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "6e459f2b27074b40d0e919c263c8d300ca7c92ca", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove irrelevant clk_set_parent()\u000a\u000aClocks hierarchy is described in device tree file:\u000aarch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "6e459f2b27074b40d0e919c263c8d300ca7c92ca", "msg" : "gpu: pvr: remove irrelevant clk_set_parent()", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "68a2641d8a8f80dae77b1db29f45a610ba9939f6", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: cpufreq_register_notifier -> clk_notifier_register\u000a\u000aRevert commit \"SGX: clk_notifier_register -> cpufreq_register_notifier\"\u000aand update for common clk framework.\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "68a2641d8a8f80dae77b1db29f45a610ba9939f6", "msg" : "gpu: pvr: cpufreq_register_notifier -> clk_notifier_register", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/power.c", "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/bridged_pvr_bridge.c" ], "commitId" : "2b5f3d7eb31f5d3b6d1f0881f14489ff179f940e", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: remove line wraps\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "2b5f3d7eb31f5d3b6d1f0881f14489ff179f940e", "msg" : "gpu: pvr: remove line wraps", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/power.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/bridged_pvr_bridge.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c" ], "commitId" : "518d419afadcb4ed871ff59057146daf8adfee1c", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: set FMODE_UNSIGNED_OFFSET\u000a\u000aSince be83bbf80 (\"mmap: introduce sane default mmap limits\") there's\u000abeen checking of mmap size. Let's assume the client-side driver does\u000ait correctly.\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "518d419afadcb4ed871ff59057146daf8adfee1c", "msg" : "gpu: pvr: set FMODE_UNSIGNED_OFFSET", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/mmap.c", "drivers/gpu/pvr/mm.c" ], "commitId" : "c89135f55e33c0302e65431688375d900b95c84e", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: debug: show memory stats in /proc/slabinfo\u000a\u000aSeparate constructors prevent cache merging.\u000a\u000aThat's how it works:\u000a kmem_cache_create() ->\u000a -> kmem_cache_create_usercopy() ->\u000a -> __kmem_cache_alias() ->\u000a -> find_mergeable()\u000a\u000aIf constructor is NULL, find_mergeable() can return already registered\u000acache for merging. New cache is not created, therefore it's not\u000arepresented in /proc/slabinfo.\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "c89135f55e33c0302e65431688375d900b95c84e", "msg" : "gpu: pvr: debug: show memory stats in /proc/slabinfo", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/mm.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/mmap.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/module.c", "drivers/gpu/pvr/sgxpower.c", "drivers/gpu/pvr/sysutils.c", "drivers/gpu/pvr/syslocal.h", "drivers/gpu/pvr/resman.c", "drivers/gpu/pvr/sgxreset.c" ], "commitId" : "6ffa4935f8fd26bdf12aeeeda06eb1480d36237e", "timestamp" : 1579843593000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: enhance debugging\u000a\u000aAllow additional messages to be logged without enabling \"Extra debugging\u000ainfo\" driver option.\u000a\u000aPort some debugging messages from Maemo Fremantle driver.\u000a", "date" : "2020-01-24 08:26:33 +0300", "id" : "6ffa4935f8fd26bdf12aeeeda06eb1480d36237e", "msg" : "gpu: pvr: enhance debugging", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/module.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/resman.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxpower.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/syslocal.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxreset.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/sysutils.c" ], "commitId" : "bd2947c4ab9502a2006ee3047f190ea86b4886f1", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: minor fix\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "bd2947c4ab9502a2006ee3047f190ea86b4886f1", "msg" : "gpu: pvr: minor fix", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/sysutils.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_trace_cmd.c" ], "commitId" : "a2685f91450bdec53658e206b21d1da988d36309", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: fix CONFIG_PVR_TRACE_CMD=y compilation\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "a2685f91450bdec53658e206b21d1da988d36309", "msg" : "gpu: pvr: fix CONFIG_PVR_TRACE_CMD=y compilation", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_trace_cmd.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_trace_cmd.c" ], "commitId" : "19d110cc8af21462309a19d122b7e2ad573affff", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: trace_cmd: fix empty buffer\u000a\u000aDon't return -ENOMEM when the buffer is empty.\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "19d110cc8af21462309a19d122b7e2ad573affff", "msg" : "gpu: pvr: trace_cmd: fix empty buffer", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_trace_cmd.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/gpu/pvr/pvr_trace_cmd.c", "drivers/gpu/pvr/pvr_debugfs.c", "drivers/gpu/pvr/pvr_trace_cmd.h", "drivers/gpu/pvr/sgxinit.c" ], "commitId" : "bdb751835eeb91263f7c2825c9a92e0d1bace322", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "gpu: pvr: trace_cmd: rewrite with seq_file\u000a\u000aFix system hangs when dumping traces longer than one page.\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "bdb751835eeb91263f7c2825c9a92e0d1bace322", "msg" : "gpu: pvr: trace_cmd: rewrite with seq_file", "paths" : [ { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_trace_cmd.h" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/sgxinit.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_debugfs.c" }, { "editType" : "edit", "file" : "drivers/gpu/pvr/pvr_trace_cmd.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/video/fbdev/omap2/omapfb/dss/dss.h", "include/video/omapfb_dss.h", "drivers/video/fbdev/omap2/omapfb/dss/apply.c" ], "commitId" : "303c81431186f7c1e86da9ea5eba6ead13034a2a", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "OMAP: DSS2: apply patch from Nemo Adaptation\u000a\u000aConsists of the following patches:\u000a\u000aOMAP: DSS2: Fix notifiers when swapping managers\u000aOMAP: DSS2: Rename pending_notify to requested_events\u000aOMAP: DSS2: Implement update notify for manual update display\u000aOMAP: DSS2: Implement support for more notification types.\u000aOMAP: DSS2: use atomic notifiers\u000aOMAP: DSS2: return error values down to caller\u000aOMAP: DSS2: Rename notify_go to notify\u000aOMAP: DSS2: Use GO notifiers for wait_for_go()\u000aOMAP: DSS2: Add GO notifiers\u000aOMAP: DSS2: in_use flag for dss_data\u000aOMAP: DSS2: Keep track whether overlay managers are enabled\u000aOMAP: DSS2: Use spin_lock_irqsave/unlock_irqrestore in apply irq handler\u000a\u000aThe source:\u000ahttp://releases.nemomobile.org/releases/latest/repos/hw/ti/omap3/n900/armv7hl/src/kernel-adaptation-n900-2.6.37-1.4.Nemo.Adaptation.N9xx.src.rpm\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "303c81431186f7c1e86da9ea5eba6ead13034a2a", "msg" : "OMAP: DSS2: apply patch from Nemo Adaptation", "paths" : [ { "editType" : "edit", "file" : "drivers/video/fbdev/omap2/omapfb/dss/apply.c" }, { "editType" : "edit", "file" : "include/video/omapfb_dss.h" }, { "editType" : "edit", "file" : "drivers/video/fbdev/omap2/omapfb/dss/dss.h" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/video/fbdev/omap2/omapfb/dss/apply.c" ], "commitId" : "0edc5f3bd2d859bb666dd978caf5bbde66e918b4", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "OMAP: DSS2: fix state checking\u000a\u000adssdev->state is not synchronized with dssdev->dst->state, so we need to\u000ause the latter explicitly\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "0edc5f3bd2d859bb666dd978caf5bbde66e918b4", "msg" : "OMAP: DSS2: fix state checking", "paths" : [ { "editType" : "edit", "file" : "drivers/video/fbdev/omap2/omapfb/dss/apply.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/touchscreen/tsc200x-core.c" ], "commitId" : "3345caef0c18872aac4329f5ab3870b954716d80", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Input: tsc200x-core - add 'disable' sysfs attribute\u000a\u000aWe need 'disable' attribute to be able to control the power consumption\u000aof touchscreen in user space.\u000a\u000aThis reverts commit 5cb81d19b. Thanks Pali Rohár.\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "3345caef0c18872aac4329f5ab3870b954716d80", "msg" : "Input: tsc200x-core - add 'disable' sysfs attribute", "paths" : [ { "editType" : "edit", "file" : "drivers/input/touchscreen/tsc200x-core.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/omap3-n900.dts" ], "commitId" : "f649f05cdb5e9088d2994892c0ef03795e2b3cc8", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: dts: n900: remove rx51-battery\u000a\u000aN900 has bq27200 chip, which provides much better\u000afunctionality when exposing battery properties.\u000a\u000aNo need to confuse userspace with two battery devices\u000aexposed by the kernel at the same time.\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "f649f05cdb5e9088d2994892c0ef03795e2b3cc8", "msg" : "ARM: dts: n900: remove rx51-battery", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/omap3-n900.dts" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/omap3-n900.dts" ], "commitId" : "80bd324a3e83595c0be6b573d77b92e360d23f18", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: dts: n900: increase charge current limit to 950mA\u000a\u000aThat was default in Maemo Fremantle\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "80bd324a3e83595c0be6b573d77b92e360d23f18", "msg" : "ARM: dts: n900: increase charge current limit to 950mA", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/omap3-n900.dts" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/omap3-n900.dts" ], "commitId" : "9ce9bb2557208bb347909823d4710c9f93f65bf0", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: dts: n900: ignore mmc1 card detect gpio\u000a\u000aAllow the device to boot from external MMC with back cover removed.\u000a\u000aSee https://github.com/maemo-leste/bugtracker/issues/225\u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "9ce9bb2557208bb347909823d4710c9f93f65bf0", "msg" : "ARM: dts: n900: ignore mmc1 card detect gpio", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/omap3-n900.dts" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/phy/ti/phy-twl4030-usb.c" ], "commitId" : "949a796f05f6aab2f13d1504b9453a2dea03f2df", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "phy: phy-twl4030-usb: Fix cable state handling\u000a\u000aWith the recent regulator changes I noticed new warnings on doing rmmod of\u000aphy-twl4030-usb:\u000a\u000aWARNING: CPU: 0 PID: 1080 at drivers/regulator/core.c:2046 _regulator_put\u000a...\u000a\u000aTurns out we can currently miss disconnect at least for cases where status\u000ais 0 and linkstat is 0. And in that case doing rmmod phy-twl4030-usb will\u000aproduce the regulator_put() warning.\u000a\u000aThis is because the missed disconnect causes unbalanced PM runtime calls\u000aand the regulators will be on exit.\u000a\u000aLet's fix the issue by using an atomic flag for the cable state to make\u000asure that PM runtime won't get out of sync with the cable state. That\u000away we can also simplify the code a bit.\u000a\u000aNote that we can also drop the old comments, those relate to issues that\u000athe battery charger driver and musb driver is dealing with rather than\u000athe USB PHY driver.\u000a\u000aCc: NeilBrown \u000aSigned-off-by: Tony Lindgren \u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "949a796f05f6aab2f13d1504b9453a2dea03f2df", "msg" : "phy: phy-twl4030-usb: Fix cable state handling", "paths" : [ { "editType" : "edit", "file" : "drivers/phy/ti/phy-twl4030-usb.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/usb/musb/omap2430.c" ], "commitId" : "898a43115b9ce7fcd8346eb0e8fddad76bfa2d40", "timestamp" : 1579843594000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "usb: musb: omap2430: Add support for idling phy when musb is idle\u000a\u000aI noticed that musb is blocking core retention for omap4 unlike for\u000aomap3. This is because for omap3 we have phy-twl4030-usb implement\u000ait's own PM runtime to handle errata \"VUSB3V1 VBUS overvoltage\u000adebouncer not working when the PHY is powered down\". That is done\u000ain order to keep the USB PHY powered when phy-twl4030-usb is loaded.\u000a\u000aFor the other USB PHYs, we need to enable and disable the PHY based on\u000amusb PM runtime. With the session bit based PM runtime for musb core,\u000awe can now idle the USB PHY always when musb is idle.\u000a\u000aNote that adding these calls will not affect the twl4030 driver\u000aas it's phy functions will just query the PHY state without powering\u000athe PHY on or off.\u000a\u000aSigned-off-by: Tony Lindgren \u000a", "date" : "2020-01-24 08:26:34 +0300", "id" : "898a43115b9ce7fcd8346eb0e8fddad76bfa2d40", "msg" : "usb: musb: omap2430: Add support for idling phy when musb is idle", "paths" : [ { "editType" : "edit", "file" : "drivers/usb/musb/omap2430.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/input/keyboard/twl4030_keypad.c" ], "commitId" : "f1df290b4af3801d314782930cb34f0e7945b2be", "timestamp" : 1579845618000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Input: twl4030-keypad - omit ghost state detection\u000a\u000aSome key combinations cannot be uniquely identified because of the\u000anature of the hardware keyboard. However, these combinations can still\u000abe useful if keyboard mapping is configured properly.\u000a\u000ahttp://wiki.maemo.org/N900_Hardware_Subsystems#Keyboard\u000ahttps://ec2.sheer.us/~enyc/n900-kbd/n900-kbd-README.txt\u000a", "date" : "2020-01-24 09:00:18 +0300", "id" : "f1df290b4af3801d314782930cb34f0e7945b2be", "msg" : "Input: twl4030-keypad - omit ghost state detection", "paths" : [ { "editType" : "edit", "file" : "drivers/input/keyboard/twl4030_keypad.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/boot/dts/omap3-n900.dts" ], "commitId" : "b30255858d086bf8c1ded4034a6368080b634260", "timestamp" : 1580762306000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: OMAP: DTS: N900: fix onenand timings\u000a\u000aCommit a758f50f10cf (\"mtd: onenand: omap2: Configure driver from DT\")\u000astarted using DT specified timings for GPMC, and as a result the\u000aOneNAND stopped working on N900 as we had wrong values in the DT.\u000aFix by updating the values to bootloader timings that have been tested\u000ato be working on Nokia N900 with OneNAND manufacturers: Samsung,\u000aNumonyx.\u000a\u000aFixes: a758f50f10cf (\"mtd: onenand: omap2: Configure driver from DT\")\u000aSigned-off-by: Arthur Demchenkov \u000a", "date" : "2020-02-03 23:38:26 +0300", "id" : "b30255858d086bf8c1ded4034a6368080b634260", "msg" : "ARM: OMAP: DTS: N900: fix onenand timings", "paths" : [ { "editType" : "edit", "file" : "arch/arm/boot/dts/omap3-n900.dts" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/regulator/twl-regulator.c" ], "commitId" : "8de6836ab833f41a2bd5574ffcf3edfcf584dfec", "timestamp" : 1582656725000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "regulator: twl: Constify regulator_ops\u000a\u000aThese regulator_ops variables never need to be modified, make them const so\u000acompiler can put them to .rodata.\u000a\u000aSigned-off-by: Axel Lin \u000aSigned-off-by: Mark Brown \u000a", "date" : "2020-02-25 21:52:05 +0300", "id" : "8de6836ab833f41a2bd5574ffcf3edfcf584dfec", "msg" : "regulator: twl: Constify regulator_ops", "paths" : [ { "editType" : "edit", "file" : "drivers/regulator/twl-regulator.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/regulator/twl-regulator.c" ], "commitId" : "8ce61c60c8386e972abd61e00a34be43cc474a22", "timestamp" : 1582656725000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "regulator: twl: voltage lists for vdd1/2 on twl4030\u000a\u000a_opp_supported_by_regulators() wrongly ignored errors from\u000aregulator_is_supported_voltage(), so it considered errors as\u000asuccess. Since\u000acommit 498209445124 (\"regulator: core: simplify return value on suported_voltage\")\u000aregulator_is_supported_voltage() returns a real boolean, so\u000aerrors make _opp_supported_by_regulators() return false.\u000a\u000aThat reveals a problem with the declaration of the VDD1/2\u000aregulators on twl4030.\u000aThe VDD1/VDD2 regulators on twl4030 are neither defined with\u000avoltage lists nor with the continuous flag set, so\u000aregulator_is_supported_voltage() returns false and an error\u000abefore above mentioned commit (which was considered success)\u000aThe result is that after the above mentioned commit cpufreq\u000adoes not work properly e.g. dm3730.\u000a\u000a[ 2.490997] core: _opp_supported_by_regulators: OPP minuV: 1012500 maxuV: 1012500, not supported by regulator\u000a[ 2.501617] cpu cpu0: _opp_add: OPP not supported by regulators (300000000)\u000a[ 2.509246] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1200000, not supported by regulator\u000a[ 2.519775] cpu cpu0: _opp_add: OPP not supported by regulators (600000000)\u000a[ 2.527313] core: _opp_supported_by_regulators: OPP minuV: 1325000 maxuV: 1325000, not supported by regulator\u000a[ 2.537750] cpu cpu0: _opp_add: OPP not supported by regulators (800000000)\u000a\u000aThe patch fixes declaration of VDD1/2 regulators by\u000aadding proper voltage lists.\u000a\u000aFixes: 498209445124 (\"regulator: core: simplify return value on suported_voltage\")\u000aCc: stable@vger.kernel.org\u000aSigned-off-by: Andreas Kemnade \u000aTested-by: Adam Ford #logicpd-torpedo-37xx-devkit\u000aLink: https://lore.kernel.org/r/20190814214319.24087-1-andreas@kemnade.info\u000aSigned-off-by: Mark Brown \u000a", "date" : "2020-02-25 21:52:05 +0300", "id" : "8ce61c60c8386e972abd61e00a34be43cc474a22", "msg" : "regulator: twl: voltage lists for vdd1/2 on twl4030", "paths" : [ { "editType" : "edit", "file" : "drivers/regulator/twl-regulator.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/platform/omap3isp/ispccdc.c" ], "commitId" : "7f596aab429598502ac2e7a167042762472112ea", "timestamp" : 1583665961000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "n900: camera: magic bit makes it work\u000a\u000aPavel Machek wrote:\u000a\u000a\"For camera, I need this patch, otherwise image is deformed (square\u000ainstead of proper shape). Unfortunately, I don't have good idea why\u000athat's the case.\"\u000a\u000ahttps://lists.dyne.org/lurker/message/20200307.114526.7b4baeda.en.html\u000a", "date" : "2020-03-08 14:12:41 +0300", "id" : "7f596aab429598502ac2e7a167042762472112ea", "msg" : "n900: camera: magic bit makes it work", "paths" : [ { "editType" : "edit", "file" : "drivers/media/platform/omap3isp/ispccdc.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "drivers/media/i2c/et8ek8/et8ek8_driver.c" ], "commitId" : "1e38cadefca946690f1c2b2a7153b3c3174dc754", "timestamp" : 1583763940000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "et8ek8: Support for EXPOSURE_ABSOLUTE\u000a\u000aTo do a good job taking photos, userland needs to be able to query/set\u000aexposure in absolute units. (As scene gets darker, exposure time\u000ashould be increased to cca 1/100 second -- based on scene type -- then\u000asensitivity should be stepped up to maximum reasonable value, only\u000athen time should be increased again). This patch provides neccessary\u000asupport.\u000a\u000aSigned-off-by: Pavel Machek \u000a", "date" : "2020-03-09 17:25:40 +0300", "id" : "1e38cadefca946690f1c2b2a7153b3c3174dc754", "msg" : "et8ek8: Support for EXPOSURE_ABSOLUTE", "paths" : [ { "editType" : "edit", "file" : "drivers/media/i2c/et8ek8/et8ek8_driver.c" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/omap2plus_defconfig", "arch/arm/configs/n900_defconfig" ], "commitId" : "307112cef6e1255d999d2c3986936067186444b9", "timestamp" : 1583764002000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: rename omap2plus_defconfig\u000a", "date" : "2020-03-09 17:26:42 +0300", "id" : "307112cef6e1255d999d2c3986936067186444b9", "msg" : "ARM: n900_defconfig: rename omap2plus_defconfig", "paths" : [ { "editType" : "add", "file" : "arch/arm/configs/n900_defconfig" }, { "editType" : "delete", "file" : "arch/arm/configs/omap2plus_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "de4f4a47b56c73518c8b356238180ac1a0a142fa", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: update for current kernel\u000a\u000aThe config file was updated using these commands:\u000amake ARCH=arm n900_defconfig\u000amake ARCH=arm savedefconfig\u000amv defconfig arch/arm/configs/n900_defconfig\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "de4f4a47b56c73518c8b356238180ac1a0a142fa", "msg" : "ARM: n900_defconfig: update for current kernel", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "aa163463110f8b8dbd14dcdb381bfac18c792435", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable lock debugging\u000a\u000aThese options are supposed to be used by kernel hackers who debug\u000adrivers. Not recommended to be included in distro kernels.\u000a\u000aWARNING: enabling CONFIG_DEBUG_LOCK_ALLOC causes LCD to be unusable.\u000aThe reason is not yet established.\u000a\u000aKernel hacking --->\u000a Lock Debugging (spinlocks, mutexes, etc...) --->\u000a [ ] Lock debugging: prove locking correctness [CONFIG_PROVE_LOCKING]\u000a [ ] RT Mutex debugging, deadlock detection [CONFIG_DEBUG_RT_MUTEXES]\u000a [ ] Spinlock and rw-lock debugging: basic checks [CONFIG_DEBUG_SPINLOCK]\u000a [ ] Mutex debugging: basic checks [CONFIG_DEBUG_MUTEXES]\u000a [ ] Wait/wound mutex debugging: Slowpath testing [CONFIG_DEBUG_WW_MUTEX_SLOWPATH]\u000a [ ] Lock debugging: detect incorrect freeing ... [CONFIG_DEBUG_LOCK_ALLOC]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "aa163463110f8b8dbd14dcdb381bfac18c792435", "msg" : "ARM: n900_defconfig: disable lock debugging", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "ac3966c3bca0393c33dfe750eba79a216eba7c1e", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable SMP\u000a\u000aWe only have one CPU.\u000a\u000aKernel Features --->\u000a [ ] Symmetric Multi-Processing [CONFIG_SMP]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "ac3966c3bca0393c33dfe750eba79a216eba7c1e", "msg" : "ARM: n900_defconfig: disable SMP", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "270d461030f19722d2272dc47da29744dfbb38f4", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable DRM\u000a\u000aCurrent PowerVR SGX driver is tied to omapfb.\u000a\u000aDevice Drivers --->\u000a Graphics support --->\u000a < > Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "270d461030f19722d2272dc47da29744dfbb38f4", "msg" : "ARM: n900_defconfig: disable DRM", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "7bbe12340a6cafb25ad32338ad5b07f111e7552a", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: make display work\u000a\u000aDevice Drivers --->\u000a Graphics support --->\u000a Frame buffer Devices --->\u000a <*> OMAP2+ frame buffer support ---> [CONFIG_FB_OMAP2]\u000a [ ] DPI support [CONFIG_FB_OMAP2_DSS_DPI]\u000a [ ] HDMI support for OMAP4 [CONFIG_FB_OMAP4_DSS_HDMI]\u000a [*] SDI support [CONFIG_FB_OMAP2_DSS_SDI]\u000a OMAPFB Panel and Encoder Drivers --->\u000a <*> Analog TV Connector [CONFIG_FB_OMAP2_CONNECTOR_ANALOG_TV]\u000a <*> ACX565AKM Panel [CONFIG_FB_OMAP2_PANEL_SONY_ACX565AKM]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "7bbe12340a6cafb25ad32338ad5b07f111e7552a", "msg" : "ARM: n900_defconfig: make display work", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "e43b813290bffe6e4ca1572fd37c8bd900e81d74", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable PowerVR SGX\u000a\u000aDevice Drivers --->\u000a Graphics support --->\u000a PowerVR Services [PVR]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "e43b813290bffe6e4ca1572fd37c8bd900e81d74", "msg" : "ARM: n900_defconfig: enable PowerVR SGX", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "0549b8aff9453754c8e96baf0e9d8ec16063b98e", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable WiFi\u000a\u000aDevice Drivers --->\u000a Network device support --->\u000a Wireless LAN --->\u000a [ ] ADMtek devices [CONFIG_WLAN_VENDOR_ADMTEK]\u000a [ ] Atheros/Qualcomm devices [CONFIG_WLAN_VENDOR_ATH]\u000a [ ] Atmel devices [CONFIG_WLAN_VENDOR_ATMEL]\u000a [ ] Broadcom devices [CONFIG_WLAN_VENDOR_BROADCOM]\u000a [ ] Cisco devices [CONFIG_WLAN_VENDOR_CISCO]\u000a [ ] Intel devices [CONFIG_WLAN_VENDOR_INTEL]\u000a [ ] Intersil devices [CONFIG_WLAN_VENDOR_INTERSIL]\u000a [ ] Marvell devices [CONFIG_WLAN_VENDOR_MARVELL]\u000a [ ] MediaTek devices [CONFIG_WLAN_VENDOR_MEDIATEK]\u000a [ ] Ralink devices [CONFIG_WLAN_VENDOR_RALINK]\u000a [ ] Realtek devices [CONFIG_WLAN_VENDOR_REALTEK]\u000a [ ] Redpine Signals Inc devices [CONFIG_WLAN_VENDOR_RSI]\u000a [ ] STMicroelectronics devices [CONFIG_WLAN_VENDOR_ST]\u000a TI wl1251 driver support [CONFIG_WL1251]\u000a TI wl1251 SPI support [CONFIG_WL1251_SPI]\u000a < > TI wl12xx support [CONFIG_WL12XX]\u000a < > TI wl18xx support [CONFIG_WL18XX]\u000a < > TI wlcore support [CONFIG_WLCORE]\u000a [ ] ZyDAS devices [CONFIG_WLAN_VENDOR_ZYDAS]\u000a [ ] Quantenna wireless cards support [CONFIG_WLAN_VENDOR_QUANTENNA]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "0549b8aff9453754c8e96baf0e9d8ec16063b98e", "msg" : "ARM: n900_defconfig: enable WiFi", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "49238c90eb78dd8890b1bd4e6ebc947a2b582dd5", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: set kernel compression mode to LZ4\u000a\u000aThis one is the fastest.\u000a\u000aGeneral setup --->\u000a Kernel compression mode (LZ4) [CONFIG_KERNEL_LZ4]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "49238c90eb78dd8890b1bd4e6ebc947a2b582dd5", "msg" : "ARM: n900_defconfig: set kernel compression mode to LZ4", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "826282c93845a2ca272bf16a1c79fd05c116b383", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: don't store .config in kernel\u000a\u000aThree reasons:\u000a- we are on low memory;\u000a- it's default for current debian kernel config;\u000a- there's no need to store config file in the kernel\u000a\u000aGeneral setup --->\u000a < > Kernel .config support [CONFIG_IKCONFIG]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "826282c93845a2ca272bf16a1c79fd05c116b383", "msg" : "ARM: n900_defconfig: don't store .config in kernel", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "0a56562059aaa5f93b455104208bb8cfce78bd72", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: increase kernel log buffer size\u000a\u000aChanged from 64KB to 256KB.\u000a\u000aGeneral setup --->\u000a (18) Kernel log buffer size (16 => 64KB, 17 => 128KB) [CONFIG_LOG_BUF_SHIFT]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "0a56562059aaa5f93b455104208bb8cfce78bd72", "msg" : "ARM: n900_defconfig: increase kernel log buffer size", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "24cc9ee6cb6076b16341aff6a84404acd1e9f7fc", "timestamp" : 1583764003000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable swap controller (cgroup)\u000a\u000a- Reduce kernel memory usage.\u000a- This option is disabled in Debian kernels as well.\u000a- Can be enabled at runtime.\u000a\u000aGeneral setup --->\u000a Control Group support --->\u000a [ ] Swap controller enabled by default [CONFIG_MEMCG_SWAP_ENABLED]\u000a", "date" : "2020-03-09 17:26:43 +0300", "id" : "24cc9ee6cb6076b16341aff6a84404acd1e9f7fc", "msg" : "ARM: n900_defconfig: disable swap controller (cgroup)", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "7b3a6674e7dc9bb0ec5bcbf634d9eea0359a032c", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: remove obsolete sysfs syscall\u000a\u000a- No longer supported in libc.\u000a- This option is disabled in Debian kernel.\u000a\u000aGeneral setup --->\u000a Configure standard kernel features (expert users) --->\u000a [ ] Sysfs syscall support [CONFIG_SYSFS_SYSCALL]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "7b3a6674e7dc9bb0ec5bcbf634d9eea0359a032c", "msg" : "ARM: n900_defconfig: remove obsolete sysfs syscall", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "c0a758ba2b946a1b2c3dd49ef0da41e44063d75b", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: select SLUB as slab allocator\u000a\u000aThis one is stated to be the default by kernel documentation.\u000a\u000aCheck this link for some background:\u000ahttps://stackoverflow.com/questions/15470560/what-to-choose-between-slab-and-slub-allocator-in-linux-kernel\u000a\u000aGeneral setup --->\u000a Choose SLAB allocator (SLUB (Unqueued Allocator)) [CONFIG_SLUB]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "c0a758ba2b946a1b2c3dd49ef0da41e44063d75b", "msg" : "ARM: n900_defconfig: select SLUB as slab allocator", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "35f9daea1da1aee25a3ef97804af11fd36f7093c", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable ARMv6\u000a\u000aNokia N900 is based on ARMv7.\u000a\u000aSystem Type --->\u000a Multiple platform selection --->\u000a [ ] ARMv6 based platforms (ARM11) [ARCH_MULTI_V6]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "35f9daea1da1aee25a3ef97804af11fd36f7093c", "msg" : "ARM: n900_defconfig: disable ARMv6", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "fa77d6a881cd53919a0203f237599a529f8734bb", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: remove excessive systems\u000a\u000aWe only need TI OMAP3 here.\u000a\u000aSystem Type --->\u000a TI OMAP/AM/DM/DRA Family --->\u000a [ ] TI OMAP4 [ARCH_OMAP4]\u000a [ ] TI OMAP5 [SOC_OMAP5]\u000a [ ] TI AM33XX [SOC_AM33XX]\u000a [ ] TI AM43x [SOC_AM43XX]\u000a [ ] TI DRA7XX [SOC_DRA7XX]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "fa77d6a881cd53919a0203f237599a529f8734bb", "msg" : "ARM: n900_defconfig: remove excessive systems", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "7832dd37490fc2f1b04876e007ad4f3d1bee75d4", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: clean up SoC specific features\u000a\u000aN900 is based on OMAP3430.\u000a\u000aSystem Type --->\u000a TI OMAP/AM/DM/DRA Family --->\u000a TI OMAP2/3/4 Specific Features --->\u000a [ ] TI81XX support [SOC_TI81XX]\u000a [ ] OMAP3517/ AM3517 EVM board [MACH_OMAP3517EVM]\u000a [ ] OMAP3 Pandora [MACH_OMAP3_PANDORA]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "7832dd37490fc2f1b04876e007ad4f3d1bee75d4", "msg" : "ARM: n900_defconfig: clean up SoC specific features", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "4d84aad178e1e5d9eebaaba5b6329adfc5f5f852", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: clean up common clock framework\u000a\u000aDevice Drivers --->\u000a Common Clock Framework --->\u000a < > Clock driver for dm814x ADPLL [CONFIG_COMMON_CLK_TI_ADPLL]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "4d84aad178e1e5d9eebaaba5b6329adfc5f5f852", "msg" : "ARM: n900_defconfig: clean up common clock framework", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "ec8c7d05a48c464b981b1e9dc1874eaae369b55a", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable extraneous erratas\u000a\u000aN900 is based on Cortex-A8. Erratas below are for Cortex-A9.\u000a\u000aSystem Type --->\u000a [ ] ARM errata: TLBIASIDIS and TLBIMVAIS ... [CONFIG_ARM_ERRATA_720789]\u000a [ ] ARM errata: possible faulty MMU trans... [CONFIG_ARM_ERRATA_754322]\u000a [ ] ARM errata: A data cache maintenance ... [CONFIG_ARM_ERRATA_775420]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "ec8c7d05a48c464b981b1e9dc1874eaae369b55a", "msg" : "ARM: n900_defconfig: disable extraneous erratas", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "d9ef4187e91d498a629400f28bb71b057be62362", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable L2x0 PrimeCell\u000a\u000aI didn't find mentions of this controller to be used in OMAP3430/ARMv7.\u000aAnd its \"Selected by\" section doesn't show anything interesting for us.\u000a\u000aSystem Type --->\u000a [ ] Enable the L2x0 outer cache controller [CONFIG_CACHE_L2X0]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "d9ef4187e91d498a629400f28bb71b057be62362", "msg" : "ARM: n900_defconfig: disable L2x0 PrimeCell", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "9d9949c44413c96e349634e82e89b7fef344b650", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable PCI\u000a\u000aObviously N900 doesn't have a PCI controller.\u000a\u000aDevice Drivers --->\u000a [ ] PCI support [CONFIG_PCI]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "9d9949c44413c96e349634e82e89b7fef344b650", "msg" : "ARM: n900_defconfig: disable PCI", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "a2e0f663044a0e02f9c74c2fb450a3a281cccce9", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: set preemption model to \"Desktop\"\u000a\u000aIt should give good performance and responsibility at the same time.\u000a\u000aGeneral setup --->\u000a Preemption Model (Voluntary Kernel Preemption (Desktop)) [CONFIG_PREEMPT_VOLUNTARY]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "a2e0f663044a0e02f9c74c2fb450a3a281cccce9", "msg" : "ARM: n900_defconfig: set preemption model to \"Desktop\"", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "d6ff1db1f8391aea348ae4542d63503c9c0e1931", "timestamp" : 1583764004000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: optimize kernel for size\u000a\u000aGeneral setup --->\u000a Compiler optimization level (Optimize for size) [CONFIG_CC_OPTIMIZE_FOR_SIZE]\u000a", "date" : "2020-03-09 17:26:44 +0300", "id" : "d6ff1db1f8391aea348ae4542d63503c9c0e1931", "msg" : "ARM: n900_defconfig: optimize kernel for size", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "ded312987ed59a699812f85d70ca18ad764985ec", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: build in Thumb-2 mode\u000a\u000aThis should optimize kernel size and performance using ARMv7 thumb2\u000ainstructions set.\u000a\u000aKernel Features --->\u000a [*] Compile the kernel in Thumb-2 mode [CONFIG_THUMB2_KERNEL]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "ded312987ed59a699812f85d70ca18ad764985ec", "msg" : "ARM: n900_defconfig: build in Thumb-2 mode", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "9044ecc492b86713433fe261d10deb045e78082b", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable Thumb-2 bug workaround\u000a\u000aSeems like the bug was fixed in 2011.\u000aCheck https://bugs.launchpad.net/binutils-linaro/+bug/725126\u000a\u000aKernel Features --->\u000a [ ] Work around buggy Thumb-2 short branch relocations in gas\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "9044ecc492b86713433fe261d10deb045e78082b", "msg" : "ARM: n900_defconfig: disable Thumb-2 bug workaround", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "db91c47242081d196976b4373e4fb9590ad89c40", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: set timer frequency to 200 Hz\u000a\u000aThis is default in Debian kernel.\u000a\u000aKernel Features --->\u000a Timer frequency (200 Hz) [HZ_200]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "db91c47242081d196976b4373e4fb9590ad89c40", "msg" : "ARM: n900_defconfig: set timer frequency to 200 Hz", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "178bb3682838641a1bf888932f49d91e855d2707", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable highmem interaction code\u000a\u000aWe only have 256M of RAM (and some swap possible).\u000aThe code for interaction with 4G+ memory is excessive.\u000a\u000aKernel Features --->\u000a [ ] Allocate 2nd-level pagetables from highmem [CONFIG_HIGHPTE]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "178bb3682838641a1bf888932f49d91e855d2707", "msg" : "ARM: n900_defconfig: disable highmem interaction code", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "89c9dc5335070dd1a0488c7816d005374d6be5bb", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable ATAGS\u000a\u000aWe use device tree blob attached to the kernel for booting.\u000aRemove ATAGS support to reduce the kernel code.\u000a\u000aBoot options --->\u000a [ ] Support for the traditional ATAGS boot data passing [CONFIG_ATAGS]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "89c9dc5335070dd1a0488c7816d005374d6be5bb", "msg" : "ARM: n900_defconfig: disable ATAGS", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "7023f3fe84d81ecf0699ac6e1f40b5203676fc37", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable SATA/PATA\u000a\u000aN900 doesn't have such controller.\u000a\u000aDevice Drivers --->\u000a < > Serial ATA and Parallel ATA drivers (libata) [CONFIG_ATA]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "7023f3fe84d81ecf0699ac6e1f40b5203676fc37", "msg" : "ARM: n900_defconfig: disable SATA/PATA", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "c59732afd486f38b5d4569a49fc12fbbf067ebae", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: clean up 'Power supply'\u000a\u000aDevice Drivers --->\u000a Power supply class support --->\u000a < > Motorola CPCAP PMIC battery driver [CONFIG_BATTERY_CPCAP]\u000a < > BQ27xxx HDQ support [CONFIG_BATTERY_BQ27XXX_HDQ]\u000a < > CPCAP PMIC Charger Driver [CONFIG_CHARGER_CPCAP]\u000a < > OMAP TWL4030 BCI charger driver [CONFIG_CHARGER_TWL4030]\u000a < > TI BQ24190 battery charger driver [CONFIG_CHARGER_BQ24190]\u000a < > TI BQ24735 battery charger support [CONFIG_CHARGER_BQ24735]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "c59732afd486f38b5d4569a49fc12fbbf067ebae", "msg" : "ARM: n900_defconfig: clean up 'Power supply'", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "f358a1a16a56c6318938eedccabae22537bd3f0e", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: clean up 'Keyboards'\u000a\u000aDevice Drivers --->\u000a Input device support --->\u000a Keyboards --->\u000a < > AT keyboard [CONFIG_KEYBOARD_ATKBD]\u000a < > GPIO driven matrix keypad support [CONFIG_KEYBOARD_MATRIX]\u000a < > TI OMAP4+ keypad support [CONFIG_KEYBOARD_OMAP4]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "f358a1a16a56c6318938eedccabae22537bd3f0e", "msg" : "ARM: n900_defconfig: clean up 'Keyboards'", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "f27e54f8756c5bbc1c48d021927ac4cea5f39798", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: clean up 'Touchscreens'\u000a\u000aDevice Drivers --->\u000a Input device support --->\u000a Touchscreens --->\u000a < > ADS7846/TSC2046/AD7873 ... [CONFIG_TOUCHSCREEN_ADS7846]\u000a < > Atmel mXT I2C Touchscreen [CONFIG_TOUCHSCREEN_ATMEL_MXT]\u000a < > EDT FocalTech FT5x06 I2C ... [CONFIG_TOUCHSCREEN_EDT_FT5X06]\u000a < > TI Touchscreen Interface [CONFIG_TOUCHSCREEN_TI_AM335X_TSC]\u000a < > PIXCIR I2C touchscreens [CONFIG_TOUCHSCREEN_PIXCIR]\u000a < > TSC2004 based touchscreens [CONFIG_TOUCHSCREEN_TSC2004]\u000a < > TSC2007 based touchscreens [CONFIG_TOUCHSCREEN_TSC2007]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "f27e54f8756c5bbc1c48d021927ac4cea5f39798", "msg" : "ARM: n900_defconfig: clean up 'Touchscreens'", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "7f6a87dc6362e0d1a8b0690167345523f1f312d1", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: clean up 'Real Time Clock'\u000a\u000aDevice Drivers --->\u000a Real Time Clock --->\u000a < > Dallas/Maxim DS1307/37/38/39/40/41, ... [CONFIG_RTC_DRV_DS1307]\u000a < > ST M41T62/65/M41T80/81/82/83/84/85/87 ... [CONFIG_RTC_DRV_M41T80]\u000a < > TI Palmas RTC driver [CONFIG_RTC_DRV_PALMAS]\u000a < > TI OMAP Real Time Clock [CONFIG_RTC_DRV_OMAP]\u000a < > Motorola CPCAP RTC [CONFIG_RTC_DRV_CPCAP]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "7f6a87dc6362e0d1a8b0690167345523f1f312d1", "msg" : "ARM: n900_defconfig: clean up 'Real Time Clock'", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "5056fce6d9243f3c15744db2d2216ed42f37811b", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: compile RTC driver in kernel\u000a\u000aThis prevents wrong timestamps on early kernel boot\u000atime and removes the need to have a service/udev rule\u000arunning 'hwclock --hctosys'. It also allows to avoid\u000aunnecessary fsck runs at boot time.\u000a\u000aWithout this change, kernel options RTC_HCTOSYS=y and\u000aRTC_HCTOSYS_DEVICE=rtc0 have no effect except errors\u000ain the logs.\u000a\u000aDevice Drivers --->\u000a Real Time Clock --->\u000a <*> TI TWL4030/TWL5030/TWL6030/TPS659x0 [CONFIG_RTC_DRV_TWL4030]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "5056fce6d9243f3c15744db2d2216ed42f37811b", "msg" : "ARM: n900_defconfig: compile RTC driver in kernel", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "77dd998372ca8e3181db0b472cebae8e10e22141", "timestamp" : 1583764005000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: compile watchdog drivers in kernel\u000a\u000aThis should prevent occasional shut downs on slow booting.\u000a\u000aDevice Drivers --->\u000a Watchdog Timer Support --->\u000a <*> OMAP Watchdog [CONFIG_OMAP_WATCHDOG]\u000a <*> TWL4030 Watchdog [CONFIG_TWL4030_WATCHDOG]\u000a", "date" : "2020-03-09 17:26:45 +0300", "id" : "77dd998372ca8e3181db0b472cebae8e10e22141", "msg" : "ARM: n900_defconfig: compile watchdog drivers in kernel", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "2c141e4012bba087a93207fddbc6dacc55eb506a", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable ZRAM\u000a\u000aMemory Management options --->\u000a Memory allocator for compressed pages [CONFIG_ZSMALLOC]\u000a [*] Use page table mapping to access object ... [CONFIG_PGTABLE_MAPPING]\u000aDevice Drivers --->\u000a Block devices --->\u000a Compressed RAM block device support [CONFIG_ZRAM]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "2c141e4012bba087a93207fddbc6dacc55eb506a", "msg" : "ARM: n900_defconfig: enable ZRAM", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "fe26194f33630fcb53e7469f9b6962f1806b9d1a", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable ZSWAP\u000a\u000aUsage: https://wiki.archlinux.org/index.php/zswap\u000a\u000aMemory Management options --->\u000a [*] Enable frontswap to cache swap pages if tmem is ... [CONFIG_FRONTSWAP]\u000a [*] Compressed cache for swap pages (EXPERIMENTAL) [CONFIG_ZSWAP]\u000a Low (Up to 2x) density storage for compressed pages [CONFIG_ZBUD]\u000a Up to 3x density storage for compressed pages [CONFIG_Z3FOLD]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "fe26194f33630fcb53e7469f9b6962f1806b9d1a", "msg" : "ARM: n900_defconfig: enable ZSWAP", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "464d22d2d958b01fb0aaec7f7dbaec9fecf5ded1", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: change cmdline 'console' param\u000a\u000aSet console=tty1 for default kernel command line. This allows boot\u000amessages to be displayed when kernel parameters are omitted. I.e.\u000aif you do \"run sdboot\" from U-Boot console.\u000a\u000aBoot options --->\u000a Default kernel command string [CONFIG_CMDLINE]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "464d22d2d958b01fb0aaec7f7dbaec9fecf5ded1", "msg" : "ARM: n900_defconfig: change cmdline 'console' param", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "164ff496aeb54f92a7fb829a4a1dc1251f504418", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: add common filesystems\u000a\u000aFile systems --->\u000a Reiserfs support [CONFIG_REISERFS_FS]\u000a XFS filesystem support [CONFIG_XFS_FS]\u000a Btrfs filesystem support [CONFIG_BTRFS_FS]\u000a FUSE (Filesystem in Userspace) support [CONFIG_FUSE_FS]\u000a Overlay filesystem support [CONFIG_OVERLAY_FS]\u000a CD-ROM/DVD Filesystems --->\u000a ISO 9660 CDROM file system support [CONFIG_ISO9660_FS]\u000a UDF file system support [CONFIG_UDF_FS]\u000a DOS/FAT/NT Filesystems --->\u000a MSDOS fs support [CONFIG_MSDOS_FS]\u000a VFAT (Windows-95) fs support [CONFIG_VFAT_FS]\u000a NTFS file system support [CONFIG_NTFS_FS]\u000a Miscellaneous filesystems --->\u000a Journalling Flash File System v2 ... [CONFIG_JFFS2_FS]\u000a Compressed ROM file system support ... [CONFIG_CRAMFS]\u000a SquashFS 4.0 - Squashed file system ... [CONFIG_SQUASHFS]\u000a Network File Systems --->\u000a NFS client support [CONFIG_NFS_FS]\u000a SMB3 and CIFS support (advanced ... ) [CONFIG_CIFS]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "164ff496aeb54f92a7fb829a4a1dc1251f504418", "msg" : "ARM: n900_defconfig: add common filesystems", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "30242cade8adae51ed4cb26a70c2efcfdb1d3783", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: filesystems native language\u000a\u000aFile systems --->\u000a DOS/FAT/NT Filesystems --->\u000a (ascii) Default iocharset for FAT [CONFIG_FAT_DEFAULT_IOCHARSET]\u000a [*] Enable FAT UTF-8 option by default [CONFIG_FAT_DEFAULT_UTF8]\u000a Native language support --->\u000a (utf8) Default NLS Option [CONFIG_NLS_DEFAULT]\u000a Codepage 437 (United States, Canada) [CONFIG_NLS_CODEPAGE_437]\u000a ASCII (United States) [CONFIG_NLS_ASCII]\u000a NLS ISO 8859-1 (Latin 1; ...) [CONFIG_NLS_ISO8859_1]\u000a NLS UTF-8 [CONFIG_NLS_UTF8]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "30242cade8adae51ed4cb26a70c2efcfdb1d3783", "msg" : "ARM: n900_defconfig: filesystems native language", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "5fe9de845c9c679d0f6a88e587ec298df0134bdb", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: systemd related options\u000a\u000aThe source: https://github.com/systemd/systemd/blob/master/README\u000a\u000aGeneral setup --->\u000a Control Group support --->\u000a CPU controller --->\u000a [ ] Group scheduling for SCHED_RR/FIFO [CONFIG_RT_GROUP_SCHED]\u000a Namespaces support --->\u000a [*] User namespace [CONFIG_USER_NS]\u000a [*] Checkpoint/restore support [CONFIG_CHECKPOINT_RESTORE]\u000aEnable the block layer --->\u000a [*] Block layer SG support v4 [CONFIG_BLK_DEV_BSG]\u000aDevice Drivers --->\u000a Generic Driver Options --->\u000a [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]\u000aFile systems --->\u000a [*] Ext4 POSIX Access Control Lists [CONFIG_EXT4_FS_POSIX_ACL]\u000a [*] XFS POSIX ACL support [CONFIG_XFS_POSIX_ACL]\u000a [*] Btrfs POSIX Access Control Lists [CONFIG_BTRFS_FS_POSIX_ACL]\u000a {*} Kernel automounter support (...) [AUTOFS_FS]\u000aCryptographic API --->\u000a {*} HMAC support [CONFIG_CRYPTO_HMAC]\u000a {*} SHA224 and SHA256 digest algorithm [CONFIG_CRYPTO_SHA256]\u000a <*> User-space interface for hash algorithms [CONFIG_CRYPTO_USER_API_HASH]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "5fe9de845c9c679d0f6a88e587ec298df0134bdb", "msg" : "ARM: n900_defconfig: systemd related options", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "1a4cb27d081f43f4ee19ba8d6bd490feabcef10d", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: PowerTOP related options\u000a\u000aThe source: https://wiki.gentoo.org/wiki/PowerTOP\u000a\u000aCPU Power Management --->\u000a CPU Frequency scaling --->\u000a [*] CPU frequency transition statistics [CONFIG_CPU_FREQ_STAT]\u000aKernel hacking --->\u000a Tracers --->\u000a [*] Support for tracing block IO actions [CONFIG_BLK_DEV_IO_TRACE]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "1a4cb27d081f43f4ee19ba8d6bd490feabcef10d", "msg" : "ARM: n900_defconfig: PowerTOP related options", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "fdbbf4814591b23211e313902c4550946d42f570", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable ethernet drivers\u000a\u000aThis removes some drivers compiled in kernel.\u000aSo the kernel will occupy less memory.\u000a\u000aDevice Drivers --->\u000a Network device support --->\u000a [ ] Ethernet driver support [CONFIG_ETHERNET]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "fdbbf4814591b23211e313902c4550946d42f570", "msg" : "ARM: n900_defconfig: disable ethernet drivers", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "c558858888156b95b29adc81cb81b17a282a7d59", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: compile PHY devices drivers as modules\u000a\u000aRemove drivers from kernel, so the kernel will occupy less memory.\u000a\u000aDevice Drivers --->\u000a Network device support --->\u000a {M} PHY Device support and infrastructure [CONFIG_PHYLIB]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "c558858888156b95b29adc81cb81b17a282a7d59", "msg" : "ARM: n900_defconfig: compile PHY devices drivers as modules", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "d87960dc70ed16ab638cbf41e75b9b936b1aab5c", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable nokia modem\u000a\u000aDevice Drivers --->\u000a HSI support --->\u000a CMT speech [CONFIG_CMT_SPEECH]\u000a Nokia Modem [CONFIG_NOKIA_MODEM]\u000a HSI/SSI character driver [CONFIG_HSI_CHAR]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "d87960dc70ed16ab638cbf41e75b9b936b1aab5c", "msg" : "ARM: n900_defconfig: enable nokia modem", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "57c0caea7f17844eb03b8bef8800a85dd7126e3c", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable accelerometer\u000a\u000aDevice Drivers --->\u000a Misc devices --->\u000a STMicroeletronics LIS3LV02Dx three-axis ... [CONFIG_SENSORS_LIS3_I2C]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "57c0caea7f17844eb03b8bef8800a85dd7126e3c", "msg" : "ARM: n900_defconfig: enable accelerometer", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "25c134eb1435e1322fce5b7811c9fc59b755364f", "timestamp" : 1583764006000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: change compiler debug options\u000a\u000aSet these options in similar way to Debian kernel.\u000a\u000aKernel hacking --->\u000a Compile-time checks and compiler options --->\u000a [ ] Produce split debuginfo in .dwo files [CONFIG_DEBUG_INFO_SPLIT]\u000a [ ] Generate dwarf4 debuginfo [CONFIG_DEBUG_INFO_DWARF4]\u000a [*] Strip assembler-generated symbols during link [CONFIG_STRIP_ASM_SYMS]\u000a", "date" : "2020-03-09 17:26:46 +0300", "id" : "25c134eb1435e1322fce5b7811c9fc59b755364f", "msg" : "ARM: n900_defconfig: change compiler debug options", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "a9f54182fc70882da539d8db5157932ccf8d2acd", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable initramfs/initrd\u000a\u000aWe don't use initrd for booting, disable it to save memory.\u000a\u000aGeneral setup --->\u000a [ ] Initial RAM filesystem and RAM disk ... [CONFIG_BLK_DEV_INITRD]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "a9f54182fc70882da539d8db5157932ccf8d2acd", "msg" : "ARM: n900_defconfig: disable initramfs/initrd", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "f1191ce521a964972b5f4ab7ae5975dc60ebe0b4", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable crypto accelerators\u000a\u000aCryptographic API --->\u000a Hardware crypto devices --->\u000a Support for OMAP crypto HW accelerators [CONFIG_CRYPTO_DEV_OMAP]\u000a Support for OMAP MD5/SHA1/SHA2 hw ... [CONFIG_CRYPTO_DEV_OMAP_SHAM]\u000a Support for OMAP AES hw engine [CONFIG_CRYPTO_DEV_OMAP_AES]\u000a Support for OMAP DES/3DES hw engine [CONFIG_CRYPTO_DEV_OMAP_DES]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "f1191ce521a964972b5f4ab7ae5975dc60ebe0b4", "msg" : "ARM: n900_defconfig: enable crypto accelerators", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "b1e864816817bc252957fd671321c5a70fbd86db", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable thermal driver\u000a\u000aDevice Drivers --->\u000a Generic Thermal sysfs driver --->\u000a Texas Instruments thermal drivers --->\u000a [*] Texas Instruments OMAP3 thermal support [CONFIG_OMAP3_THERMAL]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "b1e864816817bc252957fd671321c5a70fbd86db", "msg" : "ARM: n900_defconfig: enable thermal driver", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "a36401674c7b2d681e788e6ad32bf65b45b9c910", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable light sensor\u000a\u000aDevice Drivers --->\u000a Industrial I/O support --->\u000a Light sensors --->\u000a TAOS TSL2560, TSL2561, TSL2562 and TSL2563 ... [CONFIG_SENSORS_TSL2563]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "a36401674c7b2d681e788e6ad32bf65b45b9c910", "msg" : "ARM: n900_defconfig: enable light sensor", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "0b023bb34c9cf0516dab4d513953f29197a75c5f", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: analog to digital converters\u000a\u000aDevice Drivers --->\u000a Industrial I/O support --->\u000a Analog to digital converters --->\u000a < > Motorola CPCAP PMIC ADC driver [CONFIG_CPCAP_ADC]\u000a < > TI's AM335X ADC driver [CONFIG_TI_AM335X_ADC]\u000a TWL4030 MADC (Monitoring A/D Converter) [CONFIG_TWL4030_MADC]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "0b023bb34c9cf0516dab4d513953f29197a75c5f", "msg" : "ARM: n900_defconfig: analog to digital converters", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "ac97173df7320559265980fd92730345cf5df68f", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable radio driver\u000a\u000aDevice Drivers --->\u000a Multimedia support --->\u000a [*] AM/FM radio receivers/transmitters support [CONFIG_MEDIA_RADIO_SUPPORT]\u000a Radio Adapters --->\u000a Silicon Labs Si4713 FM Radio with RDS ... [CONFIG_RADIO_SI4713]\u000a Silicon Labs Si4713 FM Radio ... [CONFIG_PLATFORM_SI4713]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "ac97173df7320559265980fd92730345cf5df68f", "msg" : "ARM: n900_defconfig: enable radio driver", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "2e16ae1cdb63dc7608fef159b3f7a0ebd51f0bc2", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable bluetooth radio\u000a\u000aDevice Drivers --->\u000a [*] Staging drivers ---> [CONFIG_STAGING]\u000a [*] Media staging drivers ---> [CONFIG_STAGING_MEDIA]\u000a Broadcom BCM2048 FM Radio Receiver support [CONFIG_I2C_BCM2048]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "2e16ae1cdb63dc7608fef159b3f7a0ebd51f0bc2", "msg" : "ARM: n900_defconfig: enable bluetooth radio", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "0f4dd8cd9c7f4a239ffea48173090ef2aa6eff07", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: disable TV tuners\u000a\u000aDevice Drivers --->\u000a Multimedia support --->\u000a Customize TV tuners --->\u000a [ DISABLE ALL ]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "0f4dd8cd9c7f4a239ffea48173090ef2aa6eff07", "msg" : "ARM: n900_defconfig: disable TV tuners", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "da918345dab1d6bb0464c911b051fb023d333491", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable front LED\u000a\u000aDevice Drivers --->\u000a LED Support --->\u000a LED Support for TI/National LP5523/55231 LED ... [CONFIG_LEDS_LP5523]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "da918345dab1d6bb0464c911b051fb023d333491", "msg" : "ARM: n900_defconfig: enable front LED", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "c0a83e248c0ff4872069863e2e088efbb40c6592", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable flash LED\u000a\u000aDevice Drivers --->\u000a Multimedia support --->\u000a I2C Encoders, decoders, sensors and other helper chips --->\u000a ADP1653 flash support [CONFIG_VIDEO_ADP1653]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "c0a83e248c0ff4872069863e2e088efbb40c6592", "msg" : "ARM: n900_defconfig: enable flash LED", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "b8a844523040cce4aeb4279e6632428858f9da7f", "timestamp" : 1583764007000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable front webcam\u000a\u000aDevice Drivers --->\u000a Multimedia support --->\u000a I2C Encoders, decoders, sensors and other helper chips --->\u000a SMIA++/SMIA sensor support [CONFIG_VIDEO_SMIAPP]\u000a", "date" : "2020-03-09 17:26:47 +0300", "id" : "b8a844523040cce4aeb4279e6632428858f9da7f", "msg" : "ARM: n900_defconfig: enable front webcam", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "4b85766d5ebc21cf14469c5cc2dfc81e3a7013fa", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable back camera\u000a\u000aDevice Drivers --->\u000a Multimedia support --->\u000a I2C Encoders, decoders, sensors and other helper chips --->\u000a AD5820 lens voice coil support [CONFIG_VIDEO_AD5820]\u000a ET8EK8 camera sensor support [CONFIG_VIDEO_ET8EK8]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "4b85766d5ebc21cf14469c5cc2dfc81e3a7013fa", "msg" : "ARM: n900_defconfig: enable back camera", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "debc10ea7551de24e64735d7bbe2e63a25f22642", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: expose thermal sensors as hwmon device\u000a\u000aDevice Drivers --->\u000a <*> Hardware Monitoring support [CONFIG_HWMON]\u000a Generic Thermal sysfs driver --->\u000a [*] Expose thermal sensors as hwmon device [CONFIG_THERMAL_HWMON]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "debc10ea7551de24e64735d7bbe2e63a25f22642", "msg" : "ARM: n900_defconfig: expose thermal sensors as hwmon device", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "9f8f14dbb897c8cc019023a6fa51ae63c73af055", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: compile keyboard driver into kernel\u000a\u000aDevice Drivers --->\u000a Input device support --->\u000a Keyboards --->\u000a <*> TI TWL4030/TWL5030/TPS659x0 keypad support [CONFIG_KEYBOARD_TWL4030]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "9f8f14dbb897c8cc019023a6fa51ae63c73af055", "msg" : "ARM: n900_defconfig: compile keyboard driver into kernel", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "733f2a9148bf09a4bcbf7c3c626682e48ee48a83", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable in-kernel .config\u000a\u000aReason: asked by Wizzup in #maemo-leste IRC channel.\u000a\u000aThis partially reverts commit \"ARM: n900_defconfig: don't store .config\u000ain kernel\"\u000a\u000aGeneral setup --->\u000a Kernel .config support [CONFIG_IKCONFIG]\u000a [*] Enable access to .config through ... [CONFIG_IKCONFIG_PROC]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "733f2a9148bf09a4bcbf7c3c626682e48ee48a83", "msg" : "ARM: n900_defconfig: enable in-kernel .config", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "8bb66d38235f5fe6b8e56700aafd4a46e5f58dea", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable vibrator support\u000a\u000aDevice Drivers --->\u000a Input device support --->\u000a Miscellaneous devices --->\u000a Support for TWL4030 Vibrator [INPUT_TWL4030_VIBRA]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "8bb66d38235f5fe6b8e56700aafd4a46e5f58dea", "msg" : "ARM: n900_defconfig: enable vibrator support", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "2cf8583c9b67a8fc077ec4c1952c14d50b6fe66e", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable NAT/masq networking\u000a\u000ahttps://github.com/maemo-leste/bugtracker/issues/248\u000a\u000aNetworking support --->\u000a Networking options --->\u000a Network packet filtering framework (Netfilter) --->\u000a Core Netfilter Configuration --->\u000a Netfilter connection tracking support [CONFIG_NF_CONNTRACK]\u000a IP: Netfilter Configuration --->\u000a IP tables support (required for ...) [CONFIG_IP_NF_IPTABLES]\u000a iptables NAT support [CONFIG_IP_NF_NAT]\u000a MASQUERADE target support [CONFIG_IP_NF_TARGET_MASQUERADE]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "2cf8583c9b67a8fc077ec4c1952c14d50b6fe66e", "msg" : "ARM: n900_defconfig: enable NAT/masq networking", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "d0d4b10093d874dfd247ec8653d3a9b11a6c5828", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable TUN/TAP driver\u000a\u000ahttps://github.com/maemo-leste/bugtracker/issues/295\u000a\u000aDevice Drivers --->\u000a Network device support --->\u000a Universal TUN/TAP device driver support [CONFIG_TUN]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "d0d4b10093d874dfd247ec8653d3a9b11a6c5828", "msg" : "ARM: n900_defconfig: enable TUN/TAP driver", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "5deaa57d3f389a7d9ea0d59463cb008f4d9fa3d0", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable F2FS support\u000a\u000aSee: https://github.com/maemo-leste/bugtracker/issues/313\u000a\u000aFile systems --->\u000a <*> F2FS filesystem support [CONFIG_F2FS_FS]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "5deaa57d3f389a7d9ea0d59463cb008f4d9fa3d0", "msg" : "ARM: n900_defconfig: enable F2FS support", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "3b09673032d6bead9d19eba633180cb864da949e", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: compile in btrfs driver\u000a\u000aReason: asked by Wizzup.\u000aSee: https://github.com/maemo-leste/bugtracker/issues/313\u000a\u000aFile systems --->\u000a <*> Btrfs filesystem support [CONFIG_BTRFS_FS]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "3b09673032d6bead9d19eba633180cb864da949e", "msg" : "ARM: n900_defconfig: compile in btrfs driver", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "4b521294714505abe190478ad90e13d82081779c", "timestamp" : 1583764008000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: enable filesystem capabilities\u000a\u000aThis fixes error:\u000aFailed to set capabilities on file (Operation not supported)\u000a\u000ahttp://tinkering-is-fun.blogspot.com/2015/06/filesystem-capabilities-kernel.html\u000a\u000aFile systems --->\u000a [*] Ext4 Security Labels [CONFIG_EXT4_FS_SECURITY]\u000a [*] F2FS Security Labels [CONFIG_F2FS_FS_SECURITY]\u000a", "date" : "2020-03-09 17:26:48 +0300", "id" : "4b521294714505abe190478ad90e13d82081779c", "msg" : "ARM: n900_defconfig: enable filesystem capabilities", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "arch/arm/configs/n900_defconfig" ], "commitId" : "54e6ec7686e9d92aa0df491e6bfb6b207595ceb3", "timestamp" : 1585168052000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "ARM: n900_defconfig: add iotop utility support\u000a\u000aGeneral setup --->\u000a CPU/Task time and stats accounting --->\u000a [*] Export task/process statistics through netlink [CONFIG_TASKSTATS]\u000a [*] Enable per-task delay accounting [CONFIG_TASK_DELAY_ACCT]\u000a [*] Enable extended accounting over taskstats [CONFIG_TASK_XACCT]\u000a [*] Enable per-task storage I/O accounting [CONFIG_TASK_IO_ACCOUNTING]\u000a", "date" : "2020-03-25 23:27:32 +0300", "id" : "54e6ec7686e9d92aa0df491e6bfb6b207595ceb3", "msg" : "ARM: n900_defconfig: add iotop utility support", "paths" : [ { "editType" : "edit", "file" : "arch/arm/configs/n900_defconfig" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "scripts/package/Makefile" ], "commitId" : "c297bdae5e5b49cd571beadb979d435be69010b7", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: preserve /debian/ on 'make clean'\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "c297bdae5e5b49cd571beadb979d435be69010b7", "msg" : "debian: preserve /debian/ on 'make clean'", "paths" : [ { "editType" : "edit", "file" : "scripts/package/Makefile" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ ".gitignore" ], "commitId" : "b016999c516eed488aead04fe904470522c698f1", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: remove /debian/ from .gitignore\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "b016999c516eed488aead04fe904470522c698f1", "msg" : "debian: remove /debian/ from .gitignore", "paths" : [ { "editType" : "edit", "file" : ".gitignore" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/postinst.in", "debian/rules", "debian/changelog", "debian/README", "debian/compat", "debian/source/format", "debian/clean", "debian/copyright", "debian/control" ], "commitId" : "75720c392fb73dd211b1b0c67109da42560149fa", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: fill /debian/ directory with content\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "75720c392fb73dd211b1b0c67109da42560149fa", "msg" : "debian: fill /debian/ directory with content", "paths" : [ { "editType" : "add", "file" : "debian/postinst.in" }, { "editType" : "add", "file" : "debian/source/format" }, { "editType" : "add", "file" : "debian/changelog" }, { "editType" : "add", "file" : "debian/clean" }, { "editType" : "add", "file" : "debian/rules" }, { "editType" : "add", "file" : "debian/control" }, { "editType" : "add", "file" : "debian/compat" }, { "editType" : "add", "file" : "debian/copyright" }, { "editType" : "add", "file" : "debian/README" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/postinst.in", "scripts/package/builddeb", "debian/rules", "debian/control" ], "commitId" : "0ccb5d063c2a96490f666580747456fdb9ff1666", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: use linux native scripts for packaging\u000a\u000aPackages added:\u000a - linux-image-n900-dbg\u000a - linux-headers-n900\u000a\u000aThis should allow to build kernel modules out of tree.\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "0ccb5d063c2a96490f666580747456fdb9ff1666", "msg" : "debian: use linux native scripts for packaging", "paths" : [ { "editType" : "edit", "file" : "debian/control" }, { "editType" : "delete", "file" : "debian/postinst.in" }, { "editType" : "edit", "file" : "scripts/package/builddeb" }, { "editType" : "edit", "file" : "debian/rules" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "fceafc194e03d4abfec1e60e0d71f838e9d4ddbf", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.0.5-1)\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "fceafc194e03d4abfec1e60e0d71f838e9d4ddbf", "msg" : "Update debian/changelog (5.0.5-1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/control", "debian/rules" ], "commitId" : "4b014849c3c8f8eaa7a2a83155716026d28fce69", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: fix linux-headers-n900 when crossbuilding\u000a\u000aBuild kernel related binaries in target architecture format after cross\u000abuilding. This allows to run DKMS on target device successfully.\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "4b014849c3c8f8eaa7a2a83155716026d28fce69", "msg" : "debian: fix linux-headers-n900 when crossbuilding", "paths" : [ { "editType" : "edit", "file" : "debian/rules" }, { "editType" : "edit", "file" : "debian/control" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/gbp.conf" ], "commitId" : "68e2b2a255f986e5312cbedfa5c0f38efa3c8291", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: add gbp.conf needed by jenkins-debian-glue\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "68e2b2a255f986e5312cbedfa5c0f38efa3c8291", "msg" : "debian: add gbp.conf needed by jenkins-debian-glue", "paths" : [ { "editType" : "add", "file" : "debian/gbp.conf" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/README" ], "commitId" : "706c8f6675d518fc8ad93e35667cd38f536cf6ba", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: update README for default config management\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "706c8f6675d518fc8ad93e35667cd38f536cf6ba", "msg" : "debian: update README for default config management", "paths" : [ { "editType" : "edit", "file" : "debian/README" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/rules" ], "commitId" : "b7c27196a35b8b7304bbccf35a17eb648fc01680", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: rules: fix warning: 'build-arch' is missing\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "b7c27196a35b8b7304bbccf35a17eb648fc01680", "msg" : "debian: rules: fix warning: 'build-arch' is missing", "paths" : [ { "editType" : "edit", "file" : "debian/rules" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "acf2c2c39ce5f03a2000ae1247813b5e3b281bbc", "timestamp" : 1585168142000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.0.5-2)\u000a", "date" : "2020-03-25 23:29:02 +0300", "id" : "acf2c2c39ce5f03a2000ae1247813b5e3b281bbc", "msg" : "Update debian/changelog (5.0.5-2)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "78637b946c76ff9e95aa5b50f41ae0f5350260b8", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.0.5-3)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "78637b946c76ff9e95aa5b50f41ae0f5350260b8", "msg" : "Update debian/changelog (5.0.5-3)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "307bd2b2f999ef4490333718d0998ff7841f3401", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.0.7-1)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "307bd2b2f999ef4490333718d0998ff7841f3401", "msg" : "Update debian/changelog (5.0.7-1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "6d868278cc53e969e372c29e4d129bff12f0cb9d", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.0.9-1)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "6d868278cc53e969e372c29e4d129bff12f0cb9d", "msg" : "Update debian/changelog (5.0.9-1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "2711e61de953c4b8d88a5578b0b791ceb83200b9", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.0.14-1)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "2711e61de953c4b8d88a5578b0b791ceb83200b9", "msg" : "Update debian/changelog (5.0.14-1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "f987a2c95baff7ec7dfe83cef73819eea0fa268f", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1-1)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "f987a2c95baff7ec7dfe83cef73819eea0fa268f", "msg" : "Update debian/changelog (5.1-1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "b93098e664fa8f86c9793b8603a79ce839fa0516", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21-1)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "b93098e664fa8f86c9793b8603a79ce839fa0516", "msg" : "Update debian/changelog (5.1.21-1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/README" ], "commitId" : "e21ff994622cfd7b1d56124d6248476b62f24d5f", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian/README: add instructions for cross building\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "e21ff994622cfd7b1d56124d6248476b62f24d5f", "msg" : "debian/README: add instructions for cross building", "paths" : [ { "editType" : "edit", "file" : "debian/README" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/rules" ], "commitId" : "f960ecd26a53c71728eaba7f062907d1e2caa177", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian/rules: replace variables with proper names\u000a\u000aSee dpkg-architecture(1) and\u000ahttps://wiki.debian.org/CrossBuildPackagingGuidelines\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "f960ecd26a53c71728eaba7f062907d1e2caa177", "msg" : "debian/rules: replace variables with proper names", "paths" : [ { "editType" : "edit", "file" : "debian/rules" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/source/format" ], "commitId" : "e9c6815bc7d109c7ee8825e237aea46e5e97625b", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "debian: change source format to '3.0 (native)'\u000a\u000aWe don't use quilt patches. Having '3.0 (quilt)' can confuse users and\u000abuild system when additional patches/configuration changes are applied\u000ato the same kernel version.\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "e9c6815bc7d109c7ee8825e237aea46e5e97625b", "msg" : "debian: change source format to '3.0 (native)'", "paths" : [ { "editType" : "edit", "file" : "debian/source/format" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "90ed2dcb3abf083171802262bcec92a8bae707d8", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21.1)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "90ed2dcb3abf083171802262bcec92a8bae707d8", "msg" : "Update debian/changelog (5.1.21.1)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "96481d83e810e2aa9560add09cb6128a9a5c3322", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21.2)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "96481d83e810e2aa9560add09cb6128a9a5c3322", "msg" : "Update debian/changelog (5.1.21.2)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "41c830d233956fa73e019adc26db404319d28bfd", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21.3)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "41c830d233956fa73e019adc26db404319d28bfd", "msg" : "Update debian/changelog (5.1.21.3)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "cde12cb9d46ea2439703527f9f257344d906f12f", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21.4)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "cde12cb9d46ea2439703527f9f257344d906f12f", "msg" : "Update debian/changelog (5.1.21.4)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "ae4fe9ebccfae0a84587278e0a616086d7cf0ccc", "timestamp" : 1585168143000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21.5)\u000a", "date" : "2020-03-25 23:29:03 +0300", "id" : "ae4fe9ebccfae0a84587278e0a616086d7cf0ccc", "msg" : "Update debian/changelog (5.1.21.5)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "984583c461d40eaaf7621533d2b772af5bf94bc9", "timestamp" : 1585168144000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." }, "authorEmail" : "spinal.by@gmail.com", "comment" : "Update debian/changelog (5.1.21.6)\u000a", "date" : "2020-03-25 23:29:04 +0300", "id" : "984583c461d40eaaf7621533d2b772af5bf94bc9", "msg" : "Update debian/changelog (5.1.21.6)", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "1bd2a54bb5168408e3a952831265b7fc6f7566c8", "timestamp" : 1593105153000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/parazyd", "fullName" : "Ivan J." }, "authorEmail" : "parazyd@dyne.org", "comment" : "Update debian/changelog.\u000a", "date" : "2020-06-25 19:12:33 +0200", "id" : "1bd2a54bb5168408e3a952831265b7fc6f7566c8", "msg" : "Update debian/changelog.", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/control" ], "commitId" : "a8c995741acdac18e7f6d9185a59003889b56360", "timestamp" : 1593107433000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/parazyd", "fullName" : "Ivan J." }, "authorEmail" : "parazyd@dyne.org", "comment" : "Fixup\u000a", "date" : "2020-06-25 19:50:33 +0200", "id" : "a8c995741acdac18e7f6d9185a59003889b56360", "msg" : "Fixup", "paths" : [ { "editType" : "edit", "file" : "debian/control" } ] }, { "_class" : "hudson.plugins.git.GitChangeSet", "affectedPaths" : [ "debian/changelog" ], "commitId" : "16171baac6109885bedb2b52e0377c36f75449df", "timestamp" : 1593110213000, "author" : { "absoluteUrl" : "https://phoenix.maemo.org/user/parazyd", "fullName" : "Ivan J." }, "authorEmail" : "parazyd@dyne.org", "comment" : "Update debian/changelog.\u000a", "date" : "2020-06-25 20:36:53 +0200", "id" : "16171baac6109885bedb2b52e0377c36f75449df", "msg" : "Update debian/changelog.", "paths" : [ { "editType" : "edit", "file" : "debian/changelog" } ] } ], "kind" : "git" }, "culprits" : [ { "absoluteUrl" : "https://phoenix.maemo.org/user/gregkh", "fullName" : "gregkh" }, { "absoluteUrl" : "https://phoenix.maemo.org/user/parazyd", "fullName" : "Ivan J." }, { "absoluteUrl" : "https://phoenix.maemo.org/user/spinal.by", "fullName" : "Arthur D." } ] }