Re: Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Darrick J. Wong
On Wed, Sep 30, 2015 at 09:13:38PM +0300, Nikolay Borisov wrote: > Hello, > > > Well, I guess I can do that the thing is the current scenario was like > that. Anyway, > I thought something like what you describe could be happening. I saw > your patch and I'm > going to test it tomorrow. But I

Re: Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Nikolay Borisov
Hello, Well, I guess I can do that the thing is the current scenario was like that. Anyway, I thought something like what you describe could be happening. I saw your patch and I'm going to test it tomorrow. But I think the patch needs to be tagged for stable since there is going to be effort to

Re: Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Darrick J. Wong
On Wed, Sep 30, 2015 at 04:35:49PM +0300, Nikolay Borisov wrote: > Hello, > > Today a colleague was testing something and while doing so he observed > the following crash: > > jbd2_journal_bmap: journal block not found at offset 67 on dm-26-8 > Aborting journal on device dm-26-8. > BUG:

Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Nikolay Borisov
Hello, Today a colleague was testing something and while doing so he observed the following crash: jbd2_journal_bmap: journal block not found at offset 67 on dm-26-8 Aborting journal on device dm-26-8. BUG: unable to handle kernel NULL pointer dereference at (null) IP: []

Re: Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Darrick J. Wong
On Wed, Sep 30, 2015 at 09:13:38PM +0300, Nikolay Borisov wrote: > Hello, > > > Well, I guess I can do that the thing is the current scenario was like > that. Anyway, > I thought something like what you describe could be happening. I saw > your patch and I'm > going to test it tomorrow. But I

Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Nikolay Borisov
Hello, Today a colleague was testing something and while doing so he observed the following crash: jbd2_journal_bmap: journal block not found at offset 67 on dm-26-8 Aborting journal on device dm-26-8. BUG: unable to handle kernel NULL pointer dereference at (null) IP: []

Re: Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Nikolay Borisov
Hello, Well, I guess I can do that the thing is the current scenario was like that. Anyway, I thought something like what you describe could be happening. I saw your patch and I'm going to test it tomorrow. But I think the patch needs to be tagged for stable since there is going to be effort to

Re: Crash in jbd2_chksum due to null journal->j_chksum_driver

2015-09-30 Thread Darrick J. Wong
On Wed, Sep 30, 2015 at 04:35:49PM +0300, Nikolay Borisov wrote: > Hello, > > Today a colleague was testing something and while doing so he observed > the following crash: > > jbd2_journal_bmap: journal block not found at offset 67 on dm-26-8 > Aborting journal on device dm-26-8. > BUG: