Re: kernel 4.1.9: networking hangs with rcu_preempt self-detected stall, 4.1.8 works; was: Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-10-01 Thread Holger Hoffstätte
, meaning it's not any of these two patches: >> [PATCH 4.1 124/159] net: do not process device backlog during unregistration >> [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog >> >> I'll be offline for a half+ day, I'll look into bisecting when

kernel 4.1.9: networking hangs with rcu_preempt self-detected stall, 4.1.8 works; was: Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-10-01 Thread Wolfgang Walter
124/159] net: do not process device backlog during unregistration > [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog > > I'll be offline for a half+ day, I'll look into bisecting when back if > nobody has figured it out by then. > -- > To unsubscri

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-29 Thread Zdenek Kaspar
o not process device backlog during unregistration > [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog > > I'll be offline for a half+ day, I'll look into bisecting when back if > nobody has figured it out by then. After I noticed your crash I did ran some tes

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-29 Thread Julian Anastasov
Hello, On Tue, 29 Sep 2015, Andre Tomt wrote: > On 29. sep. 2015 10:39, Andre Tomt (LKML) wrote: > > I just had another hang with it reverted on two different guests.. > > However it took nearly 6 hours rather than the usual "few minutes" for > > these two. So now I'm a little unsure abo

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-29 Thread Andre Tomt
On 29. sep. 2015 12:21, Andre Tomt wrote: > Meanwhile I'll revert both the mentioned net patches and see how it goes. So that blew up as well, meaning it's not any of these two patches: [PATCH 4.1 124/159] net: do not process device backlog during unregistration [PATCH 4.1 125/1

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-29 Thread Andre Tomt
On 29. sep. 2015 10:39, Andre Tomt (LKML) wrote: > I just had another hang with it reverted on two different guests.. > However it took nearly 6 hours rather than the usual "few minutes" for > these two. So now I'm a little unsure about my initial conclusions. > > On 29. sep. 2015 09:40, Julian An

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-29 Thread Julian Anastasov
Hello, On Tue, 29 Sep 2015, Andre Tomt (LKML) wrote: > On 26. sep. 2015 22:56, Greg Kroah-Hartman wrote: > > 4.1-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Julian Anastasov > > > > [ Upstream commit 2c17d27c36dcce2b6b

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-28 Thread Andre Tomt (LKML)
On 26. sep. 2015 22:56, Greg Kroah-Hartman wrote: 4.1-stable review patch. If anyone has any objections, please let me know. -- From: Julian Anastasov [ Upstream commit 2c17d27c36dcce2b6bf689f41a46b9e909877c21 ] Incoming packet should be either in backlog queue or in RCU rea

[PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

2015-09-26 Thread Greg Kroah-Hartman
4.1-stable review patch. If anyone has any objections, please let me know. -- From: Julian Anastasov [ Upstream commit 2c17d27c36dcce2b6bf689f41a46b9e909877c21 ] Incoming packet should be either in backlog queue or in RCU read-side section. Otherwise, the final sequence of flu