Messages in this thread | | | From | OGAWA Hirofumi <> | 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 |
| |
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>
| |