From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: tytso@mit.edu, darrick.wong@oracle.com, djwong@kernel.org,
adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
joneslee@google.com, Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH 3/3] ext4: fsmap: Remove duplicated initialization
Date: Wed, 22 Feb 2023 13:12:11 +0000 [thread overview]
Message-ID: <20230222131211.3898066-4-tudor.ambarus@linaro.org> (raw)
In-Reply-To: <20230222131211.3898066-1-tudor.ambarus@linaro.org>
All members of struct ext4_fsmap_head were already initialized with zero
in the caller, ext4_ioc_getfsmap(), remove duplicated initialization.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
---
fs/ext4/fsmap.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/ext4/fsmap.c b/fs/ext4/fsmap.c
index a27d9f0967b7..348eaffaa4d8 100644
--- a/fs/ext4/fsmap.c
+++ b/fs/ext4/fsmap.c
@@ -668,8 +668,6 @@ int ext4_getfsmap(struct super_block *sb, struct ext4_fsmap_head *head,
int i;
int error = 0;
- head->fmh_entries = 0;
-
/* Set up our device handlers. */
memset(handlers, 0, sizeof(handlers));
handlers[0].gfd_dev = new_encode_dev(sb->s_bdev->bd_dev);
--
2.39.2.637.g21b0678d19-goog
prev parent reply other threads:[~2023-02-22 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 13:12 [PATCH 0/3] ext4: fsmap: Improve key validation Tudor Ambarus
2023-02-22 13:12 ` [PATCH 1/3] ext4: fsmap: Fix crash caused by poor " Tudor Ambarus
2023-02-22 13:12 ` [PATCH 2/3] ext4: fsmap: Consolidate fsmap_head checks Tudor Ambarus
2023-03-04 2:56 ` Darrick J. Wong
2023-03-06 15:55 ` Tudor Ambarus
2023-02-22 13:12 ` Tudor Ambarus [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=20230222131211.3898066-4-tudor.ambarus@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=adilger.kernel@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=joneslee@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).