Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-09 Thread zhong jiang
On 2017/5/9 23:46, Rik van Riel wrote: > On Thu, 2017-05-04 at 10:28 +0800, zhong jiang wrote: >> On 2017/5/4 2:46, Rik van Riel wrote: >>> However, it is not as easy as simply checking the >>> end against __pa(high_memory). Some systems have >>> non-contiguous physical memory ranges, with gaps

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-09 Thread zhong jiang
On 2017/5/9 23:46, Rik van Riel wrote: > On Thu, 2017-05-04 at 10:28 +0800, zhong jiang wrote: >> On 2017/5/4 2:46, Rik van Riel wrote: >>> However, it is not as easy as simply checking the >>> end against __pa(high_memory). Some systems have >>> non-contiguous physical memory ranges, with gaps

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-09 Thread Xishi Qiu
On 2017/5/9 23:46, Rik van Riel wrote: > On Thu, 2017-05-04 at 10:28 +0800, zhong jiang wrote: >> On 2017/5/4 2:46, Rik van Riel wrote: > >>> However, it is not as easy as simply checking the >>> end against __pa(high_memory). Some systems have >>> non-contiguous physical memory ranges, with

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-09 Thread Xishi Qiu
On 2017/5/9 23:46, Rik van Riel wrote: > On Thu, 2017-05-04 at 10:28 +0800, zhong jiang wrote: >> On 2017/5/4 2:46, Rik van Riel wrote: > >>> However, it is not as easy as simply checking the >>> end against __pa(high_memory). Some systems have >>> non-contiguous physical memory ranges, with

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-09 Thread Rik van Riel
On Thu, 2017-05-04 at 10:28 +0800, zhong jiang wrote: > On 2017/5/4 2:46, Rik van Riel wrote: > > However, it is not as easy as simply checking the > > end against __pa(high_memory). Some systems have > > non-contiguous physical memory ranges, with gaps > > of invalid addresses in-between. > >  

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-09 Thread Rik van Riel
On Thu, 2017-05-04 at 10:28 +0800, zhong jiang wrote: > On 2017/5/4 2:46, Rik van Riel wrote: > > However, it is not as easy as simply checking the > > end against __pa(high_memory). Some systems have > > non-contiguous physical memory ranges, with gaps > > of invalid addresses in-between. > >  

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-03 Thread zhong jiang
On 2017/5/4 2:46, Rik van Riel wrote: > On Tue, 2017-05-02 at 13:54 -0700, David Rientjes wrote: > >>> diff --git a/drivers/char/mem.c b/drivers/char/mem.c >>> index 7e4a9d1..3a765e02 100644 >>> --- a/drivers/char/mem.c >>> +++ b/drivers/char/mem.c >>> @@ -55,7 +55,7 @@ static inline int >>

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-03 Thread zhong jiang
On 2017/5/4 2:46, Rik van Riel wrote: > On Tue, 2017-05-02 at 13:54 -0700, David Rientjes wrote: > >>> diff --git a/drivers/char/mem.c b/drivers/char/mem.c >>> index 7e4a9d1..3a765e02 100644 >>> --- a/drivers/char/mem.c >>> +++ b/drivers/char/mem.c >>> @@ -55,7 +55,7 @@ static inline int >>

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-03 Thread Rik van Riel
On Tue, 2017-05-02 at 13:54 -0700, David Rientjes wrote: > > diff --git a/drivers/char/mem.c b/drivers/char/mem.c > > index 7e4a9d1..3a765e02 100644 > > --- a/drivers/char/mem.c > > +++ b/drivers/char/mem.c > > @@ -55,7 +55,7 @@ static inline int > valid_phys_addr_range(phys_addr_t addr, size_t

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-03 Thread Rik van Riel
On Tue, 2017-05-02 at 13:54 -0700, David Rientjes wrote: > > diff --git a/drivers/char/mem.c b/drivers/char/mem.c > > index 7e4a9d1..3a765e02 100644 > > --- a/drivers/char/mem.c > > +++ b/drivers/char/mem.c > > @@ -55,7 +55,7 @@ static inline int > valid_phys_addr_range(phys_addr_t addr, size_t

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-03 Thread zhong jiang
On 2017/5/3 4:54, David Rientjes wrote: > On Thu, 27 Apr 2017, zhongjiang wrote: > >> From: zhong jiang >> >> Recently, I found the following issue, it will result in the panic. >> >> [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 >> [ 168.745039] PGD

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-03 Thread zhong jiang
On 2017/5/3 4:54, David Rientjes wrote: > On Thu, 27 Apr 2017, zhongjiang wrote: > >> From: zhong jiang >> >> Recently, I found the following issue, it will result in the panic. >> >> [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 >> [ 168.745039] PGD 61f4a1067 >> [

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-02 Thread David Rientjes
On Thu, 27 Apr 2017, zhongjiang wrote: > From: zhong jiang > > Recently, I found the following issue, it will result in the panic. > > [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 > [ 168.745039] PGD 61f4a1067 > [ 168.745040] PUD 61ab19067 > [

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-02 Thread David Rientjes
On Thu, 27 Apr 2017, zhongjiang wrote: > From: zhong jiang > > Recently, I found the following issue, it will result in the panic. > > [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 > [ 168.745039] PGD 61f4a1067 > [ 168.745040] PUD 61ab19067 > [ 168.747730] PMD 61fb8b067

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-01 Thread zhong jiang
ping anyone has any objections. On 2017/4/27 19:49, zhongjiang wrote: > From: zhong jiang > > Recently, I found the following issue, it will result in the panic. > > [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 > [ 168.745039] PGD 61f4a1067 > [

Re: [RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-05-01 Thread zhong jiang
ping anyone has any objections. On 2017/4/27 19:49, zhongjiang wrote: > From: zhong jiang > > Recently, I found the following issue, it will result in the panic. > > [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 > [ 168.745039] PGD 61f4a1067 > [ 168.745040] PUD

[RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-04-27 Thread zhongjiang
From: zhong jiang Recently, I found the following issue, it will result in the panic. [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 [ 168.745039] PGD 61f4a1067 [ 168.745040] PUD 61ab19067 [ 168.747730] PMD 61fb8b067 [ 168.750418] PTE

[RESENT PATCH] x86/mem: fix the offset overflow when read/write mem

2017-04-27 Thread zhongjiang
From: zhong jiang Recently, I found the following issue, it will result in the panic. [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002 [ 168.745039] PGD 61f4a1067 [ 168.745040] PUD 61ab19067 [ 168.747730] PMD 61fb8b067 [ 168.750418] PTE 80001225 [ 168.753109] [