From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no
	version=3.4.4
Received: (qmail 11169 invoked from network); 26 May 2023 01:11:12 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 26 May 2023 01:11:12 -0000
Received: from ftrv.se ([45.76.35.157]) by 9front; Thu May 25 21:06:36 -0400 2023
Date: Fri, 26 May 2023 03:06:27 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftrv.se; s=mail;
	t=1685063188; bh=pH/EeFlAQUeSN95wbtbW4O4GtGMCHFIcWhhFKhLxFmw=;
	h=Date:From:To:Subject:In-Reply-To:References;
	b=WQks+wM9z0sgnEGtP7nKHfC/SOak+NLgXsMhyV5W58bbclNSP4IOB5mAyWfRqwgmu
	 jBDwxv/td0VTnU1RF+qFjFl2w5FwWheshHKrCdhNKY2qTqON+s4SQT8qmw4tufRSo2
	 mP82jE7bfZK43pL9xVzUMpQhRm4DU2gnQSlM+raA=
From: =?ISO-8859-1?Q?Sigrid_Solveig_Hafl=EDnud=F3ttir?= <sigrid@ftrv.se>
To: 9front@9front.org
In-Reply-To: <38F6DFD3A4EFABEDC15102B0F9A53A0A@gaff.inri.net>
References: <38F6DFD3A4EFABEDC15102B0F9A53A0A@gaff.inri.net>
Message-ID: <5EE27AD5-BC82-4641-9D59-D94A4AAB9494@ftrv.se>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: webscale injection YAML map/reduce-scale just-in-time layer 
Subject: Re: [9front] latest code crashes thinkpad x1 yoga 3rd gen on fshalt
Reply-To: 9front@9front.org
Precedence: bulk

It's because I added nvme shutdown via fshalt, and apparently shutting down=
 *ram* disks uncovered this bug=2E Because sdram seems to be only present o=
n pc and pc64 (read: none that I have here) I haven't noticed it before pus=
hing my change=2E I think you can just replace xalloc back with malloc in s=
dram=2Ec=2E
Sorry=2E

On May 26, 2023 2:50:16 AM GMT+02:00, sl@stanleylieber=2Ecom wrote:
>> the bug is in sdram=2Ec, it uses xalloc for sddev allocation, but
>> devsd=2Ec calls free on it=2E should be an easy fix I guess=2E
>
>i wonder why this never triggered until just now=2E  i've been running
>9front on this machine all year=2E
>
>sl