Re: kern/53280: amd64 panics since recent compat/netbsd32 commits

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR kern/53280; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
	gson%gson.org@localhost (Andreas Gustafsson)
Cc: 
Subject: Re: kern/53280: amd64 panics since recent compat/netbsd32 commits
Date: Sat, 12 May 2018 18:11:53 -0400

 On May 12,  8:10pm, gson%gson.org@localhost (Andreas Gustafsson) wrote:
 -- Subject: Re: kern/53280: amd64 panics since recent compat/netbsd32 commits
 
 |  I have no idea, and I don't think finding out should be my
 |  responsibility.
 
 I just want to know at least if this is a 32 bit binary causing this...
 |
 |  > I added the code because nsd needs send and recv mmsg which were
 |  > missing. So removing the code breaks nsd which is not a test...
 |  
 |  Fixing nsd does not justify making the system panic.
 
 Yes.
 
 |  > In addition, I have more
 |  > tests that I have not committed because the code is broken in
 |  > different ways (the code before I committed my stuff). I can revert
 |  > the new changes and commit the new tests and then you can have
 |  > different broken tests :-) This is what tests are all about anyway:
 |  > to detect broken code...
 |  
 |  Yes, that is how it should work.  A few broken tests is vastly better
 |  than having no test results at all because the system paniced before
 |  the test run completed.
 
 I agree, but I could fix it as quickly as reverting if I understood
 what breaks it...
 
 christos