Re: linux-next: not-present page at swap_vma_readahead()

2020-07-19 Thread Huang, Ying
Qian Cai writes: > On Mon, Jul 20, 2020 at 03:32:59AM +, Huang, Ying wrote: >> Thanks! Can you try the dbg patch attached? That will print more debugging >> information when abnormal PTE pointer is detected. > > Here with both of your patches applied, > > [ 183.627876][ T3959] ra_info:

Re: linux-next: not-present page at swap_vma_readahead()

2020-07-19 Thread Qian Cai
On Mon, Jul 20, 2020 at 03:32:59AM +, Huang, Ying wrote: > Thanks! Can you try the dbg patch attached? That will print more debugging > information when abnormal PTE pointer is detected. Here with both of your patches applied, [ 183.627876][ T3959] ra_info: 8, 3, 4, aabe3209 [

RE: linux-next: not-present page at swap_vma_readahead()

2020-07-19 Thread Huang, Ying
; Minchan Kim; Hugh Dickins; Andrew Morton Subject: Re: linux-next: not-present page at swap_vma_readahead() On Mon, Jul 20, 2020 at 12:37:30AM +, Huang, Ying wrote: > Hi, > > Sorry for late reply. I found a problem in the swap readahead code. Can you > help to check whethe

Re: linux-next: not-present page at swap_vma_readahead()

2020-07-19 Thread Qian Cai
On Mon, Jul 20, 2020 at 12:37:30AM +, Huang, Ying wrote: > Hi, > > Sorry for late reply. I found a problem in the swap readahead code. Can you > help to check whether it can fix this? Unfortunately, I can still reproduce it easily after applied the patch. # git clone

RE: linux-next: not-present page at swap_vma_readahead()

2020-07-19 Thread Huang, Ying
; Minchan Kim; Hugh Dickins; Andrew Morton Subject: Re: linux-next: not-present page at swap_vma_readahead() On Wed, Apr 15, 2020 at 10:01:53AM +0800, Huang, Ying wrote: > Qian Cai writes: > > >> On Apr 14, 2020, at 10:32 AM, Qian Cai wrote: > >> > >&

Re: linux-next: not-present page at swap_vma_readahead()

2020-06-15 Thread Qian Cai
On Wed, Apr 15, 2020 at 10:01:53AM +0800, Huang, Ying wrote: > Qian Cai writes: > > >> On Apr 14, 2020, at 10:32 AM, Qian Cai wrote: > >> > >> Fuzzers are unhappy. Thoughts? > > > > This is rather to reproduce. All the traces so far are from > > copy_from_user() to trigger a page fault, > >