Delivery-Date: Sun, 24 Jan 2016 02:09:13 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id D49AD1E02F9;
	Sun, 24 Jan 2016 02:09:10 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DF0E236452;
	Sun, 24 Jan 2016 07:09:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 41CDF361AB
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 07:09:02 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id a_DNHzwJegtY for <tor-talk@lists.torproject.org>;
 Sun, 24 Jan 2016 07:09:02 +0000 (UTC)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com
 [IPv6:2607:f8b0:4001:c05::22f])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2242D35371
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 07:09:02 +0000 (UTC)
Received: by mail-ig0-x22f.google.com with SMTP id h5so14397225igh.0
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 23:09:02 -0800 (PST)
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==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:from:date
 :message-id:subject:to:content-type;
 bh=RL+k47jQY80NdX9sr8iYsV3DM1MSDmjYKfhBQx5nXmU=;
 b=L2iviQjpVoVV95fPI6hkP9gvYrTvhmMH3Bjs8iD8SkWM7VqAps2oLjjA959cQv+Y1d
 1FErHsrCt9CGAiQAi/HOIv/4bH7ZQqEs99VLOytQbc4LYmm2PH7D8J4/GOK617firTKJ
 dznB5H6Rljgo9Vl5/SPuWecq9FEkESyYlz9Qm0hRAfLZp1VOLnH5UFVqePktsRM+KAuk
 HfQENQs2mPrkmGKYWcKgws+DdJDLCINM0wxr2pu+p90M6qD/4mCDKO+CYjzLgp64lgnI
 OBcBj4teGOdiPt6h3SOthUHbiNIUKO/13WXMQ3AUI/zZ7Vaw78RXMsQ3ptp1JlsN6D+s
 yfNA==
X-Gm-Message-State: AG10YOTbpWwMwCqYr+uHAr+iElt9DIwiLGGT6uP+LTb3xrVn77Us8MMbSQda2k+we4mEZroNzgnsy52Vnuqdmw==
X-Received: by 10.50.126.8 with SMTP id mu8mr11080555igb.52.1453619339892;
 Sat, 23 Jan 2016 23:08:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.36.137.197 with HTTP; Sat, 23 Jan 2016 23:08:20 -0800 (PST)
In-Reply-To: <40E8EAC4-1F93-4CA7-BF40-8F2BA2A1CAB5@frii.com>
References: <20160116212250.GA14827@ix-293.local> <n7p00n$ia8$1@ger.gmane.org>
 <20160123191442.GA2981@ix.home>
 <975f6dce11caa36e05b79e0b6172bacf@blackmesa.at>
 <CAD2Ti2-iaD0yct=2215rsG7QEP7WQSpoQcw3hQYoDLn-C8FjpQ@mail.gmail.com>
 <40E8EAC4-1F93-4CA7-BF40-8F2BA2A1CAB5@frii.com>
From: grarpamp <grarpamp@gmail.com>
Date: Sun, 24 Jan 2016 02:08:20 -0500
Message-ID: <CAD2Ti2-gfnYOuwO_k8gTptbdutqufcfuf3LWUHpMmPeaLkm=ww@mail.gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Sat, Jan 23, 2016 at 7:17 PM, Ken Cline <cline@frii.com> 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@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

