sf...@users.sourceforge.net:
> sf...@users.sourceforge.net:
>> Thanx for the interesting bug report.
>> Although I could not reproduce the bug, I'm afraid it is an aufs
>> problem. I will try more and investigate it, but it may take some time.
> On the report, I can see that you use aufs in qemu.
sf...@users.sourceforge.net:
> Thanx for the interesting bug report.
> Although I could not reproduce the bug, I'm afraid it is an aufs
> problem. I will try more and investigate it, but it may take some time.
On the report, I can see that you use aufs in qemu.
Would you kindly tell me how you
intrigeri:
> OK, sorry. I got confused by:
>
>I am interested in why you set '1' to the aufs module parameter "debug".
>If you had not set, this bug would not appear I guess. Did you see
>something wrong without setting "debug"?
>
> =E2=80=A6 which seemed to refer to that module
sf...@users.sourceforge.net:
> intrigeri:
>> Same problem without debug=1:
> That is not what I meant.
OK, sorry. I got confused by:
I am interested in why you set '1' to the aufs module parameter "debug".
If you had not set, this bug would not appear I guess. Did you see
something
intrigeri:
> Same problem without debug=1:
That is not what I meant.
--
As you might know, LOCKDEP is a kernel debugging feature and
AuRwDestroy() macro is enabled only when CONFIG_AUFS_DEBUG is
enabled. So I guess if you
intrigeri:
> sf...@users.sourceforge.net:
>> I am interested in why you set '1' to the aufs module parameter "debug".
> IIRC I added it after having noticed the bug, in the hope it would
> yield more useful information for developers to fix it.
>> If you had not set, this bug would not appear I
sf...@users.sourceforge.net:
> I am interested in why you set '1' to the aufs module parameter "debug".
IIRC I added it after having noticed the bug, in the hope it would
yield more useful information for developers to fix it.
> If you had not set, this bug would not appear I guess. Did you see
Jan Luca Naumann:
> I could reproduce the bug using a 4.15 kernel. Could you please take a
> look into this?
Thanx for the interesting bug report.
Although I could not reproduce the bug, I'm afraid it is an aufs
problem. I will try more and investigate it, but it may take some time.
I am
Dear aufs-maintainer,
below a Debian bug reporting a seg fault is attached. A online version
of the bug can be found here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886329
I could reproduce the bug using a 4.15 kernel. Could you please take a
look into this?
Thank you very much and
9 matches
Mail list logo
