Jan Luca Naumann:
> the underlying filesystem is a tmpfs for me as well:
> [...]
> I get no segfault for the call still so there has to be another reason...
Indeed!
I've just reproduced this in an up-to-date sid VM where /tmp is on the
ext4 root filesystem. I've purged and reinstalled aufs-dkms
Hey,
the underlying filesystem is a tmpfs for me as well:
# uname -a
Linux 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64
# mount | grep /tmp
none on /tmp type tmpfs (rw,nosuid,nodev,noatime,nodiratime)
# modprobe aufs debug=1 \
&& mkdir /tmp/{ro,rw,mount} \
&& touch
anonym:
> I guess that you, Jan, are *not* mounting a tmpfs on /tmp and I am guessing
> that you,
> intrigeri, *are*. Am I correct? :)
I am indeed. Jan, can you reproduce if the underlying filesystem is tmpfs?
> At least for me, the segfault only triggers when the underlying fs
> is a tmpfs.
anonym:
> Jan Luca Naumann:
>> Control: tags -1 unreproducible
>>
>> I tested your code sample below and I could not reproduce the bug with a
>> current 4.14.13 kernel on my system. Could you please test it again?
>
> I am not the reporter, but this bug still affects me using
>
Jan Luca Naumann:
> Control: tags -1 unreproducible
>
> I tested your code sample below and I could not reproduce the bug with a
> current 4.14.13 kernel on my system. Could you please test it again?
I am not the reporter, but this bug still affects me using
linux-image-4.14.0-3-amd64
Control: tags -1 unreproducible
Hey,
sorry for the long delay for my answer.
I tested your code sample below and I could not reproduce the bug with a
current 4.14.13 kernel on my system. Could you please test it again?
Best regards,
Jan
Am 04.01.2018 um 15:42 schrieb intrigeri:
> Hi,
>
>
Hey,
I am not at home for another two days and do not have a proper computer with
me. I will take a look at the problem on the weekend.
Jan
Am 4. Januar 2018 15:42:56 MEZ schrieb intrigeri :
>Hi,
>
>interestingly, only the first access to the aufs mountpoint triggers
>the
7 matches
Mail list logo