linux-kernel - Re: [PATCH] INITRAMFS: Add option to preserve mtime from INITRAMFS cpio images

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Sep 2008 15:36:37 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Nye Liu <nyet@....com>
Cc:	nyet@...t.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] INITRAMFS: Add option to preserve mtime from INITRAMFS
 cpio images

On Wed, 3 Sep 2008 15:31:14 -0700
Nye Liu <nyet@....com> wrote:

> On Wed, Sep 03, 2008 at 03:22:31PM -0700, Andrew Morton wrote:
> > > From: Nye Liu <nyet@...t.org>
> > > 
> > > When unpacking the cpio into the initramfs, mtimes are not preserved by
> > > default. This patch adds an INITRAMFS_PRESERVE_MTIME option that allows mtimes
> > > stored in the cpio image to be used when constructing the initramfs. For
> > > embedded applications that run exclusively out of the initramfs, this is
> > > invaluable.
> > 
> > Why is it "invlauable".  Please explain this value in full detail -
> > it's the whole reason for merging the patch!
> 
> When building embedded application initramfs images, its nice to know
> when the files were actually created during the build process - that
> makes it easier to see what files were modified when so we can compare
> the files that are being used on the image with the files used during
> the build process. This might help (for example) to determine if the
> target system has all the updated files you expect to see w/o having to
> check MD5s etc.
> 
> In our environment, the whole system runs off the initramfs partition,
> and seeing the modified times of the shared libraries (for example)
> helps us find bugs that may have been introduced by the build system
> incorrectly propogating outdated shared libraries into the image.
> 
> Similarly, many of the initializion/configuration files in /etc
> might be dynamically built by the build system, and knowing when
> they were modified helps us sanity check whether the target system
> has the "latest" files etc.
> 
> Finally, we might use last modified times to determine whether a
> hot fix should be applied or not to the running ramfs.
> 

Thanks, I updated the changelog.

> > gargh.  Why does this work?  It's normally a big fail to pass a kernel
> > address into a system call.  I guess we're running under KERNEL_DS here
> > and getname() and strncpy_from_user() did the right thing.
> > 
> > On what CPU architecture was this tested?
> > 
> > Wouldn't it be simpler to put a timespec into struct dir_entry then go
> > direct to do_utimes() here?
> > 

Did you see this stuff?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/