lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 21 Dec 2021 21:34:58 +0900
From:   "Sungjong Seo" <sj1557.seo@...sung.com>
To:     <linkinjeon@...nel.org>
Cc:     <linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <sj1557.seo@...sung.com>
Subject: RE: [PATCH] exfat: fix missing REQ_SYNC in exfat_update_bhs()

> If 'dirsync' is enabled, all directory updates within the
> filesystem should be done synchronously. exfat_update_bh()
> does as this, but exfat_update_bhs() does not.
> 
> Signed-off-by: Yuezhang.Mo <Yuezhang.Mo@...y.com>
> Reviewed-by: Andy.Wu <Andy.Wu@...y.com>
> Reviewed-by: Aoyama, Wataru <wataru.aoyama@...y.com>
> Reviewed-by: Kobayashi, Kento <Kento.A.Kobayashi@...y.com>
> ---
>  fs/exfat/misc.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/exfat/misc.c b/fs/exfat/misc.c
> index d34e6193258d..d5bd8e6d9741 100644
> --- a/fs/exfat/misc.c
> +++ b/fs/exfat/misc.c
> @@ -10,6 +10,7 @@
>  #include <linux/fs.h>
>  #include <linux/slab.h>
>  #include <linux/buffer_head.h>
> +#include <linux/blk_types.h>
> 
>  #include "exfat_raw.h"
>  #include "exfat_fs.h"
> @@ -180,7 +181,7 @@ int exfat_update_bhs(struct buffer_head **bhs, int
> nr_bhs, int sync)
>  		set_buffer_uptodate(bhs[i]);
>  		mark_buffer_dirty(bhs[i]);
>  		if (sync)
> -			write_dirty_buffer(bhs[i], 0);
> +			write_dirty_buffer(bhs[i], REQ_SYNC);

I think there is no problem in terms of functionality related to
"synchronously" in the original code. However, REQ_SYNC could affect
I/O scheduling, and exfat_update_bh() already requests I/O with this
flag by calling sync_dirty_buffer(). And it is desirable for two
functions to have the same concept for I/O requests.

So, the original code does not seem like a bug,
but this patch looks useful.
Thanks.

Reviewed-by: Sungjong Seo <sj1557.seo@...sung.com>

>  	}
> 
>  	for (i = 0; i < nr_bhs && sync; i++) {
> --
> 2.25.1

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ