From: David Disseldorp <ddiss@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: Martin Wilck <mwilck@suse.com>,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [PATCH v5 2/5] initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option
Date: Wed, 5 Jan 2022 21:10:51 +0100 [thread overview]
Message-ID: <20220105211051.7c1c5ab9@suse.de> (raw)
In-Reply-To: <20211213232007.26851-3-ddiss@suse.de>
On Tue, 14 Dec 2021 00:20:05 +0100, David Disseldorp wrote:
> --- a/init/initramfs.c
> +++ b/init/initramfs.c
> @@ -17,6 +17,8 @@
...
> -static void __init dir_add(const char *name, time64_t mtime)
> -{
> - struct dir_entry *de = kmalloc(sizeof(struct dir_entry), GFP_KERNEL);
> - if (!de)
> - panic_show_mem("can't allocate dir_entry buffer");
> - INIT_LIST_HEAD(&de->list);
> - de->name = kstrdup(name, GFP_KERNEL);
> - de->mtime = mtime;
> - list_add(&de->list, &dir_list);
> -}
...
> --- /dev/null
> +++ b/init/initramfs_mtime.h
...
> +static void __init dir_add(const char *name, time64_t mtime)
> +{
> + struct dir_entry *de = kmalloc(sizeof(struct dir_entry), GFP_KERNEL);
> + if (!de)
> + panic("can't allocate dir_entry buffer");
> + INIT_LIST_HEAD(&de->list);
> + de->name = kstrdup(name, GFP_KERNEL);
> + de->mtime = mtime;
> + list_add(&de->list, &dir_list);
> +}
I might as well fix the unhandled kstrdup() failure, rather than copying
it here. I'll post another round which allocates the "name" buffer via
the dir_entry kmalloc() call.
next prev parent reply other threads:[~2022-01-05 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 23:20 initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME David Disseldorp
2021-12-13 23:20 ` [PATCH v5 1/5] initramfs: refactor do_header() cpio magic checks David Disseldorp
2021-12-13 23:20 ` [PATCH v5 2/5] initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option David Disseldorp
2022-01-05 20:10 ` David Disseldorp [this message]
2021-12-13 23:20 ` [PATCH v5 3/5] gen_init_cpio: fix short read file handling David Disseldorp
2021-12-13 23:20 ` [PATCH v5 4/5] gen_init_cpio: support file checksum archiving David Disseldorp
2021-12-13 23:20 ` [PATCH v5 5/5] initramfs: support cpio extraction with file checksums David Disseldorp
2021-12-20 16:05 ` initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME David Disseldorp
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=20220105211051.7c1c5ab9@suse.de \
--to=ddiss@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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).