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

2015-12-14 Thread Andrew Morton
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:

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

2015-12-14 Thread Andrew Morton
d Nossum <vegard.nos...@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 > >>>

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

2015-12-13 Thread Vegard Nossum
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! Andrew, please queue this up for next chance. Sorry to bug you, I didn't see this merged yet and just making sure this doesn't slip through

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

2015-12-13 Thread Vegard Nossum
egard 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! Andrew, please queue this up for next chance. Sorry to bug you,

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

2015-11-26 Thread OGAWA Hirofumi
at 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! Andrew, please qu

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

2015-11-26 Thread OGAWA Hirofumi
at 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 potenti

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

2015-11-26 Thread Vegard Nossum
On 11/25/2015 10:54 PM, OGAWA Hirofumi wrote: Vegard Nossum 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

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

2015-11-26 Thread Vegard Nossum
D: 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.61] VFS: Lookup of '1' in vfat loop0 would have caused loop [ 354.

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

2015-11-26 Thread OGAWA Hirofumi
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? >> >

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

2015-11-26 Thread OGAWA Hirofumi
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? >> > >

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

2015-11-25 Thread OGAWA Hirofumi
Vegard Nossum 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

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

2015-11-25 Thread OGAWA Hirofumi
Vegard Nossum <vegard.nos...@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

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

2015-11-24 Thread Vegard Nossum
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() [...] To trigger it, you have to do a rename("/mnt/

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

2015-11-24 Thread Vegard Nossum
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() [...] To trigger it, you have to do a rename("/mnt/

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

2015-11-23 Thread Richard Weinberger
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: > e0

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

2015-11-23 Thread Richard Weinberger
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: > e0

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

2015-11-22 Thread 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 0009 605cc684 e0931b60 605cf637 e0931bc0 60040f6d

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

2015-11-22 Thread 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 0009 605cc684 e0931b60 605cf637 e0931bc0 60040f6d