mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gheskett@wdtv.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>,
	boinc_dev@ssl.berkeley.edu
Subject: Re: shouldn't a non-privileged malformed sprintf crashes the kernel
Date: Sun, 17 Feb 2013 10:23:08 -0500	[thread overview]
Message-ID: <201302171023.08803.gheskett@wdtv.com> (raw)
In-Reply-To: <5120B408.8030806@gmx.de>

On Sunday 17 February 2013, Toralf Förster wrote:
>This is the 2nd time in a row that a stable kernel (3.7.8 currently)
>crashes in such a way that even the sys-rq key doesn't work any longer.
>Found nothing in the log. The screen shot is here [1]. First time this
>issue was reported in [2].
>
>The bug seems to be triggered by the BOINC client - I'm running the alpha
>version of it [3].
>
>I'm wondering whether the sprintf issue discussed in [4] is the trigger
>for the bug (I attached that message here b/c the BOINC devs doesn't
>allow just even read access to the mail archive w/o registering).
>
>
>@boinc_devs
>IMO it would be helpful to store the pid of the BOINC clients to
>stdoutdae.txt too, or where can I find it ?
>
>
>
>[1] http://ompldr.org/vaGh0MQ
>[2] http://thread.gmane.org/gmane.linux.kernel/1438965
>[3] https://boinc.berkeley.edu/dev/forum_thread.php?id=6698#46649
>[4]
>http://lists.ssl.berkeley.edu/mailman/private/boinc_dev/2013-February/01
>9545.html

You are asking for help from the BOINC folks, on a linux list?  Rotsa ruck.
I was in the top 5000 when it was SETI@home, but they let some windows 
folks in & the next thing I knew SETI was shut down unless you ran it via 
the BOINC manager.  But the BOINC thing never learned about nice, and just 
took over the machine so badly I couldn't even type an email.  I worked for 
several days on a wrapper that did use nice, but their next packet 
transition always managed to defeat it.  When I complained, I was told to 
use windows!  Since it was my machine, not theirs, I nuked it off the 
system.

IMO, if they want to use my spare cpu cycles, then they can make an effort 
to get along with linux.  Telling me, when I complained, to use windows, 
was the last straw.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
My views 
<http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml>
God is love, but get it in writing.
		-- Gypsy Rose Lee
I was taught to respect my elders, but its getting 
harder and harder to find any...

      parent reply	other threads:[~2013-02-17 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 10:42 Toralf Förster
2013-02-17 11:58 ` richard -rw- weinberger
2013-02-17 15:23 ` Gene Heskett [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=201302171023.08803.gheskett@wdtv.com \
    --to=gheskett@wdtv.com \
    --cc=boinc_dev@ssl.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    /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®