Re: WARN in __mark_inode_dirty when mounting a filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 11/23/2015 11:21 PM, Tejun Heo wrote:
> Hello,
> 
> On Mon, Nov 23, 2015 at 05:40:36PM +0200, Nikolay Borisov wrote:
>> Hello Tejun, 
>>
>> On one of my servers I recently hit the following warn: 
>>
>> 182317.101584] ------------[ cut here ]------------
>> [182317.101753] WARNING: CPU: 7 PID: 13192 at fs/fs-writeback.c:2080 __mark_inode_dirty+0x20a/0x350()
>> [182317.102032] bdi-block not registered
>> [182317.102192] Kernel panic - not syncing: panic_on_warn set ...
>>                 
>> [182317.102474] CPU: 7 PID: 13192 Comm: mount Not tainted 4.2.5-vanilla1 #1
> 
> Is the problem reproducible?  If so, can you please see whether the
> following patch makes any difference?
> 
>  http://lkml.kernel.org/g/1448054554-24138-1-git-send-email-idryomov@xxxxxxxxx

Tested-by: Nikolay Borisov (kernel@xxxxxxxx)


> 
> Thanks.
> 
--
To unsubscribe from this list: send the line "unsubscribe cgroups" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux