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
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
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
o minor
- remove a harmless warning about the internal file-close, reported by
Ralf Jung.
J. R. Okajima
- aufs4-linux.git
aufs: remove a warning about the internal file-close
- aufs4-standalone.git
ditto
- aufs-util.git
nothing
Hi,
Ralf Jung:
> I am only getting this warning during a boot, it disappears after a
> while -- no idea why.
I guess the reason is the kernel thread who releases the internal file
object asynchronously. During the boot, the thread might not be prepared
yet.
J. R. Okajima
(removed aufs-users ML from Cc:)
Ralf Jung:
> Oh wow, that's a long list...
Thanx for the report, anyway.
> > - linux kernel version
> > if your kernel is not plain, for example modified by distributor,
> > the url where i can download its source is necessary too.
>
> Linux
Hello Jan,
Jan Luca Naumann:
> the following Debian bug (see also webpage [1]) seems to be a upstream
> problem of the aufs-kernel-module. Could you take a look into it?
Please provide me these necessary info.
(from aufs README file)
_FUSE only. So it should be refined by "#ifdef
CONFIG_AUFS_BR_FUSE".
Reported-by: Jan Luca Naumann <j.naum...@fu-berlin.de>
See-also: https://github.com/sfjro/aufs4-standalone/pull/1
Reported-by: Philipp Marek <philipp.ma...@linbit.com>
See-also: https://bugs.debian.o
Jan Luca Naumann:
> Caution: linux/mount.h is not the same as fs/mount.h, see
> https://github.com/torvalds/linux/blob/master/fs/mount.h
> vs.
> https://github.com/torvalds/linux/blob/master/include/linux/mount.h
Exactly.
How about specifying EXTRA_CFLAGS in your "make" cmdline?
J. R. Okajima
Ben Hutchings:
The code says:
BUILD_BUG_ON(sizeof(ino_t) !=3D sizeof(long));
return ALIGN(sizeof(struct au_vdir_de) + nlen, sizeof(ino_t));
but on alpha, sizeof(ino_t) =3D=3D 4 but sizeof(long) =3D=3D 8.
I decided to remove the BUILD_BUG_ON() line simply. If you want to
Hello Ben,
Ben Hutchings:
The code says:
BUILD_BUG_ON(sizeof(ino_t) !=3D sizeof(long));
return ALIGN(sizeof(struct au_vdir_de) + nlen, sizeof(ino_t));
but on alpha, sizeof(ino_t) =3D=3D 4 but sizeof(long) =3D=3D 8.
Is it really necessary that these types have the same
12 matches
Mail list logo
