Re: [PATCH AUTOSEL 4.19 13/73] s390/mm: fix mis-accounting of pgtable_bytes

2018-11-30 Thread Martin Schwidefsky
On Wed, 14 Nov 2018 17:21:07 -0500 Sasha Levin wrote: > From: Martin Schwidefsky > > [ Upstream commit e12e4044aede97974feb7f0ed726a5179a32 ] > > In case a fork or a clone system fails in copy_process and the error > handling does the mmput() at the bad_fork_cleanup_mm label, the >

Re: [PATCH AUTOSEL 4.19 13/73] s390/mm: fix mis-accounting of pgtable_bytes

2018-11-30 Thread Martin Schwidefsky
On Wed, 14 Nov 2018 17:21:07 -0500 Sasha Levin wrote: > From: Martin Schwidefsky > > [ Upstream commit e12e4044aede97974feb7f0ed726a5179a32 ] > > In case a fork or a clone system fails in copy_process and the error > handling does the mmput() at the bad_fork_cleanup_mm label, the >

[PATCH AUTOSEL 4.19 13/73] s390/mm: fix mis-accounting of pgtable_bytes

2018-11-14 Thread Sasha Levin
From: Martin Schwidefsky [ Upstream commit e12e4044aede97974feb7f0ed726a5179a32 ] In case a fork or a clone system fails in copy_process and the error handling does the mmput() at the bad_fork_cleanup_mm label, the following warning messages will appear on the console: BUG: non-zero

[PATCH AUTOSEL 4.19 13/73] s390/mm: fix mis-accounting of pgtable_bytes

2018-11-14 Thread Sasha Levin
From: Martin Schwidefsky [ Upstream commit e12e4044aede97974feb7f0ed726a5179a32 ] In case a fork or a clone system fails in copy_process and the error handling does the mmput() at the bad_fork_cleanup_mm label, the following warning messages will appear on the console: BUG: non-zero