[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VuPNwr-NhvDjH3stU7jCPy_+Cz2z3qTtr5EO2ozxsjkw@mail.gmail.com>
Date: Fri, 31 May 2019 14:01:52 -0700
From: Doug Anderson <dianders@...omium.org>
To: Evan Green <evgreen@...omium.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
LKML <linux-kernel@...r.kernel.org>,
Nicolas Boichat <drinkcat@...omium.org>,
Marc Zyngier <marc.zyngier@....com>,
Manuel Traut <manut@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] scripts/decode_stacktrace: Accept dash/underscore in modules
Hi,
On Fri, May 31, 2019 at 1:59 PM Evan Green <evgreen@...omium.org> wrote:
>
> The manpage for modprobe mentions that dashes and underscores are
> treated interchangeably in module names. The stack trace dumps seem
> to print module names with underscores. Use bash to replace _ with
> the pattern [-_] so that file names with dashes or underscores can be
> found.
>
> For example, this line:
> [ 27.919759] hda_widget_sysfs_init+0x2b8/0x3a5 [snd_hda_core]
>
> should find a module named snd-hda-core.ko.
>
> Signed-off-by: Evan Green <evgreen@...omium.org>
> ---
>
> Note: This should apply atop linux-next.
>
> Thanks to Doug for showing me the bash string substitution magic.
>
> ---
> scripts/decode_stacktrace.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/decode_stacktrace.sh b/scripts/decode_stacktrace.sh
> index fa704f17275e..13e5fbafdf2f 100755
> --- a/scripts/decode_stacktrace.sh
> +++ b/scripts/decode_stacktrace.sh
> @@ -28,7 +28,7 @@ parse_symbol() {
> local objfile=${modcache[$module]}
> else
> [[ $modpath == "" ]] && return
> - local objfile=$(find "$modpath" -name "$module.ko*" -print -quit)
> + local objfile=$(find "$modpath" -name "${module//_/[-_]}.ko*" -print -quit)
> [[ $objfile == "" ]] && return
> modcache[$module]=$objfile
> fi
Reviewed-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists