From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Richard Weinberger <richard@nod.at>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
Date: Thu, 26 Nov 2015 17:26:14 +0900 [thread overview]
Message-ID: <87two96uah.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <5656BEE8.4030001@oracle.com> (Vegard Nossum's message of "Thu, 26 Nov 2015 09:12:24 +0100")
Vegard Nossum <vegard.nossum@oracle.com> writes:
> On 11/25/2015 10:54 PM, OGAWA Hirofumi wrote:
>> Vegard Nossum <vegard.nossum@oracle.com> writes:
>>
>>> On 11/23/2015 11:21 PM, Richard Weinberger wrote:
>>>> Am 23.11.2015 um 08:55 schrieb Vegard Nossum:
>>>>> With the attached vfat disk image (fuzzed), I get the following WARNING:
>>>>>
>>>>> WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
>
> [...]
>
>>
>> Can you try this one?
>>
>
> That seems to fix the problem here, thanks!
>
> The last potential issue I'm seeing (completely unrelated to your patch)
> is this:
>
> [ 340.610000] VFS: Lookup of '1' in vfat loop0 would have caused loop
> [ 354.360000] d_splice_alias: 1104 callbacks suppressed
> [ 354.360000] VFS: Lookup of '1' in vfat loop0 would have caused loop
>
> Is that worth investigating closer?
It looks like corruption detected with ratelimited printk (at vfs
level. dir is hardlink of ancestor). IOW, it looks like intended
behavior.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2015-11-26 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 7:55 WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() Vegard Nossum
2015-11-23 22:21 ` Richard Weinberger
2015-11-24 8:08 ` Vegard Nossum
2015-11-25 21:54 ` OGAWA Hirofumi
2015-11-26 8:12 ` Vegard Nossum
2015-11-26 8:26 ` OGAWA Hirofumi [this message]
2015-11-26 8:30 ` OGAWA Hirofumi
2015-12-13 22:19 ` Vegard Nossum
2015-12-14 22:19 ` Andrew Morton
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=87two96uah.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=vegard.nossum@oracle.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox