mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kasprzak <kas@informatics.muni.cz>
To: linux-kernel@vger.kernel.org
Subject: x86_64 bad frame in signal deliver
Date: Mon, 19 Apr 2004 16:15:36 +0200	[thread overview]
Message-ID: <20040419141536.GU23938@fi.muni.cz> (raw)

	Hello, all!

I have got the following messages on my FTP server running x86_64:

proftpd[16913]: segfault at 0000007fbf7ff170 rip 000000000041ecaa rsp 0000007fbf7ff160 error 6
proftpd[16913] bad frame in signal deliver frame:0000007fbf7fef18 rip:41ecaa rsp:7fbf7ff160 orax:ffffffffffffffff
proftpd[17332]: segfault at 0000007fbf7ff170 rip 000000000041ecaa rsp 0000007fbf7ff160 error 6
proftpd[17332] bad frame in signal deliver frame:0000007fbf7fef18 rip:41ecaa rsp:7fbf7ff160 orax:ffffffffffffffff
proftpd[17803]: segfault at 0000007fbf7ff170 rip 000000000041ecaa rsp 0000007fbf7ff160 error 6
proftpd[17803] bad frame in signal deliver frame:0000007fbf7fef18 rip:41ecaa rsp:7fbf7ff160 orax:ffffffffffffffff
proftpd[18200]: segfault at 0000007fbf7ff170 rip 000000000041ecaa rsp 0000007fbf7ff160 error 6
proftpd[18200] bad frame in signal deliver frame:0000007fbf7fef18 rip:41ecaa rsp:7fbf7ff160 orax:ffffffffffffffff

	Does that mean that proftpd segfaulted inside user space (and is thus
buggy or even insecure) - as address rip:41ecaa suggests, or is it some kind
of kernel bug?

	The /proc/<pid of proftpd>/maps on my system suggests that
0x41ecaa is a valid code address:

/proc/9878/maps:00400000-00460000 r-xp 00000000 09:00 765659          /usr/sbin/proftpd
/proc/9878/maps:0055f000-00568000 rw-p 0005f000 09:00 765659          /usr/sbin/proftpd
/proc/9878/maps:00667000-00668000 rw-p 00067000 09:00 765659          /usr/sbin/proftpd

	Kernel is 2.6.5 on Fedora Core 1/x86_64.

	Thanks,

-Yenya

-- 
| Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/   Czech Linux Homepage: http://www.linux.cz/ |
 Any compiler or language that likes to hide things like memory allocations
 behind your back just isn't a good choice for a kernel.   --Linus Torvalds

             reply	other threads:[~2004-04-19 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 14:15 Jan Kasprzak [this message]
     [not found] <1MHWN-3ga-31@gated-at.bofh.it>
2004-04-19 15:36 ` Andi Kleen

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=20040419141536.GU23938@fi.muni.cz \
    --to=kas@informatics.muni.cz \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®