All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Roxana Ciobanu <roxana.ciobanu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] latencytop: fix mount error
Date: Wed, 09 Jul 2014 21:50:06 +0100	[thread overview]
Message-ID: <1404939006.15985.62.camel@ted> (raw)
In-Reply-To: <478fc5d6fb31718ce9531eca7b6f626a1412c0c3.1404930808.git.roxana.ciobanu@intel.com>

On Wed, 2014-07-09 at 21:52 +0300, Roxana Ciobanu wrote:
> Added a check to ensure debugfs is not mounted before trying
> to mount it, because sysfs.sh already mounts it.
> 
> [ YOCTO #6498 ]
> 
> Signed-off-by: Roxana Ciobanu <roxana.ciobanu@intel.com>
> ---
>  .../latencytop-0.5/latencytop-fsync-mount.patch         | 17 +++++++++++++++++
>  meta/recipes-kernel/latencytop/latencytop_0.5.bb        |  5 +++--
>  2 files changed, 20 insertions(+), 2 deletions(-)
>  create mode 100644 meta/recipes-kernel/latencytop/latencytop-0.5/latencytop-fsync-mount.patch
> 
> diff --git a/meta/recipes-kernel/latencytop/latencytop-0.5/latencytop-fsync-mount.patch b/meta/recipes-kernel/latencytop/latencytop-0.5/latencytop-fsync-mount.patch
> new file mode 100644
> index 0000000..6de27d0
> --- /dev/null
> +++ b/meta/recipes-kernel/latencytop/latencytop-0.5/latencytop-fsync-mount.patch
> @@ -0,0 +1,17 @@
> +Index: latencytop-0.5/fsync.c
> +===================================================================
> +--- latencytop-0.5.orig/fsync.c	2014-07-09 16:56:32.565238023 +0300
> ++++ latencytop-0.5/fsync.c	2014-07-09 17:12:00.553237913 +0300
> +@@ -151,8 +151,10 @@
> +  * echo ftrace_printk > iter_ctrl 
> +  * echo 1 > tracing_on
> +  */
> +-	ret = system("/bin/mount -t debugfs none /sys/kernel/debug/");
> +-	if (!ret) 
> ++    ret = system("if ! grep -q debugfs /proc/filesystems; then"
> ++                 " /bin/mount -t debugfs none /sys/kernel/debug/"
> ++                 " else false; fi");
> ++    if (!ret)
> + 		return -1;
> + 	write_to_file("/sys/kernel/debug/tracing/current_tracer", "fsync");	
> + 	write_to_file("/sys/kernel/debug/tracing/iter_ctrl", "ftrace_printk");	

I'm not sure an upstream would accept what amounts to shell in the
system() call. Could we try listing that directories contents and then
only call the mount if the directory is empty/does not exist?

That patch should then be able to be sent upstream...

Cheers,

Richard


> diff --git a/meta/recipes-kernel/latencytop/latencytop_0.5.bb b/meta/recipes-kernel/latencytop/latencytop_0.5.bb
> index 516e2c5..9a95b92 100644
> --- a/meta/recipes-kernel/latencytop/latencytop_0.5.bb
> +++ b/meta/recipes-kernel/latencytop/latencytop_0.5.bb
> @@ -6,11 +6,12 @@ LIC_FILES_CHKSUM = "file://latencytop.c;endline=23;md5=ee9ea9b1415356e5734adad4a
>  
>  DEPENDS = "virtual/libintl ncurses glib-2.0  ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'gtk+', '', d)}"
>  
> -PR = "r3"
> +PR = "r4"
>  
>  SRC_URI = "http://www.latencytop.org/download/latencytop-${PV}.tar.gz \
>              file://latencytop-makefile.patch \
> -            file://latencytop-fsync.patch"
> +            file://latencytop-fsync.patch \
> +            file://latencytop-fsync-mount.patch"
>  
>  SRC_URI[md5sum] = "73bb3371c6ee0b0e68e25289027e865c"
>  SRC_URI[sha256sum] = "9e7f72fbea7bd918e71212a1eabaad8488d2c602205d2e3c95d62cd57e9203ef"
> -- 
> 1.9.1
> 




  reply	other threads:[~2014-07-09 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 18:52 [PATCH 0/1] Fix for YB6498 Roxana Ciobanu
2014-07-09 18:52 ` [PATCH 1/1] latencytop: fix mount error Roxana Ciobanu
2014-07-09 20:50   ` Richard Purdie [this message]
2014-07-10  8:59     ` Burton, Ross

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=1404939006.15985.62.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=roxana.ciobanu@intel.com \
    /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.