gmane.os.netbsd.bugs

Re: bin/47776: dhcpcd(8) requries hostname(1)

Izumi Tsutsui — 2013-05-24T22:30:01

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

From: Izumi Tsutsui <tsutsui< at >ceres.dti.ne.jp>
To: gnats-bugs< at >NetBSD.org
Cc: roy< at >marples.name, tsutsui< at >ceres.dti.ne.jp
Subject: Re: bin/47776: dhcpcd(8) requries hostname(1)
Date: Sat, 25 May 2013 07:25:46 +0900

 >  What's the expectation here for a system deliberately missing 
 >  hostname(1)?
 >  To try and set the hostname as requested or to avoid errors that 
 >  hostname(1) is missing?
 
 The latter.  A "not found" message during installation is not good,
 especially if users have some network trouble in their environments.
 
 >  If the former, is any other mechanism available like sysctl to set the 
 >  hostname?
 
 "sysctl -w kern.hostname=FOO" works at least on NetBSD.
 
 >  If the latter, then either remove the hook from the ramdisk as well or 
 >  add a line to dhcpcd.conf(5) to skip running it.
 
 I'm afread it's a bit annoying to maintain different versions for sysinst,
 but if they will properly be maintained on every dhc

kern/47851: kernel panic: callout_softclock(v=0x0) -> nfs_timer(arg=0x0)

2013-05-24T13:40:00

System: NetBSD cheusov.imb.invention.com 6.0.1_PATCH NetBSD 6.0.1_PATCH (GENERIC) #4: Wed Mar 13 17:27:04 FET 2013 cheusov< at >cheusov.imb.invention.com:/srv/obj/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
Stacktrace is below. This crash happened immediately after

   /etc/rc.d/mountd onestart; /etc/rc.d/nfsd onestart

and attempt to nfsmount one exported directory from Linux.

#3  0xc0788def in panic (fmt=0xc0ba72f2 "trap") at /srv/src_netbsd6/sys/kern/subr_prf.c:205
#4  0xc07cee5b in trap (frame=0xdc319be8) at /srv/src_netbsd6/sys/arch/i386/i386/trap.c:396
#5  0xc010cfb8 in ?? ()
#6  0xc0613538 in nfs_timer (arg=0x0) at /srv/src_netbsd6/sys/nfs/nfs_socket.c:846
#7  0xc055ecf8 in callout_softclock (v=0x0) at /srv/src_netbsd6/sys/kern/kern_timeout.c:734
#8  0xc05544af in softint_execute (s=<optimized out>, si=<optimized out>, l=<optimized out>) at /srv/src_netbsd6/sys/kern/kern_softint.c:543
#9  softint_dispatch (pinned=0xc9b6d540, s=2) at /srv/src_netbsd6/sys/kern/kern_softint.c:825


Un

Re: kern/47748: Invalid file on ffs

David Holland — 2013-05-24T08:20:00

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

From: David Holland <dholland-bugs< at >netbsd.org>
To: gnats-bugs< at >NetBSD.org
Cc: kern-bug-people< at >netbsd.org, gnats-admin< at >netbsd.org,
netbsd-bugs< at >netbsd.org, frederic< at >fauberteau.org
Subject: Re: kern/47748: Invalid file on ffs
Date: Fri, 24 May 2013 08:15:30 +0000

 On Sun, Apr 21, 2013 at 11:45:05PM +0000, John Nemeth wrote:
  >  }  It looks to me like it was probably four (or maybe more) characters
  >  }  long with a zero byte as the fourth character. There is no way to name
  >  
  >       Except that it should be impossible to create such a file no
  >  matter what an application does.  If a zero byte were to ever appear in
  >  a filename it would represent a serious bug in the filesystem code or
  >  memory corruption.
 
 You'd think so, yes. On the other hand, clearly the file was created
 from an uninitialized string or the name wouldn't have begun with
 K+\x6.
 
 Another possibility is that the next byte of the filename was one

Re: kern/47748: Invalid file on ffs

David Holland — 2013-05-24T08:15:30

 >  }  It looks to me like it was probably four (or maybe more) characters
 >  }  long with a zero byte as the fourth character. There is no way to name
 >  
 >       Except that it should be impossible to create such a file no
 >  matter what an application does.  If a zero byte were to ever appear in
 >  a filename it would represent a serious bug in the filesystem code or
 >  memory corruption.

You'd think so, yes. On the other hand, clearly the file was created
from an uninitialized string or the name wouldn't have begun with
K+\x6.

Another possibility is that the next byte of the filename was one of
the magic values > 0x80 that sh's parser uses for internal signalling.
That would likely make it impossible to address the file from the
shell, with or without autocompletion. (If the shell was sh, anyway.)
I could also imagine 0xff confusing some shells, particularly csh.

But if the filename merely contained a control character, fsck
wouldn't have removed it. Or so I'd think anyway. All I see in
fsck_ffs

Re: bin/47840: awk string comparison of integer constant

David Holland — 2013-05-24T07:55:00

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

From: David Holland <dholland-bugs< at >netbsd.org>
To: gnats-bugs< at >NetBSD.org
Cc: 
Subject: Re: bin/47840: awk string comparison of integer constant
Date: Fri, 24 May 2013 07:51:55 +0000

 On Mon, May 20, 2013 at 11:05:03PM +0000, Valery Ushakov wrote:
  >  > Note that k < 10 is evaluated as a string comparison.
  >  > 
  >  > Is this required by some standard? gawk does the same thing, but it
  >  > definitely violates the POLA.
  >  
  >  Hmm, it does, indeed, but [...]

 Blah... all right then, can we at least warn if a numeric constant
 gets converted to a string value like this? It is reasonable to
 suppose that if I (or anyone else) intended a string value I would
 have written a string constant.

 The behavior I've just exhibited is just as nonsensical as that cited
 in that RATIONALE.

 -- 
 David A. Holland
 dholland< at >netbsd.org

Re: bin/47776: dhcpcd(8) requries hostname(1)

Roy Marples — 2013-05-24T07:45:00

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

From: Roy Marples <roy< at >marples.name>
To: <gnats-bugs< at >NetBSD.org>
Cc: 
Subject: Re: bin/47776: dhcpcd(8) requries hostname(1)
Date: Fri, 24 May 2013 08:42:31 +0100

 What's the expectation here for a system deliberately missing 
 hostname(1)?
 To try and set the hostname as requested or to avoid errors that 
 hostname(1) is missing?

 If the former, is any other mechanism available like sysctl to set the 
 hostname?
 If the latter, then either remove the hook from the ramdisk as well or 
 add a line to dhcpcd.conf(5) to skip running it.

 Thanks

 Roy

kern/47850: ipfstat is broken.

2013-05-23T21:35:00

Entropy Unlimited, Ltd.
NetBSD quasar.astron.com 6.99.20 NetBSD 6.99.20 (QUASAR) #3: Thu May 23 09:30:24 EDT 2013  christos< at >quasar.astron.com:/usr/src/sys/arch/amd64/compile/QUASAR amd64
Architecture: x86_64
Machine: amd64
ipf loads the rules properly but ipfstat does not list them.

0 root:wheel< at >t61//etc/ipf.d#  ipf -vf /tmp/ipf.conf 
block in log quick on iwn0(!) all head 600
block in quick inet from any to 10.0.0.0/25 port = 137 group 600
block in quick inet from 0.0.0.0/32 port = 68 to 255.255.255.255/32 port = 67 group
 600
block in log quick inet from 10.0.0.0/8 to any group 600
block in log quick inet from 192.168.0.0/16 to any group 600
block in log quick inet from 172.16.0.0/12 to any group 600
block in log quick inet from 127.0.0.0/8 to any group 600
block in log quick inet from 0.0.0.0/8 to any group 600
block in log quick inet from 169.254.0.0/16 to any group 600
block in log quick inet from 192.0.2.0/24 to any group 600
block in log quick inet from x.y.64.0/23 to any group 600
block in log qui

Re: install/47845 (fail to install xulrunner-19.0.2nb1.tgz netbsd 6.1 amd64 wrong checksum)

2013-05-23T21:19:51

Synopsis: fail to install xulrunner-19.0.2nb1.tgz netbsd 6.1 amd64 wrong checksum

State-Changed-From-To: open->analyzed
State-Changed-By: bouyer< at >NetBSD.org
State-Changed-When: Thu, 23 May 2013 21:19:51 +0000
State-Changed-Why:
The corruption occurs on the server side; the precise reason and fix is being
investigated.

PR/47849 CVS commit: src/sys/netinet6

SAITOH Masanobu — 2013-05-23T16:50:00

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

From: "SAITOH Masanobu" <msaitoh< at >netbsd.org>
To: gnats-bugs< at >gnats.NetBSD.org
Cc: 
Subject: PR/47849 CVS commit: src/sys/netinet6
Date: Thu, 23 May 2013 16:49:46 +0000

 Module Name:src
 Committed By:msaitoh
 Date:Thu May 23 16:49:46 UTC 2013

 Modified Files:
 src/sys/netinet6: ip6_flow.c

 Log Message:
 Clear mbuf's csum_flags in ip6flow_fastforward(). Fixes PR#47849.

 To generate a diff of this commit:
 cvs rdiff -u -r1.20 -r1.21 src/sys/netinet6/ip6_flow.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

Re: kern/47849 (ip6flow_fastforward() desn't clear csum_flags)

2013-05-23T16:46:30

Synopsis: ip6flow_fastforward() desn't clear csum_flags

Responsible-Changed-From-To: kern-bug-people->msaitoh
Responsible-Changed-By: msaitoh< at >NetBSD.org
Responsible-Changed-When: Thu, 23 May 2013 16:46:30 +0000
Responsible-Changed-Why:
mine.

kern/47849: ip6flow_fastforward() desn't clear csum_flags

2013-05-23T16:45:00

Architecture: all
Machine: all
ip6flow_fastforward() doesn't clear csum_flags in a mbuf.
ipflow_fastforward() does it. If an outgoing interface doesn't
support hwcsum, the checksum will be corrupted. If an outgoing
interface supprot hwcsum and not enabled, packet may be corrupt.

                               wm1       wm0
                                         with UDP6CSUM_Rx
[machineA]--------------[machineB]-----------------[machineC]
                      NetBSD-current

        wm0: UDP6CSUM_Rx is set
wm1: enabled = 0

On machineC: tracetoute6 machineA

        > 1  machineB  2.023 ms  1.991 ms  1.598 ms
        > 2  machineA  2.052 ms *  1.551 ms   (<=== 2nd try failed)

tcpdump's output on machineA:

% tcpdump -vvX -s0 -i lan0 host 2001:240:694:1:230:48ff:fed8:c268
tcpdump: listening on lan0, link-type EN10MB (Ethernet), capture size 65535 bytes
01:32:58.306827 2001:240:694:1:230:48ff:fed8:c268.65494 > 2001:240:694::1.33438: [udp sum ok] UDP, length: 12 [hlim 1] (len 20)
        0x0000:

PR/47846 CVS commit: src/sys/dev/raidframe

Christos Zoulas — 2013-05-23T14:20:01

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

From: "Christos Zoulas" <christos< at >netbsd.org>
To: gnats-bugs< at >gnats.NetBSD.org
Cc: 
Subject: PR/47846 CVS commit: src/sys/dev/raidframe
Date: Thu, 23 May 2013 10:15:52 -0400

 Module Name:src
 Committed By:christos
 Date:Thu May 23 14:15:52 UTC 2013

 Modified Files:
 src/sys/dev/raidframe: rf_netbsdkintf.c

 Log Message:
 PR/47846: Frank Kardel: panic/lockups in raidframe during detach at shutdown
 XXX: Fix this properly by using the memory allocated from the autoconf
 subsystem and use raidput in all the places needed.

 To generate a diff of this commit:
 cvs rdiff -u -r1.302 -r1.303 src/sys/dev/raidframe/rf_netbsdkintf.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

Re: port-sparc64/46719 (mrtg fails to build with a compiler error on sparc64)

Martin Husemann — 2013-05-23T07:05:01

The following reply was made to PR port-sparc64/46719; it has been noted by GNATS.

From: Martin Husemann <martin< at >duskware.de>
To: gnats-bugs< at >NetBSD.org
Cc: 
Subject: Re: port-sparc64/46719 (mrtg fails to build with a compiler error on sparc64)
Date: Thu, 23 May 2013 09:00:26 +0200

 For the record: this seems to be gcc bugzilla ticket #48830, fixed in
 upstream trunk, backport mostly impossible.

 Martin

Re: kern/47512 (netbsd-6 system crash)

2013-05-23T00:24:40

Synopsis: netbsd-6 system crash

State-Changed-From-To: open->closed
State-Changed-By: htodd< at >NetBSD.org
State-Changed-When: Thu, 23 May 2013 00:24:39 +0000
State-Changed-Why:
No more crashes before the reporter upgraded to NetBSD 6.1.

Re: port-sparc64/46719 (mrtg fails to build with a compiler error on sparc64)

2013-05-22T21:54:40

Synopsis: mrtg fails to build with a compiler error on sparc64

State-Changed-From-To: suspended->closed
State-Changed-By: htodd< at >NetBSD.org
State-Changed-When: Wed, 22 May 2013 21:54:40 +0000
State-Changed-Why:
Submitter no longer running NetBSD 6.0_BETA2 sparc64.

Re: lib/47804 (some processes don't exit and spin at 100% CPU)

2013-05-22T21:52:25

Synopsis: some processes don't exit and spin at 100% CPU

State-Changed-From-To: open->closed
State-Changed-By: htodd< at >NetBSD.org
State-Changed-When: Wed, 22 May 2013 21:52:25 +0000
State-Changed-Why:
Fixed by christos.

Re: kern/47780: if_vioif doesn't work with QEMU >= 1.4.0 due to features negotiation issues

Aurelien Jarno — 2013-05-22T06:10:01

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

From: Aurelien Jarno <aurelien< at >aurel32.net>
To: gnats-bugs< at >NetBSD.org
Cc: kern-bug-people< at >netbsd.org, gnats-admin< at >netbsd.org,
netbsd-bugs< at >netbsd.org
Subject: Re: kern/47780: if_vioif doesn't work with QEMU >= 1.4.0 due to
 features negotiation issues
Date: Wed, 22 May 2013 08:05:06 +0200

 On Mon, May 13, 2013 at 03:30:12AM +0000, MINOURA Makoto wrote:
 > The following reply was made to PR kern/47780; it has been noted by GNATS.
 > 
 > From: makoto< at >hauN.ORG (MINOURA Makoto)
 > To: gnats-bugs< at >NetBSD.org
 > Cc: kern-bug-people< at >netbsd.org, gnats-admin< at >netbsd.org, netbsd-bugs< at >netbsd.org
 > Subject: Re: kern/47780: if_vioif doesn't work with QEMU >= 1.4.0 due to features negotiation issues
 > Date: Mon, 13 May 2013 12:25:24 +0900
 > 
 >  if_vioif.c rev 1.4/1.2.14.1/1.2.8.1 should fix this problem.
 >  Thanks.
 >  
 
 Thanks a lot for the patch, I confirm it fixes the issue.
 
 -- 
 Aurelien Jarno                          GPG: 1024D/F1BCD

Re: kern/47780: if_vioif doesn't work with QEMU >= 1.4.0 due to features negotiation issues

Aurelien Jarno — 2013-05-22T06:05:06

Thanks a lot for the patch, I confirm it fixes the issue.

kern/47846: panic/lockups in raidframe during detach at shutdown

2013-05-21T21:05:00

System: NetBSD pip.kardel.name 6.99.19 NetBSD 6.99.19 (PIPGEN) #28: Tue May 21 22:10:18 CEST 2013 kardel< at >pip.kardel.name:/usr/src/sys/arch/amd64/compile/PIPGEN amd64
Architecture: x86_64
Machine: amd64
raidframe panics or locks up at shutdown time.
Problem was introduced with the commit of dynamic allocation of
raidX devices.

Module Name:src
Committed By:christos
Date:Sat Apr 27 21:18:43 UTC 2013

Modified Files:
src/sys/dev/raidframe: rf_engine.c rf_netbsd.h rf_netbsdkintf.c
    rf_raid.h

Log Message:
allocate devices dynamically.


To generate a diff of this commit:
cvs rdiff -u -r1.47 -r1.48 src/sys/dev/raidframe/rf_engine.c
cvs rdiff -u -r1.29 -r1.30 src/sys/dev/raidframe/rf_netbsd.h
cvs rdiff -u -r1.299 -r1.300 src/sys/dev/raidframe/rf_netbsdkintf.c
cvs rdiff -u -r1.43 -r1.44 src/sys/dev/raidframe/rf_raid.h

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Issue is caused by:
- softc structure are dynamically, independently a

Re: port-amd64/29153 (Faults in bpf_filter.c:m_xhalf in wm(4) RX path)

2013-05-21T20:08:56

Synopsis: Faults in bpf_filter.c:m_xhalf in wm(4) RX path

State-Changed-From-To: feedback->closed
State-Changed-By: jnemeth< at >NetBSD.org
State-Changed-When: Tue, 21 May 2013 20:08:55 +0000
State-Changed-Why:
Feedback timeout, and submitter says the bug has most likely been fixed
sometime in the past decade.  Thanks for the PR!

Re: bin/47840: awk string comparison of integer constant

Aleksey Cheusov — 2013-05-21T18:30:01

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

From: Aleksey Cheusov <cheusov< at >tut.by>
To: gnats-bugs< at >netbsd.org
Cc: 
Subject: Re: bin/47840: awk string comparison of integer constant
Date: Tue, 21 May 2013 17:31:17 +0300

 --089e01493e2e59a94c04dd3b4d8f
 Content-Type: text/plain; charset=ISO-8859-1

 >
 >
 >    A string value shall be considered a NUMERIC STRING if it comes from
 >    one of the following:
 >

 Thanks! I overlooked "numeric string" definition.

 --089e01493e2e59a94c04dd3b4d8f
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable

 <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
 ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
 cc solid;padding-left:1ex">
 <br>
 =A0 =A0A string value shall be considered a NUMERIC STRING if it comes from=
 <br>
 =A0 =A0one of the following:<br></blockquote><br></div>Thanks! I overlooked=
  &quot;numeric string&quot; definition.<br><br><