From: Andi Kleen <ak@muc.de>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64 bad frame in signal deliver
Date: Mon, 19 Apr 2004 17:36:28 +0200 [thread overview]
Message-ID: <m3ad18m137.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1MHWN-3ga-31@gated-at.bofh.it> (Jan Kasprzak's message of "Mon, 19 Apr 2004 16:30:17 +0200")
Jan Kasprzak <kas@informatics.muni.cz> writes:
>
> 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?
Yes, we know every message that isn't output by i386 is a kernel bug.
proftpd segfaulted.
-Andi
next parent reply other threads:[~2004-04-19 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1MHWN-3ga-31@gated-at.bofh.it>
2004-04-19 15:36 ` Andi Kleen [this message]
2004-04-19 14:15 x86_64 bad frame in signal deliver Jan Kasprzak
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=m3ad18m137.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=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