Salut à tous !
Moi je fais pas les choses à moitié. Pour moi, il est essentiel d’aller vite et
de faire en grand.
Quand je me suis inscrit sur -leamante.com (enlever les tirest en recopiant le
lien), je pensais pas cependant que ca irait aussi vite !
-leamante.com
Eux, ils vont vraiment à fon
Traditionally, we have always had warnings about uninitialized variables
enabled, as this is part of -Wall, and generally a good idea [1], but it
also always produced false positives, mainly because this is a variation
of the halting problem and provably impossible to get right in all cases
[2].
V
This is a set of patches that I hope to get into v4.9 in some form
in order to turn on the -Wmaybe-uninitialized warnings again.
After talking to Linus in person at Linaro Connect about this, I
spent some time on finding all the remaining warnings, and this
is the resulting patch series. More deta
gcc is unsure about the use of last_ofs_in_node, which might happen
without a prior initialization:
fs/f2fs//git/arm-soc/fs/f2fs/data.c: In function ‘f2fs_map_blocks’:
fs/f2fs/data.c:799:54: warning: ‘last_ofs_in_node’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
if (prea
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fragment space
3. touch all files in the image
4. umount
In this case, we actually don't need to flush dirty inode to inode page du
If inode becomes dirty, we need to check the # of dirty inodes whether or not
further checkpoint would be required.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 0907efa..e63d0fd 100644
If there are a lot of dirty inodes, we need to flush all of them when doing
checkpoint. So, we need to count this for enough free space.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/segment.h b/fs/f2fs/segment
Multiple bugs were recently fixed in the "set encryption policy" ioctl.
To make it clear that fscrypt_process_policy() and fscrypt_get_policy()
implement ioctls and therefore their implementations must take standard
security and correctness precautions, rename them to
fscrypt_ioctl_set_policy() and
