linux-kernel - Re: [PATCH] exfat: redefine DIR_DELETED as the bad cluster number

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]

Message-ID: <CAKYAXd-+3eRwJTNRiP6Rcpusd9ZRxQdq1NpG=yNOHngsx3pnVw@mail.gmail.com>
Date:   Sun, 8 Jan 2023 10:06:24 +0900
From:   Namjae Jeon <linkinjeon@...nel.org>
To:     Sungjong Seo <sj1557.seo@...sung.com>
Cc:     pali@...nel.org, viro@...iv.linux.org.uk,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Yuezhang Mo <Yuezhang.Mo@...y.com>
Subject: Re: [PATCH] exfat: redefine DIR_DELETED as the bad cluster number

2022-12-29 20:52 GMT+09:00, Sungjong Seo <sj1557.seo@...sung.com>:
> When a file or a directory is deleted, the hint for the cluster of
> its parent directory in its in-memory inode is set as DIR_DELETED.
> Therefore, DIR_DELETED must be one of invalid cluster numbers. According
> to the exFAT specification, a volume can have at most 2^32-11 clusters.
> However, DIR_DELETED is wrongly defined as 0xFFFF0321, which could be
> a valid cluster number. To fix it, let's redefine DIR_DELETED as
> 0xFFFFFFF7, the bad cluster number.
>
> Fixes: 1acf1a564b60 ("exfat: add in-memory and on-disk structures and
> headers")
>
> Reported-by: Yuezhang Mo <Yuezhang.Mo@...y.com>
> Signed-off-by: Sungjong Seo <sj1557.seo@...sung.com>
Applied, Thanks!