On 2014/10/11 11:00, Weng Meiling wrote:
> ping ...
>
> On 2014/10/9 20:47, Weng Meiling wrote:
>> On 2014/10/9 20:43, Weng Meiling wrote:
>>> Hi guys,
>>>
>>> I see the mails you discussed the BUG at fs/sysfs/group.c:65! triggered by
>>> duplicated sysfs link.
>>>
>>> the detail mail:
>>>
>>> ht
ping ...
On 2014/10/9 20:47, Weng Meiling wrote:
> On 2014/10/9 20:43, Weng Meiling wrote:
>> Hi guys,
>>
>> I see the mails you discussed the BUG at fs/sysfs/group.c:65! triggered by
>> duplicated sysfs link.
>>
>> the detail mail:
>>
>> https://lkml.org/lkml/2013/3/8/370
>>
>> but it seems the
On 2014/10/9 20:43, Weng Meiling wrote:
> Hi guys,
>
> I see the mails you discussed the BUG at fs/sysfs/group.c:65! triggered by
> duplicated sysfs link.
>
> the detail mail:
>
> https://lkml.org/lkml/2013/3/8/370
>
> but it seems the problems has no conclusion. In our environment, we trigger
Hi guys,
I see the mails you discussed the BUG at fs/sysfs/group.c:65! triggered by
duplicated sysfs link.
the detail mail:
https://lkml.org/lkml/2013/3/8/370
but it seems the problems has no conclusion. In our environment, we triggered
the bug too, but for error ENOENT:
we use 3.4 kernel, a
On Sun, Mar 10, 2013 at 01:35:12PM -0700, Eric W. Biederman wrote:
> Greg KH writes:
>
> > On Sun, Mar 10, 2013 at 04:53:11PM +0800, Ming Lei wrote:
> >> On Sun, Mar 10, 2013 at 12:36 AM, Tommi Rantala
> >> wrote:
> >> > [ 40.089036] [] sysfs_get_dirent+0x39/0x80
> >> > [ 40.089036] [] sy
Greg KH writes:
> On Sun, Mar 10, 2013 at 04:53:11PM +0800, Ming Lei wrote:
>> On Sun, Mar 10, 2013 at 12:36 AM, Tommi Rantala wrote:
>> > [ 40.089036] [] sysfs_get_dirent+0x39/0x80
>> > [ 40.089036] [] sysfs_remove_group+0x29/0x100
>> > [ 40.089036] [] blk_trace_remove_sysfs+0x14/0x20
On Sun, Mar 10, 2013 at 04:53:11PM +0800, Ming Lei wrote:
> On Sun, Mar 10, 2013 at 12:36 AM, Tommi Rantala wrote:
> > [ 40.089036] [] sysfs_get_dirent+0x39/0x80
> > [ 40.089036] [] sysfs_remove_group+0x29/0x100
> > [ 40.089036] [] blk_trace_remove_sysfs+0x14/0x20
> > [ 40.089036] [] b
(cc'ing Jens)
Hello,
On Sun, Mar 10, 2013 at 04:53:11PM +0800, Ming Lei wrote:
> On Sun, Mar 10, 2013 at 12:36 AM, Tommi Rantala wrote:
> > [ 40.089036] [] sysfs_get_dirent+0x39/0x80
> > [ 40.089036] [] sysfs_remove_group+0x29/0x100
> > [ 40.089036] [] blk_trace_remove_sysfs+0x14/0x20
>
On Sun, Mar 10, 2013 at 12:36 AM, Tommi Rantala wrote:
> [ 40.089036] [] sysfs_get_dirent+0x39/0x80
> [ 40.089036] [] sysfs_remove_group+0x29/0x100
> [ 40.089036] [] blk_trace_remove_sysfs+0x14/0x20
> [ 40.089036] [] blk_unregister_queue+0x5e/0x90
> [ 40.089036] [] del_gendisk+0x107
2013/3/9 Ming Lei :
> On Sat, Mar 9, 2013 at 4:41 AM, Greg KH wrote:
>> On Fri, Mar 08, 2013 at 09:35:17PM +0200, Tommi Rantala wrote:
>>> Hello,
>>>
>>> Saw this while fuzzing with trinity:
>>>
>>> # ./trinity -q -l off -C20 --dangerous -c ioctl -V /dev
>>> Trinity v1.2pre Dave Jones
>>> [3450]
On Sat, Mar 9, 2013 at 4:41 AM, Greg KH wrote:
> On Fri, Mar 08, 2013 at 09:35:17PM +0200, Tommi Rantala wrote:
>> Hello,
>>
>> Saw this while fuzzing with trinity:
>>
>> # ./trinity -q -l off -C20 --dangerous -c ioctl -V /dev
>> Trinity v1.2pre Dave Jones
>> [3450] Marking 64-bit syscall 16 (io
2013/3/8 Greg KH :
> On Fri, Mar 08, 2013 at 09:35:17PM +0200, Tommi Rantala wrote:
>> [ 205.043027] kernel BUG at
>> /home/ttrantal/git/linux-2.6/fs/sysfs/group.c:65!
>
> And now we crash. For a loop device we are trying to add.
>
> Ick.
>
> I'm guessing that the caller of whom ever tried to cr
On Fri, Mar 08, 2013 at 09:35:17PM +0200, Tommi Rantala wrote:
> Hello,
>
> Saw this while fuzzing with trinity:
>
> # ./trinity -q -l off -C20 --dangerous -c ioctl -V /dev
> Trinity v1.2pre Dave Jones
> [3450] Marking 64-bit syscall 16 (ioctl) as enabled
> [3450] Marking 32-bit syscall 54 (ioc
13 matches
Mail list logo
