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:
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
> >>>
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
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,
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
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
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
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.
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?
>>
>
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?
>>
>
>
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
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
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/
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/
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
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
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
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
18 matches
Mail list logo