[PATCH 4.14 156/159] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny <k.koniec...@partner.samsung.com> commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kerne

[PATCH 4.14 156/159] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES

[PATCH 4.14 154/159] crypto: talitos - fix Kernel Oops on hashing an empty file

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe <christophe.le...@c-s.fr> commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600]

[PATCH 4.14 154/159] crypto: talitos - fix Kernel Oops on hashing an empty file

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request

[PATCH 4.15 42/45] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny <k.koniec...@partner.samsung.com> commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kerne

[PATCH 4.15 42/45] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES

[PATCH 4.9 145/145] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny <k.koniec...@partner.samsung.com> commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kerne

[PATCH 4.9 145/145] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES

[PATCH 4.4 043/193] powerpc/perf: Fix oops when grouping different pmu events

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event,

[PATCH 4.4 043/193] powerpc/perf: Fix oops when grouping different pmu events

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with

Re: [PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

Le 22/02/2018 à 09:30, Horia Geantă a écrit : On 2/22/2018 9:08 AM, Christophe Leroy wrote: Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request for data at address 0x000c

Re: [PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

Le 22/02/2018 à 09:30, Horia Geantă a écrit : On 2/22/2018 9:08 AM, Christophe Leroy wrote: Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request for data at address 0x000c

Re: [PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

On 2/22/2018 9:08 AM, Christophe Leroy wrote: > Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 > > Performing the hash of an empty file leads to a kernel Oops > > [ 44.504600] Unable to handle kernel paging request for data at address > 0x000c > [ 44.512819]

Re: [PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

On 2/22/2018 9:08 AM, Christophe Leroy wrote: > Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 > > Performing the hash of an empty file leads to a kernel Oops > > [ 44.504600] Unable to handle kernel paging request for data at address > 0x000c > [ 44.512819]

[PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request for data at address 0x000c [ 44.512819] Faulting instruction address: 0xc02d2be8 [ 44.524088] Oops: Kernel access of bad

[PATCH 4.14, 4.9] crypto: talitos - fix Kernel Oops on hashing an empty file

Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721 Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request for data at address 0x000c [ 44.512819] Faulting instruction address: 0xc02d2be8 [ 44.524088] Oops: Kernel access of bad

[PATCH 4.14 008/167] IB/core: Avoid a potential OOPs for an unused optional parameter

passed, the ev_file pointer will be NULL. Using that pointer to set the cq_context will result in an OOPs. Verify that ev_file is not NULL before using. Cc: <sta...@vger.kernel.org> # 4.14.x Fixes: 9ee79fce3642 ("IB/core: Add completion queue (cq) object actions") Reviewed-

[PATCH 4.14 008/167] IB/core: Avoid a potential OOPs for an unused optional parameter

will be NULL. Using that pointer to set the cq_context will result in an OOPs. Verify that ev_file is not NULL before using. Cc: # 4.14.x Fixes: 9ee79fce3642 ("IB/core: Add completion queue (cq) object actions") Reviewed-by: Dennis Dalessandro Reviewed-by: Ira Weiny Signed-off-by: Michael J. Ru

[PATCH 4.15 007/163] IB/core: Avoid a potential OOPs for an unused optional parameter

passed, the ev_file pointer will be NULL. Using that pointer to set the cq_context will result in an OOPs. Verify that ev_file is not NULL before using. Cc: <sta...@vger.kernel.org> # 4.14.x Fixes: 9ee79fce3642 ("IB/core: Add completion queue (cq) object actions") Reviewed-

[PATCH 4.15 007/163] IB/core: Avoid a potential OOPs for an unused optional parameter

will be NULL. Using that pointer to set the cq_context will result in an OOPs. Verify that ev_file is not NULL before using. Cc: # 4.14.x Fixes: 9ee79fce3642 ("IB/core: Add completion queue (cq) object actions") Reviewed-by: Dennis Dalessandro Reviewed-by: Ira Weiny Signed-off-by: Michael J. Ru

Re: v4.13 on nokia n900: oops during tethering

Hi! > On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote: > > Hi! > > > > During tethering, I got oops in ssi_stop_tx(), followed by failure of > > GPRS. I used GPRS tethering a lot with some older kernel, and it was > > stable for hours. > >

Re: v4.13 on nokia n900: oops during tethering

Hi! > On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote: > > Hi! > > > > During tethering, I got oops in ssi_stop_tx(), followed by failure of > > GPRS. I used GPRS tethering a lot with some older kernel, and it was > > stable for hours. > >

Re: [mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

issue?] All fixups are in v4.15. > On Mon 05-02-18 19:54:24, Abdul Haleem wrote: > > > > Greetings, > > > > Kernel Oops seen when memory hot-unplug on powerpc mainline kernel. > > > > Machine: Power6 PowerVM ppc64 > > Kernel: 4.15.0 > > Config:

Re: [mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

issue?] All fixups are in v4.15. > On Mon 05-02-18 19:54:24, Abdul Haleem wrote: > > > > Greetings, > > > > Kernel Oops seen when memory hot-unplug on powerpc mainline kernel. > > > > Machine: Power6 PowerVM ppc64 > > Kernel: 4.15.0 > > Config:

Re: [mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

[CC Kirill - I have a vague recollection that there were some follow ups for 83e3c48729d9 ("mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y"). Does any of them apply to this issue?] On Mon 05-02-18 19:54:24, Abdul Haleem wrote: > > Greetings, >

Re: [mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

[CC Kirill - I have a vague recollection that there were some follow ups for 83e3c48729d9 ("mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y"). Does any of them apply to this issue?] On Mon 05-02-18 19:54:24, Abdul Haleem wrote: > > Greetings, >

[PATCH 4.9 51/88] crypto: talitos - fix Kernel Oops on hashing an empty file

4.9-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe <christophe.le...@c-s.fr> commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to

[PATCH 4.9 51/88] crypto: talitos - fix Kernel Oops on hashing an empty file

4.9-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request

[PATCH 4.14 135/195] crypto: talitos - fix Kernel Oops on hashing an empty file

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe <christophe.le...@c-s.fr> commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600]

[PATCH 4.14 135/195] crypto: talitos - fix Kernel Oops on hashing an empty file

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request

Re: [PATCH v3] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On Wed, Feb 07, 2018 at 04:52:09PM +0100, Kamil Konieczny wrote: > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops. Use IV only in AES-CBC and AES-CTR. > > Signed-off-by: Kamil Konieczny <k.koniec...@partner.samsung.com> > Reported-by:

Re: [PATCH v3] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On Wed, Feb 07, 2018 at 04:52:09PM +0100, Kamil Konieczny wrote: > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops. Use IV only in AES-CBC and AES-CTR. > > Signed-off-by: Kamil Konieczny > Reported-by: Anand Moon > Reviewed-by: Krzysztof K

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On Mon, Feb 05, 2018 at 06:40:20PM +0100, Kamil Konieczny wrote: > > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops, as reported by Anand Moon. > Fixed it by using IV only in AES-CBC and AES-CTR. > > Signed-off-by: Kamil K

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On Mon, Feb 05, 2018 at 06:40:20PM +0100, Kamil Konieczny wrote: > > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops, as reported by Anand Moon. > Fixed it by using IV only in AES-CBC and AES-CTR. > > Signed-off-by: Kamil Konieczny > Re

[PATCH 4.15 129/202] crypto: talitos - fix Kernel Oops on hashing an empty file

4.15-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe <christophe.le...@c-s.fr> commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600]

[PATCH 4.15 129/202] crypto: talitos - fix Kernel Oops on hashing an empty file

4.15-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 87a81dce53b1ea61acaeefa5191a0376a2d1d721 upstream. Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

> Actually this was brought up to me already, there's a fix on the mailing list > for this I reviewed a little while ago from nvidia that we should pull in: > > https://patchwork.freedesktop.org/patch/203205/ > > Would you guys mind confirming that this patch fixes your issues? It works on my

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

> Actually this was brought up to me already, there's a fix on the mailing list > for this I reviewed a little while ago from nvidia that we should pull in: > > https://patchwork.freedesktop.org/patch/203205/ > > Would you guys mind confirming that this patch fixes your issues? It works on my

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

Actually this was brought up to me already, there's a fix on the mailing list for this I reviewed a little while ago from nvidia that we should pull in: https://patchwork.freedesktop.org/patch/203205/ Would you guys mind confirming that this patch fixes your issues? On Wed, 2018-02-14 at 18:41

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

Actually this was brought up to me already, there's a fix on the mailing list for this I reviewed a little while ago from nvidia that we should pull in: https://patchwork.freedesktop.org/patch/203205/ Would you guys mind confirming that this patch fixes your issues? On Wed, 2018-02-14 at 18:41

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

On 2018-02-14 — 09:36, Ilia Mirkin wrote: > On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin wrote: > > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote: > >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > >> > >> NV5 in another PC

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

On 2018-02-14 — 09:36, Ilia Mirkin wrote: > On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin wrote: > > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote: > >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > >> > >> NV5 in another PC (secondary card in x86-64) made the

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin wrote: > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote: >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: >> >> NV5 in another PC (secondary card in x86-64) made the systrem crash

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

On Wed, Feb 14, 2018 at 9:35 AM, Ilia Mirkin wrote: > On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote: >>> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: >> >> NV5 in another PC (secondary card in x86-64) made the systrem crash on >> boot, in nvkm_therm_clkgate_fini.

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote: >> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > > NV5 in another PC (secondary card in x86-64) made the systrem crash on > boot, in nvkm_therm_clkgate_fini. Mind booting with nouveau.debug=trace?

Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

On Wed, Feb 14, 2018 at 9:29 AM, Meelis Roos wrote: >> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: > > NV5 in another PC (secondary card in x86-64) made the systrem crash on > boot, in nvkm_therm_clkgate_fini. Mind booting with nouveau.debug=trace? That should

Re: 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: NV5 in another PC (secondary card in x86-64) made the systrem crash on boot, in nvkm_therm_clkgate_fini. -- Meelis Roos (mr...@linux.ee)

Re: 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: NV5 in another PC (secondary card in x86-64) made the systrem crash on boot, in nvkm_therm_clkgate_fini. -- Meelis Roos (mr...@linux.ee)

Re: v4.13 on nokia n900: oops during tethering

Hi! > > During tethering, I got oops in ssi_stop_tx(), followed by failure of > > GPRS. I used GPRS tethering a lot with some older kernel, and it was > > stable for hours. > > > > It seems v4.12 has the same problem. In v4.15 usb networking does not > > w

Re: v4.13 on nokia n900: oops during tethering

Hi! > > During tethering, I got oops in ssi_stop_tx(), followed by failure of > > GPRS. I used GPRS tethering a lot with some older kernel, and it was > > stable for hours. > > > > It seems v4.12 has the same problem. In v4.15 usb networking does not > > w

Re: v4.13 on nokia n900: oops during tethering

Hi Pavel, On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote: > Hi! > > During tethering, I got oops in ssi_stop_tx(), followed by failure of > GPRS. I used GPRS tethering a lot with some older kernel, and it was > stable for hours. > > It seems v4.12 has the s

Re: v4.13 on nokia n900: oops during tethering

Hi Pavel, On Mon, Feb 12, 2018 at 09:10:00PM +0100, Pavel Machek wrote: > Hi! > > During tethering, I got oops in ssi_stop_tx(), followed by failure of > GPRS. I used GPRS tethering a lot with some older kernel, and it was > stable for hours. > > It seems v4.12 has the s

4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

] [7.409344] BUG: unable to handle kernel NULL pointer dereference at (null) [7.409640] IP: nvkm_therm_clkgate_fini+0x15/0x174 [nouveau] [7.409738] *pde = [7.409833] Oops: [#1] [7.409923] Modules linked in: nouveau(+) evdev wmi video i2c_algo_bit drm_kms_helper

4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini

] [7.409344] BUG: unable to handle kernel NULL pointer dereference at (null) [7.409640] IP: nvkm_therm_clkgate_fini+0x15/0x174 [nouveau] [7.409738] *pde = [7.409833] Oops: [#1] [7.409923] Modules linked in: nouveau(+) evdev wmi video i2c_algo_bit drm_kms_helper

v4.13 on nokia n900: oops during tethering

Hi! During tethering, I got oops in ssi_stop_tx(), followed by failure of GPRS. I used GPRS tethering a lot with some older kernel, and it was stable for hours. It seems v4.12 has the same problem. In v4.15 usb networking does not work at all, so I can't test... v4.10 seems to have similar

v4.13 on nokia n900: oops during tethering

Hi! During tethering, I got oops in ssi_stop_tx(), followed by failure of GPRS. I used GPRS tethering a lot with some older kernel, and it was stable for hours. It seems v4.12 has the same problem. In v4.15 usb networking does not work at all, so I can't test... v4.10 seems to have similar

Re: [PATCH] extcon: intel-int3496: Fix oops on probe

Hi, On 12-02-18 00:36, Chanwoo Choi wrote: On 2018년 02월 12일 08:26, Hans de Goede wrote: Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we start with the right status") starts the work on the workqueue before registration to make sure we've a valid cable state directly

Re: [PATCH] extcon: intel-int3496: Fix oops on probe

Hi, On 12-02-18 00:36, Chanwoo Choi wrote: On 2018년 02월 12일 08:26, Hans de Goede wrote: Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we start with the right status") starts the work on the workqueue before registration to make sure we've a valid cable state directly

Re: [PATCH] extcon: intel-int3496: Fix oops on probe

On 2018년 02월 12일 08:26, Hans de Goede wrote: > Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we > start with the right status") starts the work on the workqueue before > registration to make sure we've a valid cable state directly after > registration. > > But that commit

Re: [PATCH] extcon: intel-int3496: Fix oops on probe

On 2018년 02월 12일 08:26, Hans de Goede wrote: > Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we > start with the right status") starts the work on the workqueue before > registration to make sure we've a valid cable state directly after > registration. > > But that commit

[PATCH] extcon: intel-int3496: Fix oops on probe

Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we start with the right status") starts the work on the workqueue before registration to make sure we've a valid cable state directly after registration. But that commit moves the queuing of the work to before we even alloc the

[PATCH] extcon: intel-int3496: Fix oops on probe

Commit 41d600274fbf ("extcon: int3496: process id-pin first so that we start with the right status") starts the work on the workqueue before registration to make sure we've a valid cable state directly after registration. But that commit moves the queuing of the work to before we even alloc the

Re: [PATCH] crypto: talitos: fix Kernel Oops on hashing an empty file

On Fri, Jan 26, 2018 at 05:09:59PM +0100, Christophe Leroy wrote: > Performing the hash of an empty file leads to a kernel Oops > > [ 44.504600] Unable to handle kernel paging request for data at address > 0x000c > [ 44.512819] Faulting instruction address: 0xc02d2be8

Re: [PATCH] crypto: talitos: fix Kernel Oops on hashing an empty file

On Fri, Jan 26, 2018 at 05:09:59PM +0100, Christophe Leroy wrote: > Performing the hash of an empty file leads to a kernel Oops > > [ 44.504600] Unable to handle kernel paging request for data at address > 0x000c > [ 44.512819] Faulting instruction address: 0xc02d2be8

[mainline][libhugetlbfs][ppc] stack_grow_into_huge test results in kernel Oops

Greetings, Today's mainline kernel Oops when running stack_grow_into_huge Machine: Power 8 bare-metal Kernel: 4.15.0 Config: attached gcc: 4.8.5 Test: libhugetlbfs stack_grow_into_huge (16M: 64) resulted in kernel Oops message and the bad address maps to: # gdb -batch vmlinux -ex 'list

[mainline][libhugetlbfs][ppc] stack_grow_into_huge test results in kernel Oops

Greetings, Today's mainline kernel Oops when running stack_grow_into_huge Machine: Power 8 bare-metal Kernel: 4.15.0 Config: attached gcc: 4.8.5 Test: libhugetlbfs stack_grow_into_huge (16M: 64) resulted in kernel Oops message and the bad address maps to: # gdb -batch vmlinux -ex 'list

[mainline][ppc - bare-metal ] memory hotunplug operation results in kernel Oops

Greetings, Todays mainline kernel has Oops messages for memory hot-unplug operation. Machine: Power 8 bare-metal Kernel: 4.15.0 Config: attached gcc: 4.8.5 Test: Memory hot-unplug echo offline > /sys/devices/system/memory/memory/state the above command triggered 2 kernel Oops messa

[mainline][ppc - bare-metal ] memory hotunplug operation results in kernel Oops

Greetings, Todays mainline kernel has Oops messages for memory hot-unplug operation. Machine: Power 8 bare-metal Kernel: 4.15.0 Config: attached gcc: 4.8.5 Test: Memory hot-unplug echo offline > /sys/devices/system/memory/memory/state the above command triggered 2 kernel Oops messa

[PATCH v3] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES-CTR. Signed-off-by: Kamil Konieczny <k.koniec...@partner.samsung.com> Reported-by: Anand Moon <linux.am...@gmail.com> Reviewed-by: Krzysztof Kozlowski <k...@ker

[PATCH v3] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES-CTR. Signed-off-by: Kamil Konieczny Reported-by: Anand Moon Reviewed-by: Krzysztof Kozlowski Tested-by: Anand Moon Cc: sta...@vger.kernel.org # can be applied after commit

[PATCH v2] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES-CTR. Signed-off-by: Kamil Konieczny <k.koniec...@partner.samsung.com> Reported-by: Anand Moon <linux.am...@gmail.com> Reviewed-by: Krzysztof Kozlowski <k...@ker

[PATCH v2] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and AES-CTR. Signed-off-by: Kamil Konieczny Reported-by: Anand Moon Reviewed-by: Krzysztof Kozlowski Tested-by: Anand Moon Cc: sta...@vger.kernel.org Fixes: 8f9702aad138 ("crypto

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

>> <k.koniec...@partner.samsung.com> wrote: >>> >>> In AES-ECB mode crypt is done with key only, so any use of IV >>> can cause kernel Oops, as reported by Anand Moon. >> >> If possible could you avoid the name in commit message. > > This

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

> In AES-ECB mode crypt is done with key only, so any use of IV >>> can cause kernel Oops, as reported by Anand Moon. >> >> If possible could you avoid the name in commit message. > > This is added after '---' line, so it will not appear in commit message. > I kno

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On 06.02.2018 17:48, Anand Moon wrote: > Hi Kamil, > > Thanks for providing the fix to this issue. > > On 5 February 2018 at 23:10, Kamil Konieczny > <k.koniec...@partner.samsung.com> wrote: >> >> In AES-ECB mode crypt is done with key only, so an

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On 06.02.2018 17:48, Anand Moon wrote: > Hi Kamil, > > Thanks for providing the fix to this issue. > > On 5 February 2018 at 23:10, Kamil Konieczny > wrote: >> >> In AES-ECB mode crypt is done with key only, so any use of IV >> can cause kernel Oops, as repo

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

Hi Kamil, Thanks for providing the fix to this issue. On 5 February 2018 at 23:10, Kamil Konieczny <k.koniec...@partner.samsung.com> wrote: > > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops, as reported by Anand Moon. If possible could you

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

Hi Kamil, Thanks for providing the fix to this issue. On 5 February 2018 at 23:10, Kamil Konieczny wrote: > > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops, as reported by Anand Moon. If possible could you avoid the name in commit message.

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On Mon, Feb 5, 2018 at 6:40 PM, Kamil Konieczny <k.koniec...@partner.samsung.com> wrote: > > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops, as reported by Anand Moon. > Fixed it by using IV only in AES-CBC and AES-CTR. > > Signed

Re: [PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

On Mon, Feb 5, 2018 at 6:40 PM, Kamil Konieczny wrote: > > In AES-ECB mode crypt is done with key only, so any use of IV > can cause kernel Oops, as reported by Anand Moon. > Fixed it by using IV only in AES-CBC and AES-CTR. > > Signed-off-by: Kamil Konieczny > Re

[PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops, as reported by Anand Moon. Fixed it by using IV only in AES-CBC and AES-CTR. Signed-off-by: Kamil Konieczny <k.koniec...@partner.samsung.com> Reported-by: Anand Moon <linux.am...@gmail.com> --- Test

[PATCH] crypto: s5p-sss.c: Fix kernel Oops in AES-ECB mode

In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops, as reported by Anand Moon. Fixed it by using IV only in AES-CBC and AES-CTR. Signed-off-by: Kamil Konieczny Reported-by: Anand Moon --- Tested on Odroid XU4/HC1, kernel 4.15 with following command: fallocate

[mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

Greetings, Kernel Oops seen when memory hot-unplug on powerpc mainline kernel. Machine: Power6 PowerVM ppc64 Kernel: 4.15.0 Config: attached gcc: 4.8.2 Test: Memory hot-unplug of a memory block echo offline > /sys/devices/system/memory/memory/state The faulty instruction address poi

[mainline][Memory off/on][83e3c48] kernel Oops with memory hot-unplug on ppc

Greetings, Kernel Oops seen when memory hot-unplug on powerpc mainline kernel. Machine: Power6 PowerVM ppc64 Kernel: 4.15.0 Config: attached gcc: 4.8.2 Test: Memory hot-unplug of a memory block echo offline > /sys/devices/system/memory/memory/state The faulty instruction address poi

[PATCH AUTOSEL for 4.9 24/52] tipc: fix tipc_mon_delete() oops in tipc_enable_bearer() error path

From: Tommi Rantala <tommi.t.rant...@nokia.com> [ Upstream commit 642a8439ddd8423b92f2e71960afe21ee1f66bb6 ] Calling tipc_mon_delete() before the monitor has been created will oops. This can happen in tipc_enable_bearer() error path if tipc_disc_create() fails. [ 48.589074] BUG:

[PATCH AUTOSEL for 4.9 24/52] tipc: fix tipc_mon_delete() oops in tipc_enable_bearer() error path

From: Tommi Rantala [ Upstream commit 642a8439ddd8423b92f2e71960afe21ee1f66bb6 ] Calling tipc_mon_delete() before the monitor has been created will oops. This can happen in tipc_enable_bearer() error path if tipc_disc_create() fails. [ 48.589074] BUG: unable to handle kernel paging request

[PATCH AUTOSEL for 4.14 060/110] tipc: fix tipc_mon_delete() oops in tipc_enable_bearer() error path

From: Tommi Rantala <tommi.t.rant...@nokia.com> [ Upstream commit 642a8439ddd8423b92f2e71960afe21ee1f66bb6 ] Calling tipc_mon_delete() before the monitor has been created will oops. This can happen in tipc_enable_bearer() error path if tipc_disc_create() fails. [ 48.589074] BUG:

[PATCH AUTOSEL for 4.14 060/110] tipc: fix tipc_mon_delete() oops in tipc_enable_bearer() error path

From: Tommi Rantala [ Upstream commit 642a8439ddd8423b92f2e71960afe21ee1f66bb6 ] Calling tipc_mon_delete() before the monitor has been created will oops. This can happen in tipc_enable_bearer() error path if tipc_disc_create() fails. [ 48.589074] BUG: unable to handle kernel paging request

[PATCH AUTOSEL for 4.14 047/100] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link

[PATCH AUTOSEL for 4.14 047/100] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link register ] c010ce88

[PATCH AUTOSEL for 4.4 14/36] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link

[PATCH AUTOSEL for 4.4 14/36] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link register ] c010ce88

[PATCH AUTOSEL for 3.18 09/25] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link

[PATCH AUTOSEL for 3.18 09/25] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link register ] c010ce88

[PATCH AUTOSEL for 4.9 20/49] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link

[PATCH AUTOSEL for 4.9 20/49] powerpc/perf: Fix oops when grouping different pmu events

From: Ravi Bangoria [ Upstream commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 ] When user tries to group imc (In-Memory Collections) event with normal event, (sometime) kernel crashes with following log: Faulting instruction address: 0x [link register ] c010ce88

[PATCH] crypto: talitos: fix Kernel Oops on hashing an empty file

Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request for data at address 0x000c [ 44.512819] Faulting instruction address: 0xc02d2be8 [ 44.524088] Oops: Kernel access of bad area, sig: 11 [#1] [ 44.529171] BE PREEMPT CMPC885

[PATCH] crypto: talitos: fix Kernel Oops on hashing an empty file

Performing the hash of an empty file leads to a kernel Oops [ 44.504600] Unable to handle kernel paging request for data at address 0x000c [ 44.512819] Faulting instruction address: 0xc02d2be8 [ 44.524088] Oops: Kernel access of bad area, sig: 11 [#1] [ 44.529171] BE PREEMPT CMPC885

[RFC PATCH v3 09/13] fbcon: Disable bootsplash on oops

Signed-off-by: Max Staudt Reviewed-by: Oliver Neukum --- drivers/video/fbdev/core/fbcon.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c index 9a39a6fcfe98..8a9c67e1c5d8

[RFC PATCH v3 09/13] fbcon: Disable bootsplash on oops

Signed-off-by: Max Staudt Reviewed-by: Oliver Neukum --- drivers/video/fbdev/core/fbcon.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c index 9a39a6fcfe98..8a9c67e1c5d8 100644 ---

<    9   10   11   12   13   14   15   16   17   18   >