Re: [PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

[0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed [0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22 tee_shm_release() is not invoked on dma shm buffer. Implement .shutdown() method to handle the release of the buffers correctly. More info:

Re: [PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

On Tue, Mar 16, 2021 at 2:21 PM Allen Pais wrote: > > > > >> > >> [0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed > >> [0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22 > >> > >> tee_shm_release() is not invoked on dma shm buffer. > >> > >> Implement .shutdown()

[PATCH net-next 1/4] net: hinic: Remove unnecessary 'out of memory' message

This patch removes unnecessary out of memory message in hinic driver, fixes the following checkpatch.pl warning: "WARNING: Possible unnecessary 'out of memory' message" Signed-off-by: Daode Huang --- drivers/net/ethernet/huawei/hinic/hinic_hw_api_cmd.c | 8 ++-- drivers/net/ether

Re: [PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

On 2021-02-25 14:36:09, Allen Pais wrote: > From: Allen Pais > > The following out of memory errors are seen on kexec reboot > from the optee core. > > [0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed > [0.368461] tee_bnxt_fw: probe of optee-clnt0

Re: [PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

[0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed [0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22 tee_shm_release() is not invoked on dma shm buffer. Implement .shutdown() method to handle the release of the buffers correctly. More info:

Re: [PATCH][next] scsi: sg: return -ENOMEM on out of memory error

On 2021-03-11 6:33 p.m., Colin King wrote: From: Colin Ian King The sg_proc_seq_show_debug should return -ENOMEM on an out of memory error rather than -1. Fix this. Fixes: 94cda6cf2e44 ("scsi: sg: Rework debug info") Signed-off-by: Colin Ian King Acked-by: Douglas Gilber

[PATCH][next] scsi: sg: return -ENOMEM on out of memory error

From: Colin Ian King The sg_proc_seq_show_debug should return -ENOMEM on an out of memory error rather than -1. Fix this. Fixes: 94cda6cf2e44 ("scsi: sg: Rework debug info") Signed-off-by: Colin Ian King --- drivers/scsi/sg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

From: Allen Pais The following out of memory errors are seen on kexec reboot from the optee core. [0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed [0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22 tee_shm_release() is not invoked on dma shm buffer. Implement

Re: [PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

On Thu, Feb 25, 2021 at 10:06 AM Allen Pais wrote: > > From: Allen Pais > > The following out of memory errors are seen on kexec reboot > from the optee core. > > [0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed > [0.368461] tee_bnxt_fw: probe of optee-cln

[PATCH v2 1/2] optee: fix tee out of memory failure seen during kexec reboot

From: Allen Pais The following out of memory errors are seen on kexec reboot from the optee core. [0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed [0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22 tee_shm_release() is not invoked on dma shm buffer. Implement

Re: [PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot

- /* -* Ask OP-TEE to free all cached shared memory objects to decrease -* reference counters and also avoid wild pointers in secure world -* into the old shared memory range. -*/ - optee_disable_shm_cache(optee); + if (shutdown) { +

Re: [PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot

On Tue, Feb 23, 2021 at 09:56:13PM +0530, Allen Pais wrote: > > > > > > > - /* > > > > > - * Ask OP-TEE to free all cached shared memory objects to > > > > > decrease > > > > > - * reference counters and also avoid wild pointers in secure > > > > > world > > > > > - * into

Re: [PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot

- /* -* Ask OP-TEE to free all cached shared memory objects to decrease -* reference counters and also avoid wild pointers in secure world -* into the old shared memory range. -*/ - optee_disable_shm_cache(optee); + if (shutdown) { +

Re: [PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot

On Mon, Feb 22, 2021 at 06:15:08PM +0530, Allen Pais wrote: > > > On Wed, 17 Feb 2021 14:57:12 +0530, Allen Pais wrote: > > > - /* > > > - * Ask OP-TEE to free all cached shared memory objects to decrease > > > - * reference counters and also avoid wild pointers in secure world > > > - * into

Re: [PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot

On Wed, 17 Feb 2021 14:57:12 +0530, Allen Pais wrote: - /* -* Ask OP-TEE to free all cached shared memory objects to decrease -* reference counters and also avoid wild pointers in secure world -* into the old shared memory range. -*/ -

[PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot

From: Allen Pais The following out of memory errors are seen on kexec reboot from the optee core. [0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed [0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22 tee_shm_release() is not invoked on dma shm buffer. Implement

Re: 5.10 RC 7: grub2 out of memory

0 Cinnamon. elias@elias-5600X:~$ grub-install --version grub-install (GRUB) 2.04-1ubuntu26.7 Thanks, Elias On Mon, Dec 7, 2020 at 1:38 AM David Hildenbrand wrote: > > On 07.12.20 10:16, Elias Carter wrote: > > I just compiled and installed 5.10 RC 7 and got a message from grub2: >

Re: 5.10 RC 7: grub2 out of memory

On 07.12.20 10:16, Elias Carter wrote: > I just compiled and installed 5.10 RC 7 and got a message from grub2: > "out of memory, press any key to continue" shortly followed by a > kernel panic (see attached screenshot). > > The 5.4.0-56-generic kernel from Ubuntu

Re: 5.10 RC 7: grub2 out of memory

Resending grub config since that appeared to be mangled by my mail client: On Mon, Dec 7, 2020 at 1:16 AM Elias Carter wrote: > > I just compiled and installed 5.10 RC 7 and got a message from grub2: > "out of memory, press any key to continue" shortly followed by a > kern

[PATCH 7/7] slimbus: qcom-ngd-ctrl: remove redundant out of memory messages

Failure of dma_alloc_coherent will already throw a error message, so addition message is really redundant here. Remove it! Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/qcom-ngd-ctrl.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/slimbus/qcom-ngd-ctrl.c

[PATCH rdma-next 4/4] gcov: Don't print out-of-memory print for all failed files

From: Leon Romanovsky Once GCOV fails to duplicate information, the following error is printed: gcov: could not save data for '/home/leonro/src/kernel/drivers/infiniband/hw/mlx5/std_types.gcda' (out of memory) In the event of out-of-memory such prints are seen for almost every kernel file

Re: [PATCH][next] ASoC: qcom: add missing out of memory check on drvdata->clks allocation

.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: qcom: add missing out of memory check on drvdata->clks allocation commit: a467f2f8ad5f9a21f92b3fa6ad2aac90fa7054fe All being well this means that it will be integrated into the linux-next tree (usually sometime

Re: [PATCH][next] ASoC: qcom: add missing out of memory check on drvdata->clks allocation

On 8/19/2020 9:31 PM, Colin King wrote: From: Colin Ian King Currently drvdata->clks is not being checked for an allocation failure, leading to potential null pointer dereferencing. Fix this by adding a check and returning -ENOMEM if an error occurred. Addresses-Coverity: ("Dereference null

[PATCH][next] ASoC: qcom: add missing out of memory check on drvdata->clks allocation

From: Colin Ian King Currently drvdata->clks is not being checked for an allocation failure, leading to potential null pointer dereferencing. Fix this by adding a check and returning -ENOMEM if an error occurred. Addresses-Coverity: ("Dereference null return value") Fixes: 1220f6a76e77 ("ASoC:

Re: [PATCH 4.19 65/79] net: aquantia: fix out of memory condition on rx side

gracefully closing napi poll routine with correct > invocation of napi_complete_done. > > This was reproduced with artificially failing the allocation of skb to > simulate an "out of memory" error case and check that traffic does > not get stuck. > --- a/drivers/net/ether

[PATCH 4.19 65/79] net: aquantia: fix out of memory condition on rx side

th correct invocation of napi_complete_done. This was reproduced with artificially failing the allocation of skb to simulate an "out of memory" error case and check that traffic does not get stuck. Fixes: 970a2e9864b0 ("net: ethernet: aquantia: Vector operations") Signed-off-by: Igor R

[PATCH 5.2 105/124] net: aquantia: fix out of memory condition on rx side

th correct invocation of napi_complete_done. This was reproduced with artificially failing the allocation of skb to simulate an "out of memory" error case and check that traffic does not get stuck. Fixes: 970a2e9864b0 ("net: ethernet: aquantia: Vector operations") Signed-off-by: Igor R

[PATCH AUTOSEL 5.2 91/94] net: aquantia: fix out of memory condition on rx side

th correct invocation of napi_complete_done. This was reproduced with artificially failing the allocation of skb to simulate an "out of memory" error case and check that traffic does not get stuck. Fixes: 970a2e9864b0 ("net: ethernet: aquantia: Vector operations") Signed-off-by: Igor R

[PATCH AUTOSEL 4.19 51/52] net: aquantia: fix out of memory condition on rx side

th correct invocation of napi_complete_done. This was reproduced with artificially failing the allocation of skb to simulate an "out of memory" error case and check that traffic does not get stuck. Fixes: 970a2e9864b0 ("net: ethernet: aquantia: Vector operations") Signed-off-by: Igor R

[PATCH 03/10] nouveau: factor out device memory address calculation

Factor out the repeated device memory address calculation into a helper. Signed-off-by: Christoph Hellwig Reviewed-by: Ralph Campbell --- drivers/gpu/drm/nouveau/nouveau_dmem.c | 42 +++--- 1 file changed, 17 insertions(+), 25 deletions(-) diff --git

[PATCH net-next 06/11] net: hns3: modify handling of out of memory in hclge_err.c

From: Weihang Li Users should be informed if HNS driver failed to allocate memory for descriptor when handling hw errors. This patch solve above issues. Signed-off-by: Weihang Li Signed-off-by: Peng Li Signed-off-by: Huazhong Tan --- drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_err.c |

Re: [PATCH] PM / clk: Remove error message on out-of-memory condition

On Monday, May 27, 2019 2:27:51 PM CEST Geert Uytterhoeven wrote: > There is no need to print an error message if kstrdup() fails, as the > memory allocation core already takes care of that. > > Note that commit 59d84ca8c46a93ad ("PM / OPP / clk: Remove unnecessary > OOM message") already removed

Re: [PATCH] cpumask: Remove error message and backtrace on out-of-memory condition

On Mon, 27 May 2019 14:29:58 +0200 Geert Uytterhoeven wrote: > There is no need to print an error message and backtrace if > kmalloc_node() fails, as the memory allocation core already takes care > of that. > > ... > > --- a/lib/cpumask.c > +++ b/lib/cpumask.c > @@ -114,13 +114,6 @@ bool

Re: [tip:irq/core] genirq/irqdomain: Remove WARN_ON() on out-of-memory condition

On 5/28/19 5:54 PM, Joe Perches wrote: > On Tue, 2019-05-28 at 13:23 -0700, tip-bot for Geert Uytterhoeven wrote: >> diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c > [] >> @@ -139,7 +139,7 @@ struct irq_domain *__irq_domain_add(struct fwnode_handle >> *fwnode, int size, >> >>

Re: [tip:irq/core] genirq/irqdomain: Remove WARN_ON() on out-of-memory condition

On Tue, 2019-05-28 at 13:23 -0700, tip-bot for Geert Uytterhoeven wrote: > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c [] > @@ -139,7 +139,7 @@ struct irq_domain *__irq_domain_add(struct fwnode_handle > *fwnode, int size, > > domain = kzalloc_node(sizeof(*domain) +

[tip:irq/core] genirq/irqdomain: Remove WARN_ON() on out-of-memory condition

/irqdomain: Remove WARN_ON() on out-of-memory condition There is no need to print a backtrace when memory allocation fails, as the memory allocation core already takes care of that. Signed-off-by: Geert Uytterhoeven Signed-off-by: Thomas Gleixner Cc: Marc Zyngier Link: https://lkml.kernel.org/r

[PATCH] cpumask: Remove error message and backtrace on out-of-memory condition

There is no need to print an error message and backtrace if kmalloc_node() fails, as the memory allocation core already takes care of that. Signed-off-by: Geert Uytterhoeven --- lib/cpumask.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/lib/cpumask.c b/lib/cpumask.c index

[PATCH] PM / clk: Remove error message on out-of-memory condition

There is no need to print an error message if kstrdup() fails, as the memory allocation core already takes care of that. Note that commit 59d84ca8c46a93ad ("PM / OPP / clk: Remove unnecessary OOM message") already removed similar error messages, but this one was forgotten. Signed-off-by: Geert

[PATCH] arch_topology: Remove error messages on out-of-memory conditions

There is no need to print error messages if kcalloc() or alloc_cpumask_var() fail, as the memory allocation core already takes care of that. Signed-off-by: Geert Uytterhoeven --- drivers/base/arch_topology.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH v2 2/5] irqchip/renesas-irqc: Remove error messages on out-of-memory conditions

There is no need to print error messages if kzalloc() or ioremap_nocache() fail, as the memory allocation core already takes care of that. Signed-off-by: Geert Uytterhoeven Reviewed-by: Simon Horman --- v2: - Add Reviewed-by, - s/devm_kzalloc/kzalloc/ in patch description, reword. ---

[PATCH] genirq/irqdomain: Remove WARN_ON() on out-of-memory condition

There is no need to print a backtrace when memory allocation fails, as the memory allocation core already takes care of that. Signed-off-by: Geert Uytterhoeven --- kernel/irq/irqdomain.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/irq/irqdomain.c

[PATCH 4.20 79/80] md/raid5: fix out of memory during raid cache recovery

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Naberezhnov commit 483cbbeddd5fe2c80fd4141ff0748fa06c4ff146 upstream. This fixes the case when md array assembly fails because of raid cache recovery unable to allocate a stripe,

[PATCH 4.19 73/74] md/raid5: fix out of memory during raid cache recovery

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Naberezhnov commit 483cbbeddd5fe2c80fd4141ff0748fa06c4ff146 upstream. This fixes the case when md array assembly fails because of raid cache recovery unable to allocate a stripe,

[PATCH 4.14 43/46] md/raid5: fix out of memory during raid cache recovery

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Naberezhnov commit 483cbbeddd5fe2c80fd4141ff0748fa06c4ff146 upstream. This fixes the case when md array assembly fails because of raid cache recovery unable to allocate a stripe,

Re: [PATCH] staging: wlan-ng: prism2fw.c: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning"

The subject is too long. On Mon, Dec 24, 2018 at 08:11:28AM -0800, Prathamesh Deshpande wrote: > This patch removes unnecessary out of memory warning > message from wlan-ng prism2fw.c file. > > Signed-off-by: Prathamesh Deshpande > --- > drivers/staging/wlan-ng/prism2fw

[PATCH v2] staging: wlan-ng: prism2fw.c: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning"

This patch removes unnecessary out of memory warning message from wlan-ng prism2fw.c file. Signed-off-by: Prathamesh Deshpande --- drivers/staging/wlan-ng/prism2fw.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/staging/wlan-ng/prism2fw.c b/drivers/staging

[PATCH] staging: wlan-ng: prism2fw.c: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning"

This patch removes unnecessary out of memory warning message from wlan-ng prism2fw.c file. Signed-off-by: Prathamesh Deshpande --- drivers/staging/wlan-ng/prism2fw.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/wlan-ng/prism2fw.c b/drivers/staging/wlan-ng/prism2fw.c index

Re: ODEBUG: Out of memory. ODEBUG disabled

riday, November 09, 2018 at 5:08 PM >>>>> From: "Waiman Long" >>>>> To: "Qian Cai" , "Yang Shi" >>>>> Cc: "open list" , "Thomas Gleixner" >>>>> , "Arnd Bergmann" , "Joel Fernandes >

Re: ODEBUG: Out of memory. ODEBUG disabled

riday, November 09, 2018 at 5:08 PM >>>>> From: "Waiman Long" >>>>> To: "Qian Cai" , "Yang Shi" >>>>> Cc: "open list" , "Thomas Gleixner" >>>>> , "Arnd Bergmann" , "Joel Fernandes >

Re: ODEBUG: Out of memory. ODEBUG disabled

"Qian Cai" , "Yang Shi" >>>> Cc: "open list" , "Thomas Gleixner" >>>> , "Arnd Bergmann" , "Joel Fernandes >>>> (Google)" , "Zhong Jiang" >>>> Subject: Re: ODEBUG: Out of memory. OD

Re: ODEBUG: Out of memory. ODEBUG disabled

"Qian Cai" , "Yang Shi" >>>> Cc: "open list" , "Thomas Gleixner" >>>> , "Arnd Bergmann" , "Joel Fernandes >>>> (Google)" , "Zhong Jiang" >>>> Subject: Re: ODEBUG: Out of memory. OD

Re: ODEBUG: Out of memory. ODEBUG disabled

ot; , "Thomas Gleixner" > >> , "Arnd Bergmann" , "Joel Fernandes > >> (Google)" , "Zhong Jiang" > >> Subject: Re: ODEBUG: Out of memory. ODEBUG disabled > >> > >> On 11/09/2018 04:51 PM, Qian Cai wrote: > >>>

Re: ODEBUG: Out of memory. ODEBUG disabled

ot; , "Thomas Gleixner" > >> , "Arnd Bergmann" , "Joel Fernandes > >> (Google)" , "Zhong Jiang" > >> Subject: Re: ODEBUG: Out of memory. ODEBUG disabled > >> > >> On 11/09/2018 04:51 PM, Qian Cai wrote: > >>>

Re: ODEBUG: Out of memory. ODEBUG disabled

On 11/09/2018 08:45 PM, Qian Cai wrote: >> Sent: Friday, November 09, 2018 at 5:08 PM >> From: "Waiman Long" >> To: "Qian Cai" , "Yang Shi" >> Cc: "open list" , "Thomas Gleixner" >> , "Arnd Bergmann" , &q

Re: ODEBUG: Out of memory. ODEBUG disabled

On 11/09/2018 08:45 PM, Qian Cai wrote: >> Sent: Friday, November 09, 2018 at 5:08 PM >> From: "Waiman Long" >> To: "Qian Cai" , "Yang Shi" >> Cc: "open list" , "Thomas Gleixner" >> , "Arnd Bergmann" , &q

Re: ODEBUG: Out of memory. ODEBUG disabled

> Sent: Friday, November 09, 2018 at 5:08 PM > From: "Waiman Long" > To: "Qian Cai" , "Yang Shi" > Cc: "open list" , "Thomas Gleixner" > , "Arnd Bergmann" , "Joel Fernandes > (Google)" , "Zhong Jiang&

Re: ODEBUG: Out of memory. ODEBUG disabled

> Sent: Friday, November 09, 2018 at 5:08 PM > From: "Waiman Long" > To: "Qian Cai" , "Yang Shi" > Cc: "open list" , "Thomas Gleixner" > , "Arnd Bergmann" , "Joel Fernandes > (Google)" , "Zhong Jiang&

Re: ODEBUG: Out of memory. ODEBUG disabled

33fd1f2) causes object debugging >>> always running out of memory. >> May you please paste the detail failure log? > I assume you mean dmesg. > > Here is the dmesg for 64 CPUs, > https://paste.ubuntu.com/p/BnhvXXhn7k/ >>> I have to boot the kernel with only

Re: ODEBUG: Out of memory. ODEBUG disabled

33fd1f2) causes object debugging >>> always running out of memory. >> May you please paste the detail failure log? > I assume you mean dmesg. > > Here is the dmesg for 64 CPUs, > https://paste.ubuntu.com/p/BnhvXXhn7k/ >>> I have to boot the kernel with only

Re: ODEBUG: Out of memory. ODEBUG disabled

On 11/9/18 1:51 PM, Qian Cai wrote: On Nov 9, 2018, at 4:42 PM, Yang Shi wrote: On 11/9/18 1:36 PM, Qian Cai wrote: It is a bit annoying on this aarch64 server with 64 CPUs that is booting the latest mainline (3541833fd1f2) causes object debugging always running out of memory. May you

Re: ODEBUG: Out of memory. ODEBUG disabled

On 11/9/18 1:51 PM, Qian Cai wrote: On Nov 9, 2018, at 4:42 PM, Yang Shi wrote: On 11/9/18 1:36 PM, Qian Cai wrote: It is a bit annoying on this aarch64 server with 64 CPUs that is booting the latest mainline (3541833fd1f2) causes object debugging always running out of memory. May you

Re: ODEBUG: Out of memory. ODEBUG disabled

> On Nov 9, 2018, at 4:42 PM, Yang Shi wrote: > > > > On 11/9/18 1:36 PM, Qian Cai wrote: >> It is a bit annoying on this aarch64 server with 64 CPUs that is >> booting the latest mainline (3541833fd1f2) causes object debugging >> always running out of

Re: ODEBUG: Out of memory. ODEBUG disabled

> On Nov 9, 2018, at 4:42 PM, Yang Shi wrote: > > > > On 11/9/18 1:36 PM, Qian Cai wrote: >> It is a bit annoying on this aarch64 server with 64 CPUs that is >> booting the latest mainline (3541833fd1f2) causes object debugging >> always running out of

Re: ODEBUG: Out of memory. ODEBUG disabled

On 11/9/18 1:36 PM, Qian Cai wrote: It is a bit annoying on this aarch64 server with 64 CPUs that is booting the latest mainline (3541833fd1f2) causes object debugging always running out of memory. May you please paste the detail failure log? I have to boot the kernel with only 16 CPUs

Re: ODEBUG: Out of memory. ODEBUG disabled

On 11/9/18 1:36 PM, Qian Cai wrote: It is a bit annoying on this aarch64 server with 64 CPUs that is booting the latest mainline (3541833fd1f2) causes object debugging always running out of memory. May you please paste the detail failure log? I have to boot the kernel with only 16 CPUs

ODEBUG: Out of memory. ODEBUG disabled

It is a bit annoying on this aarch64 server with 64 CPUs that is booting the latest mainline (3541833fd1f2) causes object debugging always running out of memory. I have to boot the kernel with only 16 CPUs instead (nr_cpus=16) to make it work. Is it expected that object debugging is not going

ODEBUG: Out of memory. ODEBUG disabled

It is a bit annoying on this aarch64 server with 64 CPUs that is booting the latest mainline (3541833fd1f2) causes object debugging always running out of memory. I have to boot the kernel with only 16 CPUs instead (nr_cpus=16) to make it work. Is it expected that object debugging is not going

[PATCH 3.16 227/366] virtio_console: reset on out of memory

3.16.60-rc1 review patch. If anyone has any objections, please let me know. -- From: "Michael S. Tsirkin" commit 5c60300d68da32ca77f7f978039dc72bfc78b06b upstream. When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the error handl

[PATCH 3.16 227/366] virtio_console: reset on out of memory

3.16.60-rc1 review patch. If anyone has any objections, please let me know. -- From: "Michael S. Tsirkin" commit 5c60300d68da32ca77f7f978039dc72bfc78b06b upstream. When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the error handl

[PATCH 4.16 002/279] Input: synaptics-rmi4 - fix an unchecked out of memory error path

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 839c42273617787318da7baf6151d553108f5e17 ] When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access

[PATCH 4.16 002/279] Input: synaptics-rmi4 - fix an unchecked out of memory error path

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 839c42273617787318da7baf6151d553108f5e17 ] When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access

[PATCH 4.14 002/189] Input: synaptics-rmi4 - fix an unchecked out of memory error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 839c42273617787318da7baf6151d553108f5e17 ] When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access

[PATCH 4.14 002/189] Input: synaptics-rmi4 - fix an unchecked out of memory error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 839c42273617787318da7baf6151d553108f5e17 ] When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access

[PATCH 4.14 27/91] virtio_console: reset on out of memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael S. Tsirkin <m...@redhat.com> commit 5c60300d68da32ca77f7f978039dc72bfc78b06b upstream. When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the

[PATCH 4.14 27/91] virtio_console: reset on out of memory

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael S. Tsirkin commit 5c60300d68da32ca77f7f978039dc72bfc78b06b upstream. When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the error handling is out of spec

[PATCH 4.16 029/113] virtio_console: reset on out of memory

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Michael S. Tsirkin <m...@redhat.com> commit 5c60300d68da32ca77f7f978039dc72bfc78b06b upstream. When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the

[PATCH 4.16 029/113] virtio_console: reset on out of memory

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Michael S. Tsirkin commit 5c60300d68da32ca77f7f978039dc72bfc78b06b upstream. When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the error handling is out of spec

[PATCH 6/6] virtio_console: reset on out of memory

When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the error handling is out of spec: it calls del_vqs without bothering to reset the device first. To fix, call the full cleanup function in this case. Cc: sta...@vger.kernel.org Signed-off-by: Michael S. Tsirkin &l

[PATCH 6/6] virtio_console: reset on out of memory

When out of memory and we can't add ctrl vq buffers, probe fails. Unfortunately the error handling is out of spec: it calls del_vqs without bothering to reset the device first. To fix, call the full cleanup function in this case. Cc: sta...@vger.kernel.org Signed-off-by: Michael S. Tsirkin

Re: [PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

On Mon, Apr 02, 2018 at 05:52:52PM -0700, Andrew Duggan wrote: > > On 04/02/2018 07:03 AM, Christophe JAILLET wrote: > > When extending the rmi_spi buffers, we must check that no out of memory > > error occurs, otherwise we may access data above the currently al

Re: [PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

On Mon, Apr 02, 2018 at 05:52:52PM -0700, Andrew Duggan wrote: > > On 04/02/2018 07:03 AM, Christophe JAILLET wrote: > > When extending the rmi_spi buffers, we must check that no out of memory > > error occurs, otherwise we may access data above the currently al

Re: [PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

Hi Christophe JAILLET. [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 7.5278) The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126, v4.15.15: Build OK!

Re: [PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

Hi Christophe JAILLET. [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 7.5278) The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126, v4.15.15: Build OK!

Re: [PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

On 04/02/2018 07:03 AM, Christophe JAILLET wrote: When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access data above the currently allocated memory. Propagate the error code returned by 'rmi_spi_manage_pools()' instead. Yep

Re: [PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

On 04/02/2018 07:03 AM, Christophe JAILLET wrote: When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access data above the currently allocated memory. Propagate the error code returned by 'rmi_spi_manage_pools()' instead. Yep

[PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access data above the currently allocated memory. Propagate the error code returned by 'rmi_spi_manage_pools()' instead. Signed-off-by: Christophe JAILLET <christophe.jail...@wanadoo

[PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access data above the currently allocated memory. Propagate the error code returned by 'rmi_spi_manage_pools()' instead. Signed-off-by: Christophe JAILLET --- drivers/input/rmi4/rmi_spi.c | 7

Re: kernel panic: Out of memory and no killable processes... (2)

You should CC maintainer to get an answer On Fri 23-03-18 19:40:08, Tetsuo Handa wrote: > On 2018/01/29 2:58, syzbot wrote: > > This bug is generated by a dumb bot. It may contain errors. > > See https://goo.gl/tpsmEJ for details. > > Direct all questions to syzkal...@googlegroups.com. > > > >

Re: kernel panic: Out of memory and no killable processes... (2)

You should CC maintainer to get an answer On Fri 23-03-18 19:40:08, Tetsuo Handa wrote: > On 2018/01/29 2:58, syzbot wrote: > > This bug is generated by a dumb bot. It may contain errors. > > See https://goo.gl/tpsmEJ for details. > > Direct all questions to syzkal...@googlegroups.com. > > > >

Re: kernel panic: Out of memory and no killable processes... (2)

On 2018/01/29 2:58, syzbot wrote: > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkal...@googlegroups.com. > > syzbot will keep track of this bug report. > If you forgot to add the Reported-by tag, once the fix

Re: kernel panic: Out of memory and no killable processes... (2)

On 2018/01/29 2:58, syzbot wrote: > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkal...@googlegroups.com. > > syzbot will keep track of this bug report. > If you forgot to add the Reported-by tag, once the fix

[PATCH v2] staging: vt6656: Remove unnecessary 'out of memory' message

This patch removes the unnecessary out of memory message fixing the following checkpatch.pl warning in usbpipe.c: WARNING: Possible unnecessary 'out of memory' message Signed-off-by: Dileep Sankhla <sankhla.dilee...@gmail.com> --- Change in v2: - changed commit message --- drivers/staging/

[PATCH v2] staging: vt6656: Remove unnecessary 'out of memory' message

This patch removes the unnecessary out of memory message fixing the following checkpatch.pl warning in usbpipe.c: WARNING: Possible unnecessary 'out of memory' message Signed-off-by: Dileep Sankhla --- Change in v2: - changed commit message --- drivers/staging/vt6656/usbpipe.c | 3 --- 1 file

Re: [PATCH] staging: vt6656: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning

On Sat, Feb 10, 2018 at 09:46:18PM +0530, Dileep Sankhla wrote: > Signed-off-by: Dileep Sankhla The subject is too long and you need to have a changelog. regards, dan carpenter

Re: [PATCH] staging: vt6656: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning

On Sat, Feb 10, 2018 at 09:46:18PM +0530, Dileep Sankhla wrote: > Signed-off-by: Dileep Sankhla The subject is too long and you need to have a changelog. regards, dan carpenter

[PATCH] staging: vt6656: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning

Signed-off-by: Dileep Sankhla --- drivers/staging/vt6656/usbpipe.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/staging/vt6656/usbpipe.c b/drivers/staging/vt6656/usbpipe.c index 273176386a51..5bbc56f8779e 100644 --- a/drivers/staging/vt6656/usbpipe.c

[PATCH] staging: vt6656: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning

Signed-off-by: Dileep Sankhla --- drivers/staging/vt6656/usbpipe.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/staging/vt6656/usbpipe.c b/drivers/staging/vt6656/usbpipe.c index 273176386a51..5bbc56f8779e 100644 --- a/drivers/staging/vt6656/usbpipe.c +++

Re: [netfilter-core] kernel panic: Out of memory and no killable processes... (2)

On Wed, Feb 07, 2018 at 11:06:42AM -0800, Andrew Morton wrote: > From: Michal Hocko > Subject: net/netfilter/x_tables.c: remove size check > > Back in 2002 vmalloc used to BUG on too large sizes. We are much better > behaved these days and vmalloc simply returns NULL for those.

Re: [netfilter-core] kernel panic: Out of memory and no killable processes... (2)

On Wed, Feb 07, 2018 at 11:06:42AM -0800, Andrew Morton wrote: > From: Michal Hocko > Subject: net/netfilter/x_tables.c: remove size check > > Back in 2002 vmalloc used to BUG on too large sizes. We are much better > behaved these days and vmalloc simply returns NULL for those. Remove the >

Re: [netfilter-core] kernel panic: Out of memory and no killable processes... (2)

On Wed, 7 Feb 2018 18:44:39 +0100 Pablo Neira Ayuso wrote: > Hi, > > On Wed, Jan 31, 2018 at 09:19:16AM +0100, Michal Hocko wrote: > [...] > > Yeah, we do not BUG but rather fail instead. See __vmalloc_node_range. > > My excavation tools pointed me to "VM: Rework vmalloc

  1   2   3   4   5   6   7   8   >