mhiramat at redhat dot com | 1 May 2008 02:05
Favicon

[Bug runtime/5648] Unaligned access to memory in _stp_vsnprintf() on ia64


------- Additional Comments From mhiramat at redhat dot com  2008-05-01 00:05 -------
I've found that another code causes unaligned access on ia64...

$ sudo stap -m end1b -bv end1.stp  -o /dev/null
$ dmesg 
...
end1b: systemtap: 0.7/0.131, base: a000000204a20000, memory:
633752+71360+384+14000 data+text+ctx+net, probes: 2
kernel unaligned access to 0xa000000204ad5fee, ip=0xa000000204a23761
kernel unaligned access to 0xa000000204ad9fbe, ip=0xa000000204a23760
kernel unaligned access to 0xa000000204addf96, ip=0xa000000204a23761
kernel unaligned access to 0xa000000204ae1f66, ip=0xa000000204a23760
kernel unaligned access to 0xa000000204ae5f3e, ip=0xa000000204a23761

$nm end1b.ko | sort
...
00000000000035c0 T stp_print_flush
0000000000003800 t probe_1059

This time, ip was in stap_print_flush()...

--

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

http://sourceware.org/bugzilla/show_bug.cgi?id=5648

(Continue reading)

fche at redhat dot com | 1 May 2008 21:31
Favicon

[Bug releng/6474] New: build setuid staprun with -fpie

For slightly greater security, let's consider building staprun with
execshield-friendly options like C*FLAGS=-fpie -fPIC, LDFLAGS=-pie.
(Autoconf'd of course.)

--

-- 
           Summary: build setuid staprun with -fpie
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: releng
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com

http://sourceware.org/bugzilla/show_bug.cgi?id=6474

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

fche at redhat dot com | 1 May 2008 23:32
Favicon

[Bug releng/6474] build setuid staprun with -fpie


------- Additional Comments From fche at redhat dot com  2008-05-01 21:32 -------
commit 8a0dc84; applies to not just staprun but stap and stapio as well.

--

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

http://sourceware.org/bugzilla/show_bug.cgi?id=6474

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

dsmith at redhat dot com | 2 May 2008 17:40
Favicon

[Bug translator/6477] New: without debuginfo, compiling a process probe script fails silently

Without kernel debuginfo installed, observe the following:

# stap -vvv -e 'probe process("/bin/program_that_does_not_exist").death { }'
SystemTap translator/driver (version 0.7/0.131 git branch work, commit 8c392b1a
+ changes)
Copyright (C) 2005-2008 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Created temporary directory "/tmp/stapFUASeP"
Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 1
Searched '/usr/local/share/systemtap/tapset/*.stp', found 38
Pass 1: parsed user script and 39 library script(s) in 420usr/20sys/449real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 2 embed(s), 0 global(s) in
10usr/0sys/8real ms.
probe_1063 locks nothing
Pass 3: translated to C into
"/tmp/stapFUASeP/stap_30b9314753167af7ce6a944b8c61ae71_431.c" in
0usr/10sys/3real ms.
Pass 3: translation failed.  Try again with more '-v' (verbose) options.
Running rm -rf /tmp/stapFUASeP

Even if this shouldn't compile, a better error message (or any for that matter)
should be emitted.

(This bug might be related to bug #4311)

--

-- 
           Summary: without debuginfo, compiling a process probe script
                    fails silently
           Product: systemtap
           Version: unspecified
(Continue reading)

fche at redhat dot com | 2 May 2008 18:15
Favicon

[Bug translator/6477] without debuginfo, compiling a process probe script fails silently


------- Additional Comments From fche at redhat dot com  2008-05-02 16:15 -------
Chances are the problem is in the code associated with
collecting symbol table data.  I'm already working on the
area, and will probably end up borrowing code from jkenisto's
dwarfless branch (looking for System.map?) order to do
the deed.

--

-- 

http://sourceware.org/bugzilla/show_bug.cgi?id=6477

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Peter Teoh | 2 May 2008 18:35
Picon
Gravatar

Differences of stack traces between linux kernel and systap

Notice the diference in the stack trace between systap:

 0xc047ecf1 : slab_pad_check+0x1/0xb9
 0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
 0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
 0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
 0xc0434e33 : send_signal+0x4a/0x10e
 0xc0435476 : __group_send_sig_info+0x6e/0x8c
 0xc0435a8e : group_send_sig_info+0x43/0x58
 0xc048d42a : send_sigio+0xe3/0x133
 0xc048d4c9 : __kill_fasync+0x4f/0x52
 0xc048dc78 : vfs_ioctl+0x0/0x6c
 0xf8943ef5 : snd_timer_user_tinterrupt+0x11f/0x13c [snd_timer]
 0xf8942c74 : snd_timer_interrupt+0x1de/0x23f [snd_timer]
 0xf896667d : snd_pcm_period_elapsed+0xf0/0x134 [snd_pcm]
 0xf8bfef49 : azx_interrupt+0x60/0xa4 [snd_hda_intel]
 0xc0459eab : handle_IRQ_event+0x26/0x4d

And that of the linux kernel (latest patch):

 [<c042bad6>] warn_on_slowpath+0x46/0x56
 [<c0415a33>] ? apic_wait_icr_idle+0x16/0x1d
 [<c0415243>] ? __send_IPI_dest_field+0x50/0x54
 [<c04020e5>] ? send_IPI_mask+0xd/0xf
 [<c046773c>] ? get_pageblock_flags_group+0x50/0x6e
 [<c046777e>] ? get_pageblock_migratetype+0x24/0x27
 [<c0468472>] ? free_hot_page+0xf/0x11
 [<c0468494>] ? __free_pages+0x20/0x2b
 [<c047f471>] ? __free_slab+0xac/0xb4
 [<c0480754>] kmem_cache_destroy+0xfe/0x108
(Continue reading)

Frank Ch. Eigler | 2 May 2008 18:55
Picon
Favicon
Gravatar

Re: Differences of stack traces between linux kernel and systap

"Peter Teoh" <htmldeveloper <at> gmail.com> writes:

> Notice the diference in the stack trace between systap:
>[...]
> And that of the linux kernel (latest patch):
>  [<c042bad6>] warn_on_slowpath+0x46/0x56
>  [<c0415a33>] ? apic_wait_icr_idle+0x16/0x1d
>  [<c0415243>] ? __send_IPI_dest_field+0x50/0x54
>[...]
> The difference lies in the "?" in front of the function, which is to
> indicate that this function has just been executed and returned, so it
> is no longer on the stack.

I'm sorry, I don't know what that could possibly mean.  A function
that has executed and returned should leave no traces on the stack.
Can you identify the "latest patch" that purports to implement this?

> Is it possible to modify the systap stacktrace dump to be inlined
> with that of the kernel?  It this not more informative?

You mean integrated?  Perhaps.  In the mean time, a more pressing
thing to do is to get userspace backtraces working.

- FChE

Andy Gospodarek | 2 May 2008 19:15
Picon
Favicon

Re: Differences of stack traces between linux kernel and systap

On Sat, May 03, 2008 at 12:35:41AM +0800, Peter Teoh wrote:
> Notice the diference in the stack trace between systap:
> 
>  0xc047ecf1 : slab_pad_check+0x1/0xb9
>  0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
>  0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
>  0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
>  0xc0434e33 : send_signal+0x4a/0x10e
>  0xc0435476 : __group_send_sig_info+0x6e/0x8c
>  0xc0435a8e : group_send_sig_info+0x43/0x58
>  0xc048d42a : send_sigio+0xe3/0x133
>  0xc048d4c9 : __kill_fasync+0x4f/0x52
>  0xc048dc78 : vfs_ioctl+0x0/0x6c
>  0xf8943ef5 : snd_timer_user_tinterrupt+0x11f/0x13c [snd_timer]
>  0xf8942c74 : snd_timer_interrupt+0x1de/0x23f [snd_timer]
>  0xf896667d : snd_pcm_period_elapsed+0xf0/0x134 [snd_pcm]
>  0xf8bfef49 : azx_interrupt+0x60/0xa4 [snd_hda_intel]
>  0xc0459eab : handle_IRQ_event+0x26/0x4d
> 
> 
> And that of the linux kernel (latest patch):
> 
>  [<c042bad6>] warn_on_slowpath+0x46/0x56
>  [<c0415a33>] ? apic_wait_icr_idle+0x16/0x1d
>  [<c0415243>] ? __send_IPI_dest_field+0x50/0x54
>  [<c04020e5>] ? send_IPI_mask+0xd/0xf
>  [<c046773c>] ? get_pageblock_flags_group+0x50/0x6e
>  [<c046777e>] ? get_pageblock_migratetype+0x24/0x27
>  [<c0468472>] ? free_hot_page+0xf/0x11
>  [<c0468494>] ? __free_pages+0x20/0x2b
(Continue reading)

Peter Teoh | 2 May 2008 19:53
Picon
Gravatar

Re: Differences of stack traces between linux kernel and systap

On 5/3/08, Andy Gospodarek <gospo <at> redhat.com> wrote:
> On Sat, May 03, 2008 at 12:35:41AM +0800, Peter Teoh wrote:
>  > Notice the diference in the stack trace between systap:
>  >
>  >  0xc047ecf1 : slab_pad_check+0x1/0xb9
>  >  0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
>  >  0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
>  >  0xc064dd69 : kretprobe_trampoline_holder+0x18/0x38
>  >  0xc0434e33 : send_signal+0x4a/0x10e
>  >  0xc0435476 : __group_send_sig_info+0x6e/0x8c
>  >  0xc0435a8e : group_send_sig_info+0x43/0x58
>  >  0xc048d42a : send_sigio+0xe3/0x133
>  >  0xc048d4c9 : __kill_fasync+0x4f/0x52
>  >  0xc048dc78 : vfs_ioctl+0x0/0x6c
>  >  0xf8943ef5 : snd_timer_user_tinterrupt+0x11f/0x13c [snd_timer]
>  >  0xf8942c74 : snd_timer_interrupt+0x1de/0x23f [snd_timer]
>  >  0xf896667d : snd_pcm_period_elapsed+0xf0/0x134 [snd_pcm]
>  >  0xf8bfef49 : azx_interrupt+0x60/0xa4 [snd_hda_intel]
>  >  0xc0459eab : handle_IRQ_event+0x26/0x4d
>  >
>  >
>  > And that of the linux kernel (latest patch):
>  >
>  >  [<c042bad6>] warn_on_slowpath+0x46/0x56
>  >  [<c0415a33>] ? apic_wait_icr_idle+0x16/0x1d
>  >  [<c0415243>] ? __send_IPI_dest_field+0x50/0x54
>  >  [<c04020e5>] ? send_IPI_mask+0xd/0xf
>  >  [<c046773c>] ? get_pageblock_flags_group+0x50/0x6e
>  >  [<c046777e>] ? get_pageblock_migratetype+0x24/0x27
>  >  [<c0468472>] ? free_hot_page+0xf/0x11
(Continue reading)

fche at redhat dot com | 3 May 2008 12:47
Favicon

[Bug translator/6479] New: investigate possible adverse effects of RT branch rwlocks

http://blogs.sun.com/roland/entry/performance_tools_and_realtime_java (!)

--

-- 
           Summary: investigate possible adverse effects of RT branch
                    rwlocks
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com

http://sourceware.org/bugzilla/show_bug.cgi?id=6479

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Gmane