From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ed Bartosh <ed.bartosh@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 0/7] #11662 - wic should mount /boot
Date: Sat, 29 Jul 2017 08:40:19 +0100 [thread overview]
Message-ID: <1501314019.22282.199.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1501233796.git.ed.bartosh@linux.intel.com>
On Fri, 2017-07-28 at 12:29 +0300, Ed Bartosh wrote:
> This patchset adds /boot to the /etc/fstab of root partition, making
> it mounted on boot. It also fixes reporting and testing issues
> caused by this change.
>
> The patchset also fixes long standing bug: wic updated fstab
> inplace in rootfs directory. This causes other tasks working with
> rootfs directory to produce incorrect results or crash. This is
> fixed by hadlinking rootfs content to the temporary directory before
> updating fstab.
>
> This approach caused do_image_tar to fail with the error "file
> changed as we read it"
> as hardlinking changes files ctime. In order to solve this we had to
> modify do_image_tar to ignore file changes.
>
> Changes in v2: squashed patches by reviewer's request
> Changes in v3: unlink /etc/fstab in rootfs copy before updating it
> Changes in v4: used 'cp -a' instead of copyhardlinktree to avoid
> do_image_tar failure due to changed ctime
> Changes in v5: back to hardlinking. ignored tar exit code 1.
This patchset had a couple of issues, the tar command change was a
bashism '[[' so I changed it to '['. The cp -a change also doesn't work
cross device so I resurrected one of the previous versions of that
patch that uses copyhardlinktree.
As I mentioned previously, if we can speed up that function, great. We
do need to handle cross device linkage though (and there may be an
optimisation to have wic use the same device for the temp rootfs?).
The updated series is going through tests again now.
Cheers,
Richard
prev parent reply other threads:[~2017-07-29 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 9:29 [PATCH v5 0/7] #11662 - wic should mount /boot Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 1/7] image_types.bbclass: ignore tar exit code 1 Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 2/7] wic: copy rootfs directory before changing fstab Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 3/7] wic: use absolute paths in rootfs plugin Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 4/7] wic: rootfs: fix rootfs path reporting Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 5/7] wic: rootfs: make copied rootfs unique Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 6/7] wic: add /boot mount point to fstab by default Ed Bartosh
2017-07-28 9:29 ` [PATCH v5 7/7] oe-selftest: wic: fix test_quemu Ed Bartosh
2017-07-29 7:40 ` Richard Purdie [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=1501314019.22282.199.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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