Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-04-08 Thread Hugh Dickins
On Mon, 8 Apr 2019, Konstantin Khlebnikov wrote: > > I suppose your solution will wait for wakeup from shmem_evict_inode()? No, it's the other way round: shmem_unuse() gets on with its work without delay, shmem_evict_inode() waits until the stop_eviction count has gone down to zero, saying

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-04-08 Thread Konstantin Khlebnikov
On 08.04.2019 9:05, Hugh Dickins wrote: On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote: On 05.04.2019 5:12, Hugh Dickins wrote: Hi Alex, could you please give the patch below a try? It fixes a problem, but I'm not sure that it's your problem - please let us know. I've not yet written up the

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-04-08 Thread Hugh Dickins
On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote: > On 05.04.2019 5:12, Hugh Dickins wrote: > > Hi Alex, could you please give the patch below a try? It fixes a > > problem, but I'm not sure that it's your problem - please let us know. > > > > I've not yet written up the commit description, and

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-04-05 Thread Konstantin Khlebnikov
On 05.04.2019 5:12, Hugh Dickins wrote: On Tue, 2 Apr 2019, Hugh Dickins wrote: On Sun, 31 Mar 2019, Hugh Dickins wrote: On Sun, 31 Mar 2019, Alex Xu (Hello71) wrote: Excerpts from Vineeth Pillai's message of March 25, 2019 6:08 pm: On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) wrote:

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-04-04 Thread Hugh Dickins
On Tue, 2 Apr 2019, Hugh Dickins wrote: > On Sun, 31 Mar 2019, Hugh Dickins wrote: > > On Sun, 31 Mar 2019, Alex Xu (Hello71) wrote: > > > Excerpts from Vineeth Pillai's message of March 25, 2019 6:08 pm: > > > > On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) > > > > wrote: > > > >> > > > >>

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-04-02 Thread Hugh Dickins
On Sun, 31 Mar 2019, Hugh Dickins wrote: > On Sun, 31 Mar 2019, Alex Xu (Hello71) wrote: > > Excerpts from Vineeth Pillai's message of March 25, 2019 6:08 pm: > > > On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) > > > wrote: > > >> > > >> I get this BUG in 5.1-rc1 sometimes when powering off

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-03-31 Thread Hugh Dickins
On Sun, 31 Mar 2019, Alex Xu (Hello71) wrote: > Excerpts from Vineeth Pillai's message of March 25, 2019 6:08 pm: > > On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) > > wrote: > >> > >> I get this BUG in 5.1-rc1 sometimes when powering off the machine. I > >> suspect my setup erroneously

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-03-31 Thread Alex Xu (Hello71)
Excerpts from Vineeth Pillai's message of March 25, 2019 6:08 pm: > On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) wrote: >> >> I get this BUG in 5.1-rc1 sometimes when powering off the machine. I >> suspect my setup erroneously executes two swapoff+cryptsetup close >> operations

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-03-25 Thread Vineeth Pillai
On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) wrote: > > I get this BUG in 5.1-rc1 sometimes when powering off the machine. I > suspect my setup erroneously executes two swapoff+cryptsetup close > operations simultaneously, so a race condition is triggered. > > I am using a single swap on a

shmem_recalc_inode: unable to handle kernel NULL pointer dereference

2019-03-24 Thread Alex Xu (Hello71)
I get this BUG in 5.1-rc1 sometimes when powering off the machine. I suspect my setup erroneously executes two swapoff+cryptsetup close operations simultaneously, so a race condition is triggered. I am using a single swap on a plain dm-crypt device on a MBR partition on a SATA drive. I think