On 2019-8-17 9:03, Jaegeuk Kim wrote:
> If we use later kernel having larger extra_isize, old fsck will delete
> entire old files.
Would it be better to construct the length based on existed features?
Thanks,
>
> Signed-off-by: Jaegeuk Kim
> ---
> fsck/fsck.c | 2 +-
> 1 file changed, 1 inser
Hi Eric,
Do you mind folding these fixes into original patch as it's still in dev branch?
BTW, any comment or suggestion is welcome in my original patch :)
Thanks,
On 2019-8-16 14:49, Chao Yu wrote:
> Eric, thanks for all the fixes.
>
> Thanks,
>
> On 2019/8/16 13:55, Eric Biggers wrote:
Hi Chandan,
On 2019-8-16 14:18, Chandan Rajendra wrote:
> F2FS has a copy of "post read processing" code using which encrypted
> file data is decrypted. This commit replaces it to make use of the
> generic read_callbacks facility.
I remember that previously Jaegeuk had mentioned f2fs will support
On Fri, Aug 16, 2019 at 02:59:37PM +0800, Chao Yu wrote:
> On 2019/8/16 13:55, Eric Biggers wrote:
> > From: Eric Biggers
> >
> > Userspace provides a null-terminated string, so don't assume that the
> > full FSLABEL_MAX bytes can always be copied.>
> > Fixes: 61a3da4d5ef8 ("f2fs: support FS_IOC_
On Sun, Aug 18, 2019 at 09:03:21PM +0800, Chao Yu wrote:
> Hi Eric,
>
> Do you mind folding these fixes into original patch as it's still in dev
> branch?
>
> BTW, any comment or suggestion is welcome in my original patch :)
>
> Thanks,
>
I'm fine with the patches being folded in.
- Eric
On Fri, Aug 16, 2019 at 04:37:35PM +0800, Chao Yu wrote:
> Hi Eric,
>
> Sorry for late reply...
>
> I only hit ENOSPC error:
>
> QA output created by 204
> line 82: echo: write error: No space left on device
>
> What is your mkfs/mount option?
>
It's:
MKFS_OPTIONS -- /dev/vdc
MOUNT_OPTIONS
The series is an update and a more complete version of the
previously posted series at
https://lore.kernel.org/linux-fsdevel/20180122020426.2988-1-deepa.ker...@gmail.com/
Thanks to Arnd Bergmann for doing a few preliminary reviews.
They helped me fix a few issues I had overlooked.
The limits (som
Update the inode timestamp updates to use timestamp_truncate()
instead of timespec64_trunc().
The change was mostly generated by the following coccinelle
script.
virtual context
virtual patch
@r1 depends on patch forall@
struct inode *inode;
identifier i_xtime =~ "^i_[acm]time$";
expression e;
@
On Sun, Aug 18, 2019 at 09:58:00AM -0700, Deepa Dinamani wrote:
> Update the inode timestamp updates to use timestamp_truncate()
> instead of timespec64_trunc().
>
> The change was mostly generated by the following coccinelle
> script.
>
> virtual context
> virtual patch
>
> @r1 depends on patch
On Sun, Aug 11, 2019 at 02:35:51PM -0700, Eric Biggers wrote:
> A few fixes and cleanups for fs-verity.
>
> If there are no objections, I'll fold these into the original patches.
>
> Eric Biggers (6):
> fs-verity: fix crash on read error in build_merkle_tree_level()
> ext4: skip truncate when
On Tue, Aug 13, 2019 at 10:40:39AM +0800, Chao Yu wrote:
> Hi Eric,
>
> On 2019/8/13 6:58, Eric Biggers wrote:
> > Hi Chao,
> >
> > On Mon, Aug 12, 2019 at 08:25:33PM +0800, Chao Yu wrote:
> >> Hi Eric,
> >>
> >> On 2019/8/12 5:35, Eric Biggers wrote:
> >>> From: Eric Biggers
> >>>
> >>> When an
On 2019/8/18 23:41, Eric Biggers wrote:
> On Fri, Aug 16, 2019 at 02:59:37PM +0800, Chao Yu wrote:
>> On 2019/8/16 13:55, Eric Biggers wrote:
>>> From: Eric Biggers
>>>
>>> Userspace provides a null-terminated string, so don't assume that the
>>> full FSLABEL_MAX bytes can always be copied.>
>>> F
On 2019/8/19 9:33, Chao Yu wrote:
> On 2019/8/18 23:41, Eric Biggers wrote:
>> On Fri, Aug 16, 2019 at 02:59:37PM +0800, Chao Yu wrote:
>>> On 2019/8/16 13:55, Eric Biggers wrote:
From: Eric Biggers
Userspace provides a null-terminated string, so don't assume that the
full FSLA
On 2019/8/16 10:41, Jaegeuk Kim wrote:
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
On Mon, Aug 19, 2019 at 09:58:30AM +0800, Chao Yu wrote:
> On 2019/8/19 9:33, Chao Yu wrote:
> > On 2019/8/18 23:41, Eric Biggers wrote:
> >> On Fri, Aug 16, 2019 at 02:59:37PM +0800, Chao Yu wrote:
> >>> On 2019/8/16 13:55, Eric Biggers wrote:
> From: Eric Biggers
>
> Userspace pro
On 08/18, Eric Biggers wrote:
> On Sun, Aug 18, 2019 at 09:03:21PM +0800, Chao Yu wrote:
> > Hi Eric,
> >
> > Do you mind folding these fixes into original patch as it's still in dev
> > branch?
> >
> > BTW, any comment or suggestion is welcome in my original patch :)
> >
> > Thanks,
> >
>
On 2019/8/19 10:55, Eric Biggers wrote:
> On Mon, Aug 19, 2019 at 09:58:30AM +0800, Chao Yu wrote:
>> On 2019/8/19 9:33, Chao Yu wrote:
>>> On 2019/8/18 23:41, Eric Biggers wrote:
On Fri, Aug 16, 2019 at 02:59:37PM +0800, Chao Yu wrote:
> On 2019/8/16 13:55, Eric Biggers wrote:
>> From
On 2019/8/16 11:03, Chao Yu wrote:
> There is one case can cause data corruption.
>
> - write 4k to fileA
> - fsync fileA, 4k data is writebacked to lbaA
> - write 4k to fileA
> - kworker flushs 4k to lbaB; dnode contain lbaB didn't be persisted yet
> - write 4k to fileB
> - kworker flush 4k to lb
18 matches
Mail list logo
