Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ming Liu <ming.liu@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel.bbclass: handles symbolic KERNEL_OUTPUT in bundle_initramfs task
Date: Wed, 13 Nov 2013 10:03:07 +0800	[thread overview]
Message-ID: <5282DDDB.4030709@windriver.com> (raw)
In-Reply-To: <CADkTA4OqaxJyRp-T298LG-Jm36tUNkZXvKawoWGtKOCETARTvA@mail.gmail.com>

On 11/12/2013 11:07 PM, Bruce Ashfield wrote:
> On Tue, Nov 12, 2013 at 3:17 AM, Ming Liu <ming.liu@windriver.com> wrote:
>> In many cases, KERNEL_OUTPUT is a symbolic link to the real bootable image,
>> but in bundle_initramfs task, it's not considered so that the KERNEL_OUTPUT
>> is being renamed/restored as a regular file, this leads it finally point to
>> a incorrect target, or even worse, break the bundle_initramfs task for
>> KERNEL_OUTPUT is not going to be regenerated in case it is a symbolic link
>> to vmlinux.
>>
>> Also, we need move bundle_initramfs after kernel_link_vmlinux.
>>
>> Signed-off-by: Ming Liu <ming.liu@windriver.com>
>> ---
>>   meta/classes/kernel.bbclass | 24 ++++++++++++++++++++----
>>   1 file changed, 20 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
>> index a4db9f5..2ec09ae 100644
>> --- a/meta/classes/kernel.bbclass
>> +++ b/meta/classes/kernel.bbclass
>> @@ -123,13 +123,29 @@ do_bundle_initramfs () {
>>          if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
>>                  echo "Creating a kernel image with a bundled initramfs..."
>>                  copy_initramfs
>> -               if [ -e ${KERNEL_OUTPUT} ] ; then
>> +               # Backuping kernel image relies on its type(regular file or symbolic link)
>> +               linkpath=""
>> +               realpath=""
>> +               if [ -h ${KERNEL_OUTPUT} ] ; then
>> +                       linkpath=`readlink -n ${KERNEL_OUTPUT}`
>> +                       realpath=`readlink -fn ${KERNEL_OUTPUT}`
>> +                       mv -f $realpath $realpath.bak
>> +               elif [ -f ${KERNEL_OUTPUT} ]; then
>>                          mv -f ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}.bak
>>                  fi
>>                  use_alternate_initrd=CONFIG_INITRAMFS_SOURCE=${B}/usr/${INITRAMFS_IMAGE}-${MACHINE}.cpio
>>                  kernel_do_compile
>> -               mv -f ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}.initramfs
>> -               mv -f ${KERNEL_OUTPUT}.bak ${KERNEL_OUTPUT}
>> +               # Restoring kernel image
>> +               if [ ! -z $realpath ]; then
> Why not  if [ -n "$realpath" ] ? I always find that reads easier.
OK, that would be better.
>
>> +                       mv -f $realpath $realpath.initramfs
>> +                       mv -f $realpath.bak $realpath
>> +                       cd ${B}/$(dirname ${KERNEL_OUTPUT})
>> +                       ln -sf $linkpath
>> +                       ln -sf $linkpath.initramfs
> Won't the links just follow .. they are symbolic after all. Since things are
> being put back in place. Or are the names changing underneath ?
Indeed, 'ln -sf $linkpath' is unnecessary, I can remove it, but for the 
initramfs link, we must create it here for it doesn't exist before this.
>
>> +               else
>> +                       mv -f ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}.initramfs
>> +                       mv -f ${KERNEL_OUTPUT}.bak ${KERNEL_OUTPUT}
>> +               fi
>>                  # Update install area
>>                  echo "There is kernel image bundled with initramfs: ${B}/${KERNEL_OUTPUT}.initramfs"
>>                  install -m 0644 ${B}/${KERNEL_OUTPUT}.initramfs ${D}/boot/${KERNEL_IMAGETYPE}-initramfs-${MACHINE}.bin
>> @@ -152,7 +168,7 @@ python do_devshell_prepend () {
>>       os.environ["LDFLAGS"] = ''
>>   }
>>
>> -addtask bundle_initramfs after do_compile before do_build
>> +addtask bundle_initramfs after do_kernel_link_vmlinux before do_build
> This isn't explained in the commit log.
So, I will put it into another commit, I will send the V1 soon including 
all the changes discussed above.

//Ming Liu

>
> Bruce
>
>>   kernel_do_compile() {
>>          unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
>> --
>> 1.8.4.1
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>



  reply	other threads:[~2013-11-13  2:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12  8:17 [PATCH] kernel.bbclass: handles symbolic KERNEL_OUTPUT in bundle_initramfs task Ming Liu
2013-11-12 15:07 ` Bruce Ashfield
2013-11-13  2:03   ` Ming Liu [this message]
2013-11-13  2:18     ` Otavio Salvador
2013-11-13  2:21       ` Ming Liu

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=5282DDDB.4030709@windriver.com \
    --to=ming.liu@windriver.com \
    --cc=bruce.ashfield@gmail.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