From: Richard Weinberger <richard@nod.at>
To: Vegard Nossum <vegard.nossum@oracle.com>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
Date: Mon, 23 Nov 2015 23:21:32 +0100 [thread overview]
Message-ID: <5653916C.7060601@nod.at> (raw)
In-Reply-To: <5652C676.8040207@oracle.com>
Am 23.11.2015 um 08:55 schrieb Vegard Nossum:
> Hi,
>
> 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()
> CPU: 0 PID: 913 Comm: a.out Not tainted 4.2.5+ #39
> Stack:
> e0931b50 60075412 e13981e8 00000009
> 00000000 605cc684 e0931b60 605cf637
> e0931bc0 60040f6d e0931ba0 6011e12b
> Call Trace:
> [<60029f3b>] show_stack+0xdb/0x1a0
> [<605cf637>] dump_stack+0x2a/0x2c
> [<60040f6d>] warn_slowpath_common+0x9d/0xf0
> [<6004114c>] warn_slowpath_null+0x1c/0x20
> [<6011e12b>] drop_nlink+0x4b/0x50
> [<601e9e2f>] vfat_rename+0x56f/0x800
> [<60113dd2>] vfs_rename+0x9a2/0x9d0
> [<60114439>] SyS_renameat2+0x639/0x690
> [<601144d0>] SyS_rename+0x20/0x30
> [<6002c5ce>] handle_syscall+0x6e/0xa0
> [<6003a911>] userspace+0x4f1/0x5e0
>
> To trigger it, you have to do a rename("/mnt/a/b/1", "/mnt/1"), where
> /mnt is your mountpoint.
Not here. All I get is:
FAT-fs (ubdb): Corrupted directory (i_pos 244)
Did you something before the rename()?
Thanks,
//richard
next prev parent reply other threads:[~2015-11-23 22:21 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 [this message]
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
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=5653916C.7060601@nod.at \
--to=richard@nod.at \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--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 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.