Bug 144266 - Konversation causes the Linux kernel+grsecurity to kill it
Summary: Konversation causes the Linux kernel+grsecurity to kill it
Status: RESOLVED NOT A BUG
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.0.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-15 20:56 UTC by James Theron Browning
Modified: 2011-09-26 18:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
The second logfile I've had that triggers it. (203.38 KB, application/octet-stream)
2007-04-15 21:01 UTC, James Theron Browning 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description James Theron Browning 2007-04-15 20:56:38 UTC 
Version:           1.0.1 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.4.6 (Gentoo Hardened 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10) stripped CFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
OS:                Linux

On a linux 2.6.17 w/ grsecurity and pax konversation will cause the linux kernel to kill it if a channel is joined with (some?) non-latin characters near the end of its' logfile.

generating the kernel log contents:
PAX: execution attempt in: <NULL>, 00000000-00000000 00000000
PAX: terminating task: /usr/bin/konversation(konversation):16821, uid/euid: 1000/1000, PC: 00000018, SP: bdc56920
PAX: bytes at PC: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
PAX: bytes at SP-4: 00000018 00000008 bdc569b0 0000003e 03d2a9c8 17c4ea08 17c4f350 bdc569e8 bdc569b0 bdc56980 17c4f350 bdc569
f8 bdc569fc 00000001 17c50940 bdc569e8 037c60d8 58137514 17c4f350 17c4e7b8 bdc569f8

when the logfile ends:
[Thu Apr 12 2007] [07:10:06]     * dazjorz has to go, bye!
[Thu Apr 12 2007] [07:13:58] <roeles>   cya
[Thu Apr 12 2007] [07:41:38]     * dazjorz is back
[Thu Apr 12 2007] [08:58:24] Quit       Md has left this server ("<D8><AD><D9><8E><D9><88><D9><91><D8><A7><D9><85><D8><AA>
<D9><8A> <D9><85><D9><8F><D9><85><D9><92><D8><AA><D9><90><D9><84><D8><A6><D8><A9> <D8><A8><D9><90><D8><A3><D9><8E><D9><86>
<D9><92><D9><82><D9><8E><D9><84><D9><8E><D9><8A><D9><92><D8><B3><D9><88><D9><86>").
Comment 1 James Theron Browning 2007-04-15 21:01:17 UTC 
Created attachment 20278 [details]
The second logfile I've had that triggers it.

Stick it in logs/freenode_#ipv6.log
The last line seems to be the trigger.
Comment 2 Peter Simonsson 2007-04-21 22:17:40 UTC 
Would it be possible to get a backtrace from gdb?
Comment 3 James Theron Browning 2007-04-22 21:17:36 UTC 
I don't think so, I will try though.
Comment 4 Nicolás Alvarez 2011-09-22 22:34:48 UTC 
4 years later, still waiting for that backtrace... :)
Comment 5 James Theron Browning 2011-09-26 18:53:31 UTC 
I never figure out how to get that backtrace. Since then I've stopped using a grsec/pax kernel, kde3 and konversation.