From: Nikolay Borisov <kernel-6AxghH7DbtA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
Subject: Re: WARN in __mark_inode_dirty when mounting a filesystem
Date: Fri, 11 Dec 2015 12:26:24 +0200 [thread overview]
Message-ID: <566AA4D0.9060202@kyup.com> (raw)
In-Reply-To: <20151123212130.GE19072-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Tested-by: Nikolay Borisov (kernel-6AxghH7DbtA@public.gmane.org)
>
> Thanks.
>
prev parent reply other threads:[~2015-12-11 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 15:40 WARN in __mark_inode_dirty when mounting a filesystem Nikolay Borisov
[not found] ` <56533374.2090807-6AxghH7DbtA@public.gmane.org>
2015-11-23 21:21 ` Tejun Heo
[not found] ` <20151123212130.GE19072-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-12-11 10:26 ` Nikolay Borisov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566AA4D0.9060202@kyup.com \
--to=kernel-6axghh7dbta@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.