From: MottiKumar Babu <mottikumarbabu@gmail.com>
To: cem@kernel.org
Cc: djwong@kernel.org, chandanbabu@kernel.org, dchinner@redhat.com,
zhangjiachen.jaycee@bytedance.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, anupnewsmail@gmail.com,
skhan@linuxfoundation.org
Subject: [PATCH] Follow-up on Submitted Patch: Fix out-of-bounds access in xfs_bmapi_allocate
Date: Mon, 28 Oct 2024 02:02:28 +0530 [thread overview]
Message-ID: <20241027203231.20251-1-mottikumarbabu@gmail.com> (raw)
In-Reply-To: <20241027193541.14212-1-mottikumarbabu@gmail.com>
Hi everyone,
I hope this message finds you well. I wanted to follow up on my previously submitted patch titled "[PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork."
As a reminder, this patch addresses an issue reported by Coverity Scan (CID 1633175), where the variable `whichfork` can take invalid values, specifically `2`, leading to an out-of-bounds access in `xfs_bmbt_init_cursor`. The added validation check ensures that `whichfork` remains within the valid range of 0 or 1. If it falls outside this range, the function will return `-EINVAL`, enhancing the code's robustness and preventing potential crashes or undefined behavior.
I appreciate any feedback or suggestions you might have.
Best,
MottiKumar Babu
mottikumarbabu@gmail.com
next prev parent reply other threads:[~2024-10-27 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 19:35 [PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork MottiKumar Babu
2024-10-27 20:32 ` MottiKumar Babu [this message]
2024-10-27 22:53 ` Dave Chinner
2024-10-28 8:46 ` Christoph Hellwig
2024-11-01 3:36 ` kernel test robot
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=20241027203231.20251-1-mottikumarbabu@gmail.com \
--to=mottikumarbabu@gmail.com \
--cc=anupnewsmail@gmail.com \
--cc=cem@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=zhangjiachen.jaycee@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox