Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1278067

Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()

From OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Newsgroups linux.kernel
Subject Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
Date 2015-11-26 09:30 +0100
Message-ID <qz06d-2tb-5@gated-at.bofh.it> (permalink)
References <qxUcy-7gY-13@gated-at.bofh.it> <qy7Mu-7WJ-3@gated-at.bofh.it> <qygPM-5uK-21@gated-at.bofh.it> <qyQgy-3rg-19@gated-at.bofh.it> <qyZWy-2oi-35@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() Vegard Nossum <vegard.nossum@oracle.com> - 2015-11-23 09:00 +0100
  Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() Richard Weinberger <richard@nod.at> - 2015-11-23 23:30 +0100
    Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() Vegard Nossum <vegard.nossum@oracle.com> - 2015-11-24 09:10 +0100
      Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - 2015-11-25 23:00 +0100
        Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() Vegard Nossum <vegard.nossum@oracle.com> - 2015-11-26 09:20 +0100
          Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - 2015-11-26 09:30 +0100
          Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50() OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - 2015-11-26 09:40 +0100

csiph-web