From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: Re: segfaults and sockets
Date: Mon, 05 Jul 2004 16:42:17 -0400 [thread overview]
Message-ID: <40E9BD29.5040708@blue-labs.org> (raw)
In-Reply-To: <20040705133230.7439d301.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
Thank you, I've forwarded/reported the bug.
David S. Miller wrote:
>On Mon, 05 Jul 2004 16:23:44 -0400
>David Ford <david+challenge-response@blue-labs.org> wrote:
>
>
>
>
>>ioctl(5, 0x8906, 0x7fbfffeff0) = 0
>>--- SIGSEGV (Segmentation fault) @ 0 (0) ---
>>+++ killed by SIGSEGV +++
>>
>>
>
>0x8906 is SIOCGSTAMP, aparently the app isn't using a large enough
>structure to capture the timestamp, and the kernel is thus overwriting
>some critical part of the stack causing it to crash.
>
>
[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]
begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard
prev parent reply other threads:[~2004-07-05 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 20:23 segfaults and sockets David Ford
2004-07-05 20:32 ` David S. Miller
2004-07-05 20:42 ` David Ford [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=40E9BD29.5040708@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--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