Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
In-Reply-To: <1891546521.01672360201726.JavaMail.epsvc@epcpadp3>
References: <CGME20221229115257epcas1p27195844dc54cf09608dad9967808530a@epcas1p2.samsung.com>
 <1891546521.01672360201726.JavaMail.epsvc@epcpadp3>
From:   Namjae Jeon <linkinjeon@kernel.org>
Date:   Sun, 8 Jan 2023 10:06:24 +0900
Message-ID: <CAKYAXd-+3eRwJTNRiP6Rcpusd9ZRxQdq1NpG=yNOHngsx3pnVw@mail.gmail.com>
Subject: Re: [PATCH] exfat: redefine DIR_DELETED as the bad cluster number
To:     Sungjong Seo <sj1557.seo@samsung.com>
Cc:     pali@kernel.org, viro@zeniv.linux.org.uk,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        Yuezhang Mo <Yuezhang.Mo@sony.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

2022-12-29 20:52 GMT+09:00, Sungjong Seo <sj1557.seo@samsung.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@sony.com>
> Signed-off-by: Sungjong Seo <sj1557.seo@samsung.com>
Applied, Thanks!