public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: <webman@manfbraun.de>
To: "'David Smith'" <dsmith@redhat.com>,
	"'Frank Ch. Eigler'" <fche@redhat.com>
Cc: <systemtap@sourceware.org>
Subject: RE: udp.sendmsg
Date: Sat, 03 Sep 2016 14:31:00 -0000	[thread overview]
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAOosgHnoPqdNlUO2DUrQ/DfCgAAAEAAAAJOIsAtXCKNKl44tEFrnutoBAAAAAA==@manfbraun.de> (raw)
In-Reply-To: <f0b3fbe9-1100-c7d6-35b7-9b92157f6202@redhat.com>

Hello !

Thanks for this good information!
I just removed this code snippet and only use "execname()"
and the error went away!

I am new to Linux and it is really very hard for me ;-)
But I was able to use SystemTap to track some Virtualbox
calls, just to show them, what brings to whole server
to stop (!!) - but they are not interested .... and now,
I am trying to avoid Virtualbox like the devil the
holy water ;-)

So, this is the same machine and was my new delay ....

Best regards,
Manfred

BTW: I am of that type, that will not use "--skip-badvars",
at least, in a permanent running script ;-)

> -----Original Message-----
> From: systemtap-owner@sourceware.org [mailto:systemtap-
> owner@sourceware.org] On Behalf Of David Smith
> Sent: Thursday, August 25, 2016 9:52 PM
> To: webman@manfbraun.de; 'Frank Ch. Eigler'
> Cc: systemtap@sourceware.org
> Subject: Re: udp.sendmsg
> 
> On 08/25/2016 11:18 AM, webman@manfbraun.de wrote:
> > Hello !
> >
> > Many thanks for your answer!
> > Sometimes, writing "it's not working" reactivates some areas
> > in the own brain, do dig deeper ...
> > What ist failing for me, is my modified version of the original
> > script. I run the original and no errors at all ... ;-)
> >
> > So, here is MY version - with my little newbies thinking about
> > this type of scripts ;-)
> >
> > =======================
> > probe begin { printf("Monitoring use of port 53\n") }
> > probe end { printf("Stopped.\n") }
> >
> > probe udp.sendmsg {
> >         if ( dport == 53 ) {
> >                 task = pid2task(pid());
> >                 printf(
> >                         "UDP53 %5d.%6d %15s %d(%s/%s) %d(%s)\n",
> >                         gettimeofday_s(),
> >                         gettimeofday_ms(),
> >                         daddr,
> >                         pid(),
> >                         task_execname(task),
> >                         execname(),
> >                         ppid(),
> >                         pexecname()
> >                         )
> >         }
> > }
> 
> OK, here's a couple of things about your script.
> 
>   task = pid2task(pid())
> 
> is the same thing as:
> 
>   task = task_current()
> 
> Plus, since task is the current task, task_execname(task) and execname()
> are always going to return the same string.
> 
> So, at that point you really don't need your 'task' variable.
> 
> If you are still getting that kernel_string copy fault error, you'll
> need to delete/replace one function call at a time so that we can narrow
> down which function is causing the fault.
> 
> --
> David Smith
> dsmith@redhat.com
> Red Hat
> http://www.redhat.com
> 256.217.0141 (direct)
> 256.837.0057 (fax)


      parent reply	other threads:[~2016-09-03 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 20:58 udp.sendmsg webman
2016-07-11 10:09 ` udp.sendmsg Timo Juhani Lindfors
2016-07-19 14:41 ` udp.sendmsg Frank Ch. Eigler
2016-08-19  2:18   ` udp.sendmsg webman
2016-08-19 16:32     ` udp.sendmsg David Smith
2016-08-25 16:19       ` udp.sendmsg webman
2016-08-25 19:52         ` udp.sendmsg David Smith
2016-08-25 19:59           ` udp.sendmsg Frank Ch. Eigler
2016-09-03 14:31           ` webman [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=''\!'&'\!'AAAAAAAAAAAYAAAAAAAAAOosgHnoPqdNlUO2DUrQ/DfCgAAAEAAAAJOIsAtXCKNKl44tEFrnutoBAAAAAA==@manfbraun.de' \
    --to=webman@manfbraun.de \
    --cc=dsmith@redhat.com \
    --cc=fche@redhat.com \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).