On Sat, May 28, 2016 at 08:56:39PM -0400, Zygo Blaxell wrote:
> On Sun, May 29, 2016 at 02:21:03AM +0200, Adam Borowski wrote:
> > In any case, this patch doesn't introduce any cases not already triggerable
> > by root.
>
> It allows non-root to trigger cases that previously could only be
>
29.05.2016 03:56, Zygo Blaxell пишет:
>>
>> I don't think this can happen on btrfs: the superblock is updated only after
>> a barrier when both the data and extent refs are already on the disk.
>
> If and only if the filesystem is mounted with the flushoncommit option,
> that's true. This is not
On Sun, May 29, 2016 at 02:21:03AM +0200, Adam Borowski wrote:
> On Fri, May 27, 2016 at 09:59:22PM -0400, Zygo Blaxell wrote:
> > I wonder if there is a risk of damaging files like this:
> >
> > open A O_RDWR
> >
> > open B O_RDONLY
> >
> > copy B to A
> >
> > do _not_ call
On Fri, May 27, 2016 at 09:59:22PM -0400, Zygo Blaxell wrote:
> On Thu, May 26, 2016 at 05:04:01PM -0700, Mark Fasheh wrote:
> > On Fri, May 20, 2016 at 05:45:12AM +0200, Adam Borowski wrote:
> > > (Only btrfs currently implements dedupe_file_range.)
> > >
> > > Instead of checking the mode of
On Thu, May 26, 2016 at 05:04:01PM -0700, Mark Fasheh wrote:
> On Fri, May 20, 2016 at 05:45:12AM +0200, Adam Borowski wrote:
> > (Only btrfs currently implements dedupe_file_range.)
> >
> > Instead of checking the mode of the file descriptor, let's check whether
> > it could have been opened rw.
On Thu, May 26, 2016 at 05:04:01PM -0700, Mark Fasheh wrote:
> On Fri, May 20, 2016 at 05:45:12AM +0200, Adam Borowski wrote:
> > (Only btrfs currently implements dedupe_file_range.)
> >
> > Instead of checking the mode of the file descriptor, let's check whether
> > it could have been opened rw.
On Fri, May 20, 2016 at 05:45:12AM +0200, Adam Borowski wrote:
> (Only btrfs currently implements dedupe_file_range.)
>
> Instead of checking the mode of the file descriptor, let's check whether
> it could have been opened rw. This allows fixing failures when deduping
> a live system: anyone
On Fri, May 20, 2016 at 05:45:12AM +0200, Adam Borowski wrote:
> (Only btrfs currently implements dedupe_file_range.)
>
> Instead of checking the mode of the file descriptor, let's check whether
> it could have been opened rw. This allows fixing failures when deduping
> a live system: anyone
(Only btrfs currently implements dedupe_file_range.)
Instead of checking the mode of the file descriptor, let's check whether
it could have been opened rw. This allows fixing failures when deduping
a live system: anyone trying to exec a file currently being deduped gets
ETXTBSY.
Issuing this
