Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Jan Kara
On Tue 17-04-18 16:15:07, Pavlos Parissis wrote: > On 17/04/2018 04:02 μμ, Jan Kara wrote: > > On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: > >> In one of our production servers where we run kernel version 4.14.32, I > >> noticed > >> the following: > > > > OK, I was looking into this for

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Jan Kara
On Tue 17-04-18 16:15:07, Pavlos Parissis wrote: > On 17/04/2018 04:02 μμ, Jan Kara wrote: > > On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: > >> In one of our production servers where we run kernel version 4.14.32, I > >> noticed > >> the following: > > > > OK, I was looking into this for

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Pavlos Parissis
On 17/04/2018 04:02 μμ, Jan Kara wrote: > On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: >> In one of our production servers where we run kernel version 4.14.32, I >> noticed >> the following: > > OK, I was looking into this for some time and couldn't find a problem in > 4.14.32 code. Can you

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Pavlos Parissis
On 17/04/2018 04:02 μμ, Jan Kara wrote: > On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: >> In one of our production servers where we run kernel version 4.14.32, I >> noticed >> the following: > > OK, I was looking into this for some time and couldn't find a problem in > 4.14.32 code. Can you

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Jan Kara
On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: > In one of our production servers where we run kernel version 4.14.32, I > noticed > the following: OK, I was looking into this for some time and couldn't find a problem in 4.14.32 code. Can you try running a kernel with CONFIG_DEBUG_SLAB and

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Jan Kara
On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: > In one of our production servers where we run kernel version 4.14.32, I > noticed > the following: OK, I was looking into this for some time and couldn't find a problem in 4.14.32 code. Can you try running a kernel with CONFIG_DEBUG_SLAB and

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Jan Kara
Hi, On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: > In one of our production servers where we run kernel version 4.14.32, I > noticed > the following: Thanks for the report! So I believe this is the same underlying problem as for the softlockups you were observing - there I believe the

Re: kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Jan Kara
Hi, On Tue 17-04-18 12:39:32, Pavlos Parissis wrote: > In one of our production servers where we run kernel version 4.14.32, I > noticed > the following: Thanks for the report! So I believe this is the same underlying problem as for the softlockups you were observing - there I believe the

kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Pavlos Parissis
Hi, In one of our production servers where we run kernel version 4.14.32, I noticed the following: [138630.417246] cache_from_obj: Wrong slab cache. fsnotify_mark_connector but object is from kmalloc-2048(361:anycast-healthchecker.service) [138630.477075] [ cut here

kernel 4.14.x crash around fsnotify_mark_connector

2018-04-17 Thread Pavlos Parissis
Hi, In one of our production servers where we run kernel version 4.14.32, I noticed the following: [138630.417246] cache_from_obj: Wrong slab cache. fsnotify_mark_connector but object is from kmalloc-2048(361:anycast-healthchecker.service) [138630.477075] [ cut here