All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: WANG Chao <chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] dracut-lib: do not use cached CMDLINE in _getcmdline
Date: Thu, 05 Sep 2013 08:45:09 +0200	[thread overview]
Message-ID: <52282875.8030701@redhat.com> (raw)
In-Reply-To: <20130904161037.GA24055-UAAZkH0G2Ts1naxU1pY8ZxcY2uh10dtjAL8bYrjMMd8@public.gmane.org>

On 09/04/2013 06:10 PM, WANG Chao wrote:
> Cached CMDLINE doesn't work 100%. For example the following case,
> 
> 1. dracut starts to run dracut-cmdline.sh. CMDLINE is cached when calling
>    getarg 'rd.break=cmdline'.
> 2. In 92-parse-ibft.sh, ibft_to_cmdline() calls $(set_ifname ibft xx:xx..)
>    multiple times in each subshell.
> 3. In 1st call, set_ifname() will check $(getargs ifname) and write out
>    ifname=xxxx accordingly.
> 4. In 2nd call, set_ifname() will check $(getargs ifname) and it's wrong here.
>    Because in step 3, we introduce a new cmdline arg ifname=xxx, but CMDLINE
>    isn't updated. Thus we fail to get the new ifname arg.
> 
> It's doable to unset CMDLINE every time after a new cmdline arg is in. But
> unset should be done in the parent process, because unset CMDLINE in a
> subshell won't unset CMDLINE in its parent or sibling process. And also it's
> painful to unset CMDLINE every time. In the future, functions and code
> snippet could probably separate or move to other file, the unset CMDLINE could
> malfunction again like this time.
> 
> So I'm thinking not to cache CMDLINE. It's doesn't hurt to re-read all the
> cmdline args everytime. Because it's in initramfs, a non cached _getcmdline()
> should be fast enough.
> 
> Please consider!
> 
> Thanks
> WANG Chao
> ---
>  modules.d/99base/dracut-lib.sh | 33 ++++++++++++++++-----------------
>  1 file changed, 16 insertions(+), 17 deletions(-)
> 
> diff --git a/modules.d/99base/dracut-lib.sh b/modules.d/99base/dracut-lib.sh
> index 0d5cab9..ef8c5a3 100755
> --- a/modules.d/99base/dracut-lib.sh
> +++ b/modules.d/99base/dracut-lib.sh
> @@ -103,23 +103,22 @@ _getcmdline() {
>      local _line
>      local _i
>      unset _line
> -    if [ -z "$CMDLINE" ]; then
> -        unset CMDLINE_ETC CMDLINE_ETC_D
> -        if [ -e /etc/cmdline ]; then
> -            while read -r _line; do
> -                CMDLINE_ETC="$CMDLINE_ETC $_line";
> -            done </etc/cmdline;
> -        fi
> -        for _i in /etc/cmdline.d/*.conf; do
> -            [ -e "$_i" ] || continue
> -            while read -r _line; do
> -                CMDLINE_ETC_D="$CMDLINE_ETC_D $_line";
> -            done <"$_i";
> -        done
> -        if [ -e /proc/cmdline ]; then
> -            read -r CMDLINE </proc/cmdline;
> -            CMDLINE="$CMDLINE_ETC_D $CMDLINE_ETC $CMDLINE"
> -        fi
> +    unset CMDLINE_ETC CMDLINE_ETC_D
> +
> +    if [ -e /etc/cmdline ]; then
> +        while read -r _line; do
> +            CMDLINE_ETC="$CMDLINE_ETC $_line";
> +        done </etc/cmdline;
> +    fi
> +    for _i in /etc/cmdline.d/*.conf; do
> +        [ -e "$_i" ] || continue
> +        while read -r _line; do
> +            CMDLINE_ETC_D="$CMDLINE_ETC_D $_line";
> +        done <"$_i";
> +    done
> +    if [ -e /proc/cmdline ]; then
> +        read -r CMDLINE </proc/cmdline;
> +        CMDLINE="$CMDLINE_ETC_D $CMDLINE_ETC $CMDLINE"
>      fi
>  }
>  
> 

Yes, you are right! Will merge! Thanks!!

      parent reply	other threads:[~2013-09-05  6:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 16:10 [PATCH] dracut-lib: do not use cached CMDLINE in _getcmdline WANG Chao
     [not found] ` <20130904161037.GA24055-UAAZkH0G2Ts1naxU1pY8ZxcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2013-09-05  6:45   ` Harald Hoyer [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=52282875.8030701@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.