mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shawn Starr" <shawn.starr@rogers.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.x strangeness with large buffer usage via network transfer/disk and SEGV processes
Date: Sat, 27 Mar 2004 18:07:38 -0500	[thread overview]
Message-ID: <000001c41450$4c6c1f30$030aa8c0@PANIC> (raw)

I don't get something maybe someone can explain why this is happening:

1) When using a large amount of buffers via sending say a 800MB file from
one PC to another, the Linux system will segfault processes but not preform
an OOM. Even though the system itself has not touched swap memory. Why is
the kernel killing/or why are the processes dying with Segfault?

I see this happening when I extract a Linux source tarball and have certain
processes running, while tar extracts the process will just receive a
segmentation fault w/o core.

When using a virtual OS emulator, the emulator will just die.

I don't remember this behaviour in 2.4 at all and I don't think this is
correct. I have PREEMPT enabled as well.

Is this a problem or is this correct behavour?

Thanks

Shawn S.


             reply	other threads:[~2004-03-27 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-27 23:07 Shawn Starr [this message]
2004-03-28  2:58 ` Eric

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='000001c41450$4c6c1f30$030aa8c0@PANIC' \
    --to=shawn.starr@rogers.com \
    --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®