Re: mm: shm: hang in shmem_fallocate

2014-07-09 Thread Hugh Dickins
On Wed, 9 Jul 2014, Hugh Dickins wrote: > On Wed, 9 Jul 2014, Johannes Weiner wrote: > > On Thu, Jun 26, 2014 at 10:36:20PM -0700, Hugh Dickins wrote: > > > Hannes, a question for you please, I just could not make up my mind. > > > In mm/truncate.c truncate_inode_pages_range(), what should be done

Re: mm: shm: hang in shmem_fallocate

2014-07-09 Thread Hugh Dickins
On Wed, 9 Jul 2014, Johannes Weiner wrote: > On Thu, Jun 26, 2014 at 10:36:20PM -0700, Hugh Dickins wrote: > > Hannes, a question for you please, I just could not make up my mind. > > In mm/truncate.c truncate_inode_pages_range(), what should be done > > with a failed clear_exceptional_entry() in t

Re: mm: shm: hang in shmem_fallocate

2014-07-09 Thread Johannes Weiner
Hi Hugh, On Thu, Jun 26, 2014 at 10:36:20PM -0700, Hugh Dickins wrote: > Hannes, a question for you please, I just could not make up my mind. > In mm/truncate.c truncate_inode_pages_range(), what should be done > with a failed clear_exceptional_entry() in the case of hole-punch? > Is that case cur

Re: mm: shm: hang in shmem_fallocate

2014-07-01 Thread Hugh Dickins
On Tue, 1 Jul 2014, Vlastimil Babka wrote: > On 06/27/2014 07:36 AM, Hugh Dickins wrote:> [Cc Johannes: at the end I have > a particular question for you] > > On Thu, 26 Jun 2014, Vlastimil Babka wrote: > > > > > > Thanks, I didn't notice that. Do I understand correctly that this could > > > mean

Re: mm: shmem: hang in shmem_fault (WAS: mm: shm: hang in shmem_fallocate)

2014-07-01 Thread Hugh Dickins
On Tue, 1 Jul 2014, Sasha Levin wrote: > Hi Hugh, > > I've been observing a very nonspecific hang involving some mutexes from fs/ > but > without any lockdep output or a concrete way to track it down. > > It seems that today was my lucky day, and after enough tinkering I've managed > to get out

mm: shmem: hang in shmem_fault (WAS: mm: shm: hang in shmem_fallocate)

2014-07-01 Thread Sasha Levin
Hi Hugh, I've been observing a very nonspecific hang involving some mutexes from fs/ but without any lockdep output or a concrete way to track it down. It seems that today was my lucky day, and after enough tinkering I've managed to get output out of lockdep, which pointed me to shmem: [ 1871.98

Re: mm: shm: hang in shmem_fallocate

2014-07-01 Thread Vlastimil Babka
On 06/27/2014 07:36 AM, Hugh Dickins wrote:> [Cc Johannes: at the end I have a particular question for you] On Thu, 26 Jun 2014, Vlastimil Babka wrote: On 06/26/2014 12:36 AM, Hugh Dickins wrote: On Tue, 24 Jun 2014, Vlastimil Babka wrote: Sorry for the slow response: I have got confused, lea

Re: mm: shm: hang in shmem_fallocate

2014-06-28 Thread Sasha Levin
On 06/27/2014 02:03 PM, Hugh Dickins wrote: > On Fri, 27 Jun 2014, Sasha Levin wrote: >> On 06/27/2014 01:59 AM, Hugh Dickins wrote: > First, this: > > [ 681.267487] BUG: unable to handle kernel paging request at > ea0003480048 > [ 681.268621] IP: zap_pte_range (mm/memory

Re: mm: shm: hang in shmem_fallocate

2014-06-27 Thread Hugh Dickins
On Fri, 27 Jun 2014, Sasha Levin wrote: > On 06/27/2014 01:59 AM, Hugh Dickins wrote: > >> > First, this: > >> > > >> > [ 681.267487] BUG: unable to handle kernel paging request at > >> > ea0003480048 > >> > [ 681.268621] IP: zap_pte_range (mm/memory.c:1132) > > Weird, I don't think we've s

Re: mm: shm: hang in shmem_fallocate

2014-06-27 Thread Sasha Levin
On 06/27/2014 01:59 AM, Hugh Dickins wrote: >> > First, this: >> > >> > [ 681.267487] BUG: unable to handle kernel paging request at >> > ea0003480048 >> > [ 681.268621] IP: zap_pte_range (mm/memory.c:1132) > Weird, I don't think we've seen anything like that before, have we? > I'm pretty s

Re: mm: shm: hang in shmem_fallocate

2014-06-26 Thread Hugh Dickins
On Thu, 26 Jun 2014, Sasha Levin wrote: > On 06/25/2014 06:36 PM, Hugh Dickins wrote: > > Sasha, may I trespass on your time, and ask you to revert the previous > > patch from your tree, and give this patch below a try? I am very > > interested to learn if in fact it fixes it for you (as it did fo

Re: mm: shm: hang in shmem_fallocate

2014-06-26 Thread Hugh Dickins
[Cc Johannes: at the end I have a particular question for you] On Thu, 26 Jun 2014, Vlastimil Babka wrote: > On 06/26/2014 12:36 AM, Hugh Dickins wrote: > > On Tue, 24 Jun 2014, Vlastimil Babka wrote: > > > > Sorry for the slow response: I have got confused, learnt more, and > > changed my mind,

Re: mm: shm: hang in shmem_fallocate

2014-06-26 Thread Vlastimil Babka
On 06/26/2014 11:14 AM, Vlastimil Babka wrote: On 06/26/2014 12:36 AM, Hugh Dickins wrote: On Tue, 24 Jun 2014, Vlastimil Babka wrote: On 06/16/2014 04:29 AM, Hugh Dickins wrote: On Thu, 12 Jun 2014, Sasha Levin wrote: On 02/09/2014 08:41 PM, Sasha Levin wrote: On 02/08/2014 10:25 PM, Hugh D

Re: mm: shm: hang in shmem_fallocate

2014-06-26 Thread Vlastimil Babka
On 06/26/2014 12:36 AM, Hugh Dickins wrote: On Tue, 24 Jun 2014, Vlastimil Babka wrote: On 06/16/2014 04:29 AM, Hugh Dickins wrote: On Thu, 12 Jun 2014, Sasha Levin wrote: On 02/09/2014 08:41 PM, Sasha Levin wrote: On 02/08/2014 10:25 PM, Hugh Dickins wrote: Would trinity be likely to have a

Re: mm: shm: hang in shmem_fallocate

2014-06-25 Thread Hugh Dickins
On Tue, 24 Jun 2014, Vlastimil Babka wrote: > On 06/16/2014 04:29 AM, Hugh Dickins wrote: > > On Thu, 12 Jun 2014, Sasha Levin wrote: > >> On 02/09/2014 08:41 PM, Sasha Levin wrote: > >>> On 02/08/2014 10:25 PM, Hugh Dickins wrote: > Would trinity be likely to have a thread or process repeated

Re: mm: shm: hang in shmem_fallocate

2014-06-24 Thread Vlastimil Babka
On 06/16/2014 04:29 AM, Hugh Dickins wrote: > On Thu, 12 Jun 2014, Sasha Levin wrote: >> On 02/09/2014 08:41 PM, Sasha Levin wrote: >>> On 02/08/2014 10:25 PM, Hugh Dickins wrote: Would trinity be likely to have a thread or process repeatedly faulting in pages from the hole while it is be

Re: mm: shm: hang in shmem_fallocate

2014-06-17 Thread Sasha Levin
On 06/15/2014 10:29 PM, Hugh Dickins wrote: > On Thu, 12 Jun 2014, Sasha Levin wrote: >> > On 02/09/2014 08:41 PM, Sasha Levin wrote: >>> > > On 02/08/2014 10:25 PM, Hugh Dickins wrote: > >> Would trinity be likely to have a thread or process repeatedly > >> faulting > >> in pages f

Re: mm: shm: hang in shmem_fallocate

2014-06-15 Thread Hugh Dickins
On Thu, 12 Jun 2014, Sasha Levin wrote: > On 02/09/2014 08:41 PM, Sasha Levin wrote: > > On 02/08/2014 10:25 PM, Hugh Dickins wrote: > >> Would trinity be likely to have a thread or process repeatedly faulting > >> in pages from the hole while it is being punched? > > > > I can see how trinity wou

Re: mm: shm: hang in shmem_fallocate

2014-06-12 Thread Sasha Levin
On 02/09/2014 08:41 PM, Sasha Levin wrote: > On 02/08/2014 10:25 PM, Hugh Dickins wrote: >> Would trinity be likely to have a thread or process repeatedly faulting >> in pages from the hole while it is being punched? > > I can see how trinity would do that, but just to be certain - Cc davej. > >

Re: mm: shm: hang in shmem_fallocate

2014-02-09 Thread Sasha Levin
On 02/08/2014 10:25 PM, Hugh Dickins wrote: > Would trinity be likely to have a thread or process repeatedly faulting > in pages from the hole while it is being punched? I can see how trinity would do that, but just to be certain - Cc davej. On 02/08/2014 10:25 PM, Hugh Dickins wrote: > Does thi

Re: mm: shm: hang in shmem_fallocate

2014-02-08 Thread Hugh Dickins
On Sat, 8 Feb 2014, Sasha Levin wrote: > On 12/15/2013 11:01 PM, Sasha Levin wrote: > > Hi all, > > > > While fuzzing with trinity inside a KVM tools guest running latest -next, > > I've noticed that > > quite often there's a hang happening inside shmem_fallocate. There are > > several processes s

Re: mm: shm: hang in shmem_fallocate

2014-02-08 Thread Sasha Levin
On 12/15/2013 11:01 PM, Sasha Levin wrote: Hi all, While fuzzing with trinity inside a KVM tools guest running latest -next, I've noticed that quite often there's a hang happening inside shmem_fallocate. There are several processes stuck trying to acquire inode->i_mutex (for more than 2 minute

mm: shm: hang in shmem_fallocate

2013-12-15 Thread Sasha Levin
Hi all, While fuzzing with trinity inside a KVM tools guest running latest -next, I've noticed that quite often there's a hang happening inside shmem_fallocate. There are several processes stuck trying to acquire inode->i_mutex (for more than 2 minutes), while the process that holds it has the