[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <6939014a-adbf-f970-2541-df16d35de7e5@web.de>
Date: Wed, 10 Jun 2020 14:07:39 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Dan Carpenter <dan.carpenter@...cle.com>,
linux-fsdevel@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Namjae Jeon <namjae.jeon@...sung.com>,
Sungjong Seo <sj1557.seo@...sung.com>,
Pali Rohár <pali@...nel.org>,
Tetsuhiro Kohada <kohada.t2@...il.com>,
Wei Yongjun <weiyongjun1@...wei.com>
Subject: Re: [PATCH] exfat: call brelse() on error path
> If the second exfat_get_dentry() call fails then we need to release
> "old_bh" before returning.
Thanks you picked a bit of information up from my source code analysis
for a possible adjustment of the function “exfat_rename_file”.
exfat: Improving exception handling in two functions
https://lore.kernel.org/linux-fsdevel/208cba7b-e535-c8e0-5ac7-f15170117a7f@web.de/
https://lkml.org/lkml/2020/6/10/272
Would you like to adjust the implementation of the function “exfat_move_file”
in a similar way in a subsequent patch variant?
Regards,
Markus
Powered by blists - more mailing lists