NetBSD Problem Report #58724

From www@netbsd.org  Mon Oct  7 00:35:02 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 00CC91A923B
	for <gnats-bugs@gnats.NetBSD.org>; Mon,  7 Oct 2024 00:35:02 +0000 (UTC)
Message-Id: <20241007003500.EC36B1A923D@mollari.NetBSD.org>
Date: Mon,  7 Oct 2024 00:35:00 +0000 (UTC)
From: John.P.Darrow@gmail.com
Reply-To: John.P.Darrow@gmail.com
To: gnats-bugs@NetBSD.org
Subject: Pull up FFS signed/unsigned fixes from chs
X-Send-Pr-Version: www-1.0

>Number:         58724
>Category:       kern
>Synopsis:       Pull up FFS signed/unsigned fixes from chs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    riastradh
>State:          needs-pullups
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 07 00:40:00 +0000 2024
>Closed-Date:    
>Last-Modified:  Sat Dec 07 19:17:05 +0000 2024
>Originator:     John Darrow
>Release:        NetBSD 10.0
>Organization:
buried here somewhere
>Environment:
>Description:
Shortly after -10 was branched, chs applied a couple of fix sets (ported from mckusick@FreeBSD) to HEAD for signed/unsigned issues in ffs code, as documented in the following two source-changes messages:

http://mail-index.netbsd.org/source-changes/2023/01/07/msg142678.html

http://mail-index.netbsd.org/source-changes/2023/01/08/msg142682.html

These fixes appear, by inspection, as if they ought to also get pulled up at least to -10, but it does not appear that any pullup request was sent.

(It's possible they might also be appropriate for -9, but I don't know if any of them are also dependent on other changes that happened between -9 and -10, particularly the addition of UFS2ea support.)

noted on icb, Riastradh@ requested I file a PR to track this.
>How-To-Repeat:
See fixes while paging through old source-changes messages, note lack of having seen any matching pullups to -10, confirm said lack by checking a selected few of the involved files via cvsweb.
>Fix:
pull up the changes found in the two messages to -10, hopefully before 10.1 is tagged.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->chs
Responsible-Changed-By: riastradh@NetBSD.org
Responsible-Changed-When: Fri, 11 Oct 2024 22:01:02 +0000
Responsible-Changed-Why:
Can I trouble you to take a look at this?


State-Changed-From-To: open->needs-pullups
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Fri, 11 Oct 2024 22:01:02 +0000
State-Changed-Why:
probably needs pullup-10, maybe needs pullup-9


From: Chuck Silvers <chuq@chuq.com>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, netbsd-bugs@netbsd.org,
	gnats-admin@netbsd.org, riastradh@NetBSD.org,
	John.P.Darrow@gmail.com
Subject: Re: kern/58724 (Pull up FFS signed/unsigned fixes from chs)
Date: Sat, 7 Dec 2024 11:10:33 -0800

 these fixes were pulled up to netbsd-10 later last year:

 https://releng.netbsd.org/cgi-bin/req-10.cgi?show=160
 https://releng.netbsd.org/cgi-bin/req-10.cgi?show=161

 I did not apply them to netbsd-9, could someone else work on that if it is desired?

 -Chuck

Responsible-Changed-From-To: chs->riastradh
Responsible-Changed-By: chs@NetBSD.org
Responsible-Changed-When: Sat, 07 Dec 2024 19:17:05 +0000
Responsible-Changed-Why:
could you adapt these for netbsd-9?


>Unformatted:

Home	PR Database Search