Re: [PATCH 1/1] - Fix reiserfs WARNING in dquot_writeback_dquots

2017-06-22 Thread Jeff Mahoney
On 6/14/17 11:27 PM, Tim Savannah wrote: > Any comments? Can we get this merged, or some variation? It affects a > lot more than just all my machines. Google shows this traceback is > occurring for others as well. Hi Tim - This patch was merged for 4.12: commit 1e0e653f1136a413a9969e5d0d548ee649

Re: [PATCH 1/1] - Fix reiserfs WARNING in dquot_writeback_dquots

2017-06-14 Thread Tim Savannah
Any comments? Can we get this merged, or some variation? It affects a lot more than just all my machines. Google shows this traceback is occurring for others as well. On Mon, May 29, 2017 at 12:57 AM, Tim Savannah wrote: > Oops, sent last one without patch on accident. Attached this time. > > > T

[PATCH 1/1] - Fix reiserfs WARNING in dquot_writeback_dquots

2017-05-28 Thread Tim Savannah
Oops, sent last one without patch on accident. Attached this time. This has been happening for me since 4.10 dquot_writeback_dquots expects a lock to be held on super_block->s_umount , and reiserfs_sync_fs, which calls dquot_writeback_dquots, does not obtain such a lock. Thus, the following wa

[PATCH 1/1] - Fix reiserfs WARNING in dquot_writeback_dquots

2017-05-28 Thread Tim Savannah
This has been happening for me since 4.10 dquot_writeback_dquots expects a lock to be held on super_block->s_umount , and reiserfs_sync_fs, which calls dquot_writeback_dquots, does not obtain such a lock. Thus, the following warning is generated: [Sun May 28 04:58:06 2017] [ cut her