These patches are largely based on the casefolding patches for ext4
v2: Rebased patches again master, changed f2fs_msg to f2fs_info/f2fs_err
Daniel Rosenberg (2):
f2fs: include charset encoding information in the superblock
f2fs: Support case-insensitive file name lookups
fs/f2fs/dir.c
Add charset encoding to f2fs to support casefolding. It is modeled after
the same feature introduced in commit c83ad55eaa91 ("ext4: include charset
encoding information in the superblock")
Currently this is not compatible with encryption, similar to the current
ext4 imlpementation. This will
Modeled after commit b886ee3e778e ("ext4: Support case-insensitive file
name lookups")
"""
This patch implements the actual support for case-insensitive file name
lookups in f2fs, based on the feature bit and the encoding stored in the
superblock.
A filesystem that has the casefold feature set
https://bugzilla.kernel.org/show_bug.cgi?id=204193
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=204197
Bug ID: 204197
Summary: F2FS: kernel BUG at fs/f2fs/inode.c:722!
Product: File System
Version: 2.5
Kernel Version: 5.1.3
Hardware: All
OS: Linux
Tree:
https://bugzilla.kernel.org/show_bug.cgi?id=204193
Bug ID: 204193
Summary: BUG: KASAN: null-ptr-deref in
f2fs_write_end_io+0x215/0x650
Product: File System
Version: 2.5
Kernel Version: 5.1.3
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=202495
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=204043
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Comment #6 is|1 |0
private|
https://bugzilla.kernel.org/show_bug.cgi?id=204135
--- Comment #3 from Chao Yu (c...@kernel.org) ---
F2FS_IO_ALIGNED() was defined in last patch for your previous issue... so,
should apply them before this patch.
Could you change to last code in dev branch in Jaegeuk's git repo.
This original patch was from Weichao Guo.
We may encounter both checkpoints invalid in such a case:
1. kernel writes CP A;
2. power-cut when kernel writes CP B, then CP B is corrupted;
3. fsck: load CP A, fix meta/data;
4. power-cut when fsck writes CP A in-place, then CP A is corrupted too;
To
On 2019/7/17 5:08, Jaegeuk Kim wrote:
> On 07/16, Chao Yu wrote:
>> Ping,
>
> It seems this is still breaking the tests. At some point on fault/power tests,
> I hit fsck is stopped since it's missing one NAT node.
>
>>
>> On 2019-6-26 17:48, Chao Yu wrote:
>>> + ret = dev_read(buf, src <<
On 07/16, Chao Yu wrote:
> Ping,
It seems this is still breaking the tests. At some point on fault/power tests,
I hit fsck is stopped since it's missing one NAT node.
>
> On 2019-6-26 17:48, Chao Yu wrote:
> > This original patch was from Weichao Guo.
> >
> > We may encounter both checkpoints
Hi Daniel,
Could you please rebase you patch set?
e.g., f2fs_msg() was replaced with f2fs_err|info|...
On 07/11, Daniel Rosenberg wrote:
> Add charset encoding to f2fs to support casefolding. It is modeled after
> the same feature introduced in commit c83ad55eaa91 ("ext4: include charset
>
Ping,
On 2019-6-26 17:48, Chao Yu wrote:
> This original patch was from Weichao Guo.
>
> We may encounter both checkpoints invalid in such a case:
> 1. kernel writes CP A;
> 2. power-cut when kernel writes CP B, then CP B is corrupted;
> 3. fsck: load CP A, fix meta/data;
> 4. power-cut when
Hi Jaegeuk,
On 2019/5/9 9:15, Chao Yu wrote:
> On 2019/5/5 10:51, Chao Yu wrote:
>> On 2019/5/1 11:22, Jaegeuk Kim wrote:
>>> On 04/29, Chao Yu wrote:
On 2019-4-28 21:38, Jaegeuk Kim wrote:
> On 04/24, Chao Yu wrote:
>> This patch fixes to do sanity with enabled features in image, if
https://bugzilla.kernel.org/show_bug.cgi?id=204135
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=204043
--- Comment #4 from Chao Yu (c...@kernel.org) ---
Sorry, previous version is broken... I've updated them.
https://lore.kernel.org/linux-f2fs-devel/20190712085542.4068-1-yuch...@huawei.com/T/#u
--
You are receiving this mail because:
You are
17 matches
Mail list logo
