Re: [PATCH 07/12] vfs: do get_write_access() on upper layer of overlayfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 19, 2016 at 11:30 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote:
> On Wed, Oct 19, 2016 at 11:12 AM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>> On Wed, Oct 19, 2016 at 9:41 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote:
>>
>>> But I noticed a strange behavior:
>>> When you run t_truncate_self from upper you get success for not being
>>> able to truncate.
>>> When you run t_truncate_self from lower you get an error for being
>>> able to truncate
>>> This is ok as you write, but...
>>> When you re-run t_truncate_self file that just got copied-up you get
>>> segmentation fault
>>> and that is not ok.
>>>
>>> You get try the patch to xfstest below to reproduce the problem:
>>
>> Why would a program want to self truncate itself, except to test denywrite?
>>
>
>
> Forget it. my re-run test was silly. Because the truncate succeeded
> it was trying to run a corrupted executable.
>
> I will send patches to fix the test according to new behavior.

Sent patches to fstests. Please review.

>
> Thanks,
> Amir.
--
To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystems Devel]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux