From: Markus Elfring <Markus.Elfring@web.de>
To: linux-fsdevel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>,
Sungjong Seo <sj1557.seo@samsung.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Pali Rohár" <pali@kernel.org>,
"Tetsuhiro Kohada" <kohada.t2@gmail.com>,
"Wei Yongjun" <weiyongjun1@huawei.com>
Subject: Re: exfat: Improving exception handling in two functions
Date: Wed, 10 Jun 2020 14:14:19 +0200 [thread overview]
Message-ID: <4379dad4-8c76-6790-2d5b-91a8fbdffc9f@web.de> (raw)
In-Reply-To: <208cba7b-e535-c8e0-5ac7-f15170117a7f@web.de>
> My source code analysis approach pointed implementation details
> like the following out for further software development considerations.
The clarification of corresponding collateral evolution will be continued
with the update suggestion “exfat: call brelse() on error path”.
https://lore.kernel.org/linux-fsdevel/20200610095934.GA35167@mwanda/
https://lore.kernel.org/patchwork/patch/1254515/
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-fsdevel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>,
Sungjong Seo <sj1557.seo@samsung.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Pali Rohár" <pali@kernel.org>,
"Tetsuhiro Kohada" <kohada.t2@gmail.com>,
"Wei Yongjun" <weiyongjun1@huawei.com>
Subject: Re: exfat: Improving exception handling in two functions
Date: Wed, 10 Jun 2020 12:14:19 +0000 [thread overview]
Message-ID: <4379dad4-8c76-6790-2d5b-91a8fbdffc9f@web.de> (raw)
In-Reply-To: <208cba7b-e535-c8e0-5ac7-f15170117a7f@web.de>
> My source code analysis approach pointed implementation details
> like the following out for further software development considerations.
The clarification of corresponding collateral evolution will be continued
with the update suggestion “exfat: call brelse() on error path”.
https://lore.kernel.org/linux-fsdevel/20200610095934.GA35167@mwanda/
https://lore.kernel.org/patchwork/patch/1254515/
Regards,
Markus
next prev parent reply other threads:[~2020-06-10 12:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 15:07 [PATCH] exfat: Fix use after free in exfat_load_upcase_table() Markus Elfring
2020-06-08 15:07 ` Markus Elfring
2020-06-08 15:52 ` Matthew Wilcox
2020-06-08 15:52 ` Matthew Wilcox
2020-06-08 20:07 ` Markus Elfring
2020-06-08 20:07 ` Markus Elfring
2020-06-09 9:10 ` [PATCH] " Greg KH
2020-06-09 9:10 ` Greg KH
2020-06-10 9:27 ` exfat: Improving exception handling in two functions Markus Elfring
2020-06-10 9:27 ` Markus Elfring
2020-06-10 9:59 ` [PATCH] exfat: call brelse() on error path Dan Carpenter
2020-06-10 9:59 ` Dan Carpenter
2020-06-10 12:14 ` Markus Elfring [this message]
2020-06-10 12:14 ` exfat: Improving exception handling in two functions Markus Elfring
2020-06-10 14:53 ` Greg KH
2020-06-10 14:53 ` Greg KH
2020-06-10 12:07 [PATCH] exfat: call brelse() on error path Markus Elfring
2020-06-10 12:07 ` Markus Elfring
2020-06-10 17:22 ` [PATCH v2] exfat: add missing brelse() calls on error paths Dan Carpenter
2020-06-10 17:22 ` Dan Carpenter
2020-06-10 18:12 ` Markus Elfring
2020-06-10 18:12 ` Markus Elfring
2020-06-10 18:45 ` Dan Carpenter
2020-06-10 18:45 ` Dan Carpenter
2020-06-10 18:56 ` Markus Elfring
2020-06-10 18:56 ` Markus Elfring
2020-06-10 19:22 ` Matthew Wilcox
2020-06-10 19:22 ` Matthew Wilcox
2020-06-10 20:00 ` Markus Elfring
2020-06-10 20:00 ` Markus Elfring
2020-06-11 3:41 ` [PATCH v2] " Namjae Jeon
2020-06-11 3:41 ` Namjae Jeon
2020-06-11 8:00 ` Markus Elfring
2020-06-11 8:00 ` Markus Elfring
2020-06-11 8:40 ` Markus Elfring
2020-06-11 8:40 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4379dad4-8c76-6790-2d5b-91a8fbdffc9f@web.de \
--to=markus.elfring@web.de \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kohada.t2@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=pali@kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=weiyongjun1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.