Some device like android phone doesn't show the dev number path in
/dev/block/, but most of devices show in /sys/dev/block
Signed-off-by: Ben Chang
---
tools/fibmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/fibmap.c b/tools/fibmap.c
index 3238f29..9f94b53 100644
On 2022/6/17 1:17, Jaegeuk Kim wrote:
On 06/16, Dylan Chang wrote:
fibmap: Fix file too large causing file_pos overflow
fibmap show file_pos with incorrectly value when passing a large file.
Before:
file info---
/data/media/0/data1 :
---
On 2022/6/17 0:22, Jaegeuk Kim wrote:
On 06/16, Chao Yu wrote:
On 2022/6/16 0:54, Jaegeuk Kim wrote:
On 06/15, Chao Yu wrote:
On 2022/6/11 2:32, Daeho Jeong wrote:
From: Daeho Jeong
Made iostat related locks safe to be called from irq context again.
Will be better to add a 'Fixes' line?
From: Eric Biggers
Document the proposed STATX_DIOALIGN support for statx()
(https://lore.kernel.org/linux-fsdevel/[email protected]).
Signed-off-by: Eric Biggers
---
man2/open.2 | 43 ---
man2/statx.2 | 32
From: Eric Biggers
Add support for STATX_DIOALIGN to block devices, so that direct I/O
alignment restrictions are exposed to userspace in a generic way.
Note that this breaks the tradition of stat operating only on the block
device node, not the block device itself. However, it was felt that
do
From: Eric Biggers
To prepare for STATX_DIOALIGN support, make two changes to
fscrypt_dio_supported().
First, remove the filesystem-block-alignment check and make the
filesystems handle it instead. It previously made sense to have it in
fs/crypto/; however, to support STATX_DIOALIGN the alignme
From: Eric Biggers
f2fs_force_buffered_io() is only used in file.c, so move it into there.
No behavior change. This makes it easier to review later patches.
Signed-off-by: Eric Biggers
---
fs/f2fs/f2fs.h | 45 -
fs/f2fs/file.c | 45 +
This patchset makes the statx() system call return direct I/O (DIO)
alignment information. This allows userspace to easily determine
whether a file supports DIO, and if so with what alignment restrictions.
Patch 1 adds the basic VFS support for STATX_DIOALIGN. Patch 2 wires it
up for all block d
From: Eric Biggers
f2fs only allows direct I/O that is aligned to the filesystem block
size. Given that fact, simplify f2fs_force_buffered_io() by removing
the redundant call to block_unaligned_IO().
This makes it easier to reuse this code for STATX_DIOALIGN.
Signed-off-by: Eric Biggers
---
From: Eric Biggers
Traditionally, the conditions for when DIO (direct I/O) is supported
were fairly simple. For both block devices and regular files, DIO had
to be aligned to the logical block size of the block device.
However, due to filesystem features that have been added over time (e.g.
mul
From: Eric Biggers
Currently, if an f2fs filesystem is mounted with the mode=lfs and
io_bits mount options, DIO reads are allowed but DIO writes are not.
Allowing DIO reads but not DIO writes is an unusual restriction, which
is likely to be surprising to applications, namely any application that
From: Eric Biggers
Add support for STATX_DIOALIGN to ext4, so that direct I/O alignment
restrictions are exposed to userspace in a generic way.
Signed-off-by: Eric Biggers
---
fs/ext4/ext4.h | 1 +
fs/ext4/file.c | 15 ---
fs/ext4/inode.c | 29 +
3 fi
From: Eric Biggers
Add support for STATX_DIOALIGN to f2fs, so that direct I/O alignment
restrictions are exposed to userspace in a generic way.
Signed-off-by: Eric Biggers
---
fs/f2fs/file.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
in
On 06/16, Dylan Chang wrote:
> fibmap: Fix file too large causing file_pos overflow
>
> fibmap show file_pos with incorrectly value when passing a large file.
>
> Before:
>
> file info---
> /data/media/0/data1 :
>
> dev
On 06/15, Pavel Machek wrote:
> Hi!
>
> > > > AFAICS, the read-unfair rwsem code is created to resolve a potential
> > > > lock starvation problem that they found on linux-5.10.y stable tree. I
> > > > believe I have fixed that in the v5.11 kernel, see commit 2f06f702925
> > > > ("locking/rwsem: P
On 06/16, Chao Yu wrote:
> On 2022/6/16 0:54, Jaegeuk Kim wrote:
> > On 06/15, Chao Yu wrote:
> > > On 2022/6/11 2:32, Daeho Jeong wrote:
> > > > From: Daeho Jeong
> > > >
> > > > Made iostat related locks safe to be called from irq context again.
> > > >
> > >
> > > Will be better to add a 'Fi
16 matches
Mail list logo
