From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: <viro@zeniv.linux.org.uk>,
<linux-security-module@vger.kernel.org>,
<linux-integrity@vger.kernel.org>, <initramfs@vger.kernel.org>,
<linux-api@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <bug-cpio@gnu.org>,
<zohar@linux.vnet.ibm.com>, <silviu.vlasceanu@huawei.com>,
<dmitry.kasatkin@huawei.com>, <takondra@cisco.com>,
<kamensky@cisco.com>, <hpa@zytor.com>, <arnd@arndb.de>,
<rob@landley.net>, <james.w.mcmechan@gmail.com>,
<niveditas98@gmail.com>, Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH v4 3/3] gen_init_cpio: add support for file metadata
Date: Thu, 16 Jun 2022 17:16:03 +0200 [thread overview]
Message-ID: <20220616151603.GA4400@lxhi-065> (raw)
In-Reply-To: <20190523121803.21638-4-roberto.sassu@huawei.com>
Hello Roberto,
On Do, Mai 23, 2019 at 02:18:03 +0200, Roberto Sassu wrote:
> This patch adds support for file metadata (only TYPE_XATTR metadata type).
> gen_init_cpio has been modified to read xattrs from files that will be
> added to the image and to include file metadata as separate files with the
> special name 'METADATA!!!'.
>
> This behavior can be selected by setting the desired file metadata type as
> value for CONFIG_INITRAMFS_FILE_METADATA.
>
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> ---
> usr/Kconfig | 8 +++
> usr/Makefile | 4 +-
> usr/gen_init_cpio.c | 137 ++++++++++++++++++++++++++++++++++++--
> usr/gen_initramfs_list.sh | 10 ++-
> 4 files changed, 150 insertions(+), 9 deletions(-)
>
> diff --git a/usr/gen_init_cpio.c b/usr/gen_init_cpio.c
[..]
> +static int write_xattrs(const char *path)
> +{
[..]
> + while (list_ptr < xattr_list + list_len) {
> + name_len = strlen(list_ptr);
PVS-Studio 7.19 reports at this line:
=> usr/gen_init_cpio.c 84 warn V769
=> The 'xattr_list' pointer in the 'xattr_list + list_len' expression could be nullptr.
=> In such case, resulting value will be senseless and it should not be used. Check lines: 84, 69.
I guess the finding is valid and it's due to the fact that
the malloc return value is not being checked/sanitized?
BR, Eugeniu.
next prev parent reply other threads:[~2022-06-16 15:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:18 [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-05-23 12:18 ` [PATCH v4 1/3] initramfs: add file metadata Roberto Sassu
2022-06-15 17:54 ` Eugeniu Rosca
2019-05-23 12:18 ` [PATCH v4 2/3] initramfs: read metadata from special file METADATA!!! Roberto Sassu
2019-07-01 12:54 ` Mimi Zohar
2019-05-23 12:18 ` [PATCH v4 3/3] gen_init_cpio: add support for file metadata Roberto Sassu
2019-06-30 15:27 ` Mimi Zohar
2022-06-16 14:47 ` Eugeniu Rosca
2022-06-16 15:16 ` Eugeniu Rosca [this message]
2022-06-30 15:06 ` Roberto Sassu
2022-06-30 20:38 ` Eugeniu Rosca
2019-06-03 9:31 ` [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk Roberto Sassu
2019-06-03 18:32 ` Rob Landley
2019-06-26 8:15 ` Roberto Sassu
2019-06-30 15:39 ` Mimi Zohar
2019-07-01 13:42 ` Roberto Sassu
2019-07-01 14:31 ` Mimi Zohar
2019-07-15 16:54 ` Roberto Sassu
2019-07-24 15:34 ` Roberto Sassu
2022-06-09 10:26 ` Eugeniu Rosca
2022-06-09 11:05 ` Roberto Sassu
2022-06-10 15:33 ` Eugeniu Rosca
2022-06-10 15:38 ` Roberto Sassu
2022-06-15 9:27 ` Eugeniu Rosca
2022-07-18 16:36 ` Jim Baxter
2022-07-18 16:49 ` Roberto Sassu
2022-07-18 18:08 ` Jim Baxter
2022-07-19 6:55 ` Roberto Sassu
2022-07-19 11:50 ` Rob Landley
2022-07-19 12:26 ` Roberto Sassu
2022-07-19 14:14 ` Rob Landley
2022-07-20 11:52 ` Roberto Sassu
2022-07-29 10:37 ` Jim Baxter
2022-07-30 9:39 ` Rob Landley
2022-07-19 11:33 ` Rob Landley
2022-07-19 11:00 ` Rob Landley
2019-07-01 13:22 ` Mimi Zohar
2022-06-15 15:50 ` Alexander Lobakin
2022-06-15 16:03 ` Roberto Sassu
2022-06-16 13:24 ` Eugeniu Rosca
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=20220616151603.GA4400@lxhi-065 \
--to=erosca@de.adit-jv.com \
--cc=arnd@arndb.de \
--cc=bug-cpio@gnu.org \
--cc=dmitry.kasatkin@huawei.com \
--cc=hpa@zytor.com \
--cc=initramfs@vger.kernel.org \
--cc=james.w.mcmechan@gmail.com \
--cc=kamensky@cisco.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=niveditas98@gmail.com \
--cc=rob@landley.net \
--cc=roberto.sassu@huawei.com \
--cc=roscaeugeniu@gmail.com \
--cc=silviu.vlasceanu@huawei.com \
--cc=takondra@cisco.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).