From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "ntfs3@lists.linux.dev" <ntfs3@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: RE: [PATCH] fs/ntfs3: add checks for allocation failure
Date: Fri, 27 Aug 2021 17:16:57 +0000 [thread overview]
Message-ID: <433bf776e8cf4fcc8dc9c1db4e43151b@paragon-software.com> (raw)
In-Reply-To: <20210824115236.GJ31143@kili>
> From: Dan Carpenter <dan.carpenter@oracle.com>
> Sent: Tuesday, August 24, 2021 2:53 PM
> To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> Cc: ntfs3@lists.linux.dev; linux-kernel@vger.kernel.org; kernel-janitors@vger.kernel.org
> Subject: [PATCH] fs/ntfs3: add checks for allocation failure
>
> Add a check for when the kzalloc() in init_rsttbl() fails. Some of
> the callers checked for NULL and some did not. I went down the call
> tree and added NULL checks where ever they were missing.
>
> Fixes: b46acd6a6a62 ("fs/ntfs3: Add NTFS journal")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> fs/ntfs3/fslog.c | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
> index 397ba6a956e7..209fe6ddead0 100644
> --- a/fs/ntfs3/fslog.c
> +++ b/fs/ntfs3/fslog.c
> @@ -807,7 +807,11 @@ static inline struct RESTART_TABLE *init_rsttbl(u16 esize, u16 used)
> u32 off;
> u32 bytes = esize * used + sizeof(struct RESTART_TABLE);
> u32 lf = sizeof(struct RESTART_TABLE) + (used - 1) * esize;
> - struct RESTART_TABLE *t = ntfs_zalloc(bytes);
> + struct RESTART_TABLE *t;
> +
> + t = ntfs_zalloc(bytes);
> + if (!t)
> + return NULL;
>
> t->size = cpu_to_le16(esize);
> t->used = cpu_to_le16(used);
> @@ -831,7 +835,11 @@ static inline struct RESTART_TABLE *extend_rsttbl(struct RESTART_TABLE *tbl,
> u16 esize = le16_to_cpu(tbl->size);
> __le32 osize = cpu_to_le32(bytes_per_rt(tbl));
> u32 used = le16_to_cpu(tbl->used);
> - struct RESTART_TABLE *rt = init_rsttbl(esize, used + add);
> + struct RESTART_TABLE *rt;
> +
> + rt = init_rsttbl(esize, used + add);
> + if (!rt)
> + return NULL;
>
> memcpy(rt + 1, tbl + 1, esize * used);
>
> @@ -864,8 +872,11 @@ static inline void *alloc_rsttbl_idx(struct RESTART_TABLE **tbl)
> __le32 *e;
> struct RESTART_TABLE *t = *tbl;
>
> - if (!t->first_free)
> + if (!t->first_free) {
> *tbl = t = extend_rsttbl(t, 16, ~0u);
> + if (!t)
> + return NULL;
> + }
>
> off = le32_to_cpu(t->first_free);
>
> @@ -4482,6 +4493,10 @@ int log_replay(struct ntfs_inode *ni, bool *initialized)
> }
>
> dp = alloc_rsttbl_idx(&dptbl);
> + if (!dp) {
> + err = -ENOMEM;
> + goto out;
> + }
> dp->target_attr = cpu_to_le32(t16);
> dp->transfer_len = cpu_to_le32(t32 << sbi->cluster_bits);
> dp->lcns_follow = cpu_to_le32(t32);
> --
> 2.20.1
Hi Dan! Thanks, applied :)
Best regards
prev parent reply other threads:[~2021-08-27 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 11:52 [PATCH] fs/ntfs3: add checks for allocation failure Dan Carpenter
2021-08-24 16:02 ` Kari Argillander
2021-08-24 16:57 ` Dan Carpenter
2021-08-27 17:16 ` Konstantin Komarov [this message]
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=433bf776e8cf4fcc8dc9c1db4e43151b@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox