[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-talk] Kernel OOPS through Tor - report or ignore?

To: tor-talk@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
From: grarpamp <grarpamp@xxxxxxxxx>
Date: Sun, 24 Jan 2016 02:08:20 -0500
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sun, 24 Jan 2016 02:09:13 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=RL+k47jQY80NdX9sr8iYsV3DM1MSDmjYKfhBQx5nXmU=; b=tNtfrl7S19nhhX6Bt0pUEGHkRSm+oaMKGwDmu6puCmua57o2E7hfgUp8WNPiiyVrh2 Io7E2LyaeG9OsDx2JSOqeIuFo8a6Behk+A6YWF6kPSWDpsk6mE2ptfq4QRFlGZLkh182 2Xeg7vWf6CckGzPNMMXgHnR+e312XoUBjAHS1Ssq7hfxwG7NMUqPILb+bscfprampWC9 uCy0XExXoN8F94sDfr6JzfE/bI4Kkn+Lnv7RL4FBSpqoZhwz+DIy/xyqvaycw353PUdR SeA5cmaH5zW05WU9GFv1V7n80g70jbVBsaPWixslCFo9w4Ll9hW8LExECpy5nCwu2thH 1ndQ==
In-reply-to: <40E8EAC4-1F93-4CA7-BF40-8F2BA2A1CAB5@xxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-id: "all discussion about theory, design, and development of Onion Routing" <tor-talk.lists.torproject.org>
List-post: <mailto:tor-talk@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
References: <20160116212250.GA14827@xxxxxxxxxxxx> <n7p00n$ia8$1@xxxxxxxxxxxxx> <20160123191442.GA2981@xxxxxxx> <975f6dce11caa36e05b79e0b6172bacf@xxxxxxxxxxxx> <CAD2Ti2-iaD0yct=2215rsG7QEP7WQSpoQcw3hQYoDLn-C8FjpQ@xxxxxxxxxxxxxx> <40E8EAC4-1F93-4CA7-BF40-8F2BA2A1CAB5@xxxxxxxx>
Reply-to: tor-talk@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-talk" <tor-talk-bounces@xxxxxxxxxxxxxxxxxxxx>

On Sat, Jan 23, 2016 at 7:17 PM, Ken Cline <cline@xxxxxxxx> wrote:
> I reported a Tor crash, only to find it was caused by a failing disk.

Apps should not crash due to failed i/o, rather should retry, block,
fail, or exit, perhaps configurably. Especially if kern errno.h posted.

> Creo, It sounds like you have a crash recovery utility running.

Maybe dropped to a debug console.

> If so, save the crash dump and reboot.  You can send the dump in or wait to see if it happens a second time.

True.
-- 
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Follow-Ups:
- Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
  - From: Ken Cline

References:
- [tor-talk] trusting .onion services
  - From: Rejo Zenger
- Re: [tor-talk] trusting .onion services
  - From: Oskar Wendel
- Re: [tor-talk] trusting .onion services
  - From: Rejo Zenger
- [tor-talk] Kernel OOPS through Tor - report or ignore?
  - From: creo
- Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
  - From: grarpamp
- Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
  - From: Ken Cline

Prev by Author: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
Next by Author: [tor-talk] Network Analysis of Overlay Networks, Capabilities, Fill Traffic [was: VPN less safe?]
Previous by thread: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
Next by thread: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
Index(es):
- Author
- Thread