Re: exfat: Improving exception handling in two functions

From: Markus Elfring
Date: Wed Jun 10 2020 - 08:14:43 EST

Next message: Luciano Coelho: "Re: [PATCH 02/15] iwlwifi: mvm: fix gcc-10 zero-length-bounds warning"
Previous message: YuanJunQing: "[PATCH] mips/ftrace: Fix stack backtrace in unwind_stack_by_address()"
In reply to: Dan Carpenter: "[PATCH] exfat: call brelse() on error path"
Next in thread: Greg KH: "Re: exfat: Improving exception handling in two functions"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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â.
20200610095934.GA35167@mwanda/">https://lore.kernel.org/linux-fsdevel/20200610095934.GA35167@mwanda/
https://lore.kernel.org/patchwork/patch/1254515/

Regards,
Markus

Next message: Luciano Coelho: "Re: [PATCH 02/15] iwlwifi: mvm: fix gcc-10 zero-length-bounds warning"
Previous message: YuanJunQing: "[PATCH] mips/ftrace: Fix stack backtrace in unwind_stack_by_address()"
In reply to: Dan Carpenter: "[PATCH] exfat: call brelse() on error path"
Next in thread: Greg KH: "Re: exfat: Improving exception handling in two functions"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]