lkml.org 
[lkml]   [2015]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectWARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
Date
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.

Also happens on 3.13.0 Ubuntu trusty kernel.


Vegard
[unhandled content-type:application/x-bzip]
\
 
 \ /
  Last update: 2015-11-23 09:21    [W:0.740 / U:0.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site