Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Dec 2017 05:17:32 -0800
From:      David Wolfskill <david@catwhisker.org>
To:        ipfw@freebsd.org
Subject:   ipfw pipe show yields "REDZONE: Buffer overflow detected..."
Message-ID:  <20171219131732.GR1226@albert.catwhisker.org>

next in thread | raw e-mail | index | archive | help

--10AxbcBAbBOxkJp7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Running:
FreeBSD g1-252.catwhisker.org 11.1-STABLE FreeBSD 11.1-STABLE #484  r326952=
M/326974:1101506: Tue Dec 19 03:58:25 PST 2017     root@g1-252.catwhisker.o=
rg:/common/S1/obj/usr/src/sys/CANARY  amd64

(but I also noticed it in passing yesterday, running @r326928):

ipfw pipe show generates:
Dec 19 13:08:38 g1-252 kernel: REDZONE: Buffer overflow detected. 16 bytes =
corrupted after 0xfffff801ab736f48 (328 bytes allocated).
Dec 19 13:08:38 g1-252 kernel: Allocation backtrace:
Dec 19 13:08:38 g1-252 kernel: #0 0xffffffff80d49299 at redzone_setup+0xe9
Dec 19 13:08:38 g1-252 kernel: #1 0xffffffff80a1175d at malloc+0x22d
Dec 19 13:08:38 g1-252 kernel: #2 0xffffffff80c95e07 at dummynet_get+0x337
Dec 19 13:08:38 g1-252 kernel: #3 0xffffffff80ba4102 at rip_ctloutput+0x102
Dec 19 13:08:38 g1-252 kernel: #4 0xffffffff80ac2d9d at sogetopt+0xcd
Dec 19 13:08:38 g1-252 kernel: #5 0xffffffff80ac756b at kern_getsockopt+0xdb
Dec 19 13:08:38 g1-252 kernel: #6 0xffffffff80ac7462 at sys_getsockopt+0x52
Dec 19 13:08:38 g1-252 kernel: #7 0xffffffff80e3a66a at amd64_syscall+0xa6a
Dec 19 13:08:38 g1-252 kernel: #8 0xffffffff80e1cedb at Xfast_syscall+0xfb
Dec 19 13:08:38 g1-252 kernel: Free backtrace:
Dec 19 13:08:38 g1-252 kernel: #0 0xffffffff80d49604 at redzone_check+0x304
Dec 19 13:08:38 g1-252 kernel: #1 0xffffffff80a117b6 at free+0x46
Dec 19 13:08:38 g1-252 kernel: #2 0xffffffff80c9623d at dummynet_get+0x76d
Dec 19 13:08:38 g1-252 kernel: #3 0xffffffff80ba4102 at rip_ctloutput+0x102
Dec 19 13:08:38 g1-252 kernel: #4 0xffffffff80ac2d9d at sogetopt+0xcd
Dec 19 13:08:38 g1-252 kernel: #5 0xffffffff80ac756b at kern_getsockopt+0xdb
Dec 19 13:08:38 g1-252 kernel: #6 0xffffffff80ac7462 at sys_getsockopt+0x52
Dec 19 13:08:38 g1-252 kernel: #7 0xffffffff80e3a66a at amd64_syscall+0xa6a
Dec 19 13:08:38 g1-252 kernel: #8 0xffffffff80e1cedb at Xfast_syscall+0xfb

Similarly; "ipfw sched show" yields:
Dec 19 13:08:54 g1-252 kernel: REDZONE: Buffer overflow detected. 16 bytes =
corrupted after 0xfffff80232e73748 (328 bytes allocated).
Dec 19 13:08:54 g1-252 kernel: Allocation backtrace:
Dec 19 13:08:54 g1-252 kernel: #0 0xffffffff80d49299 at redzone_setup+0xe9
Dec 19 13:08:54 g1-252 kernel: #1 0xffffffff80a1175d at malloc+0x22d
Dec 19 13:08:54 g1-252 kernel: #2 0xffffffff80c95e07 at dummynet_get+0x337
Dec 19 13:08:54 g1-252 kernel: #3 0xffffffff80ba4102 at rip_ctloutput+0x102
Dec 19 13:08:54 g1-252 kernel: #4 0xffffffff80ac2d9d at sogetopt+0xcd
Dec 19 13:08:54 g1-252 kernel: #5 0xffffffff80ac756b at kern_getsockopt+0xdb
Dec 19 13:08:54 g1-252 kernel: #6 0xffffffff80ac7462 at sys_getsockopt+0x52
Dec 19 13:08:54 g1-252 kernel: #7 0xffffffff80e3a66a at amd64_syscall+0xa6a
Dec 19 13:08:54 g1-252 kernel: #8 0xffffffff80e1cedb at Xfast_syscall+0xfb
Dec 19 13:08:54 g1-252 kernel: Free backtrace:
Dec 19 13:08:54 g1-252 kernel: #0 0xffffffff80d49604 at redzone_check+0x304
Dec 19 13:08:54 g1-252 kernel: #1 0xffffffff80a117b6 at free+0x46
Dec 19 13:08:54 g1-252 kernel: #2 0xffffffff80c9623d at dummynet_get+0x76d
Dec 19 13:08:54 g1-252 kernel: #3 0xffffffff80ba4102 at rip_ctloutput+0x102
Dec 19 13:08:54 g1-252 kernel: #4 0xffffffff80ac2d9d at sogetopt+0xcd
Dec 19 13:08:54 g1-252 kernel: #5 0xffffffff80ac756b at kern_getsockopt+0xdb
Dec 19 13:08:54 g1-252 kernel: #6 0xffffffff80ac7462 at sys_getsockopt+0x52
Dec 19 13:08:54 g1-252 kernel: #7 0xffffffff80e3a66a at amd64_syscall+0xa6a
Dec 19 13:08:54 g1-252 kernel: #8 0xffffffff80e1cedb at Xfast_syscall+0xfb


Yesterday was the first full day of running the laptop with FQ-CoDel
implemented, and I noticed that in the evening, things (such as
echoing charcaters in an xterm) would "pause" for a second or two,
fairly randomly.  I can't say that the above were associated with the
pauses, but they are associated with the commands -- this is trivially
reproducible (for me, anyway).

Times in the above logs are UTC.

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
Given his track record so far, I presume that assertions from Trump are lie=
s.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--10AxbcBAbBOxkJp7
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAEBCgBmBQJaORFsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix
NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XAKcH/1WlAhzp7ier2k1A4hw7yoh1
8W/BNHQHSV2fOjvfMf0V9kgC53Iagfktn2RmntpWBGVq1/oMTubnPOgxaQPVtY6Z
RMs5NN2xt0fAnj9bej3iAUH2OwqJZYz7lgxYoCnFttP8d+pVif0qDpBKqythSOmg
vmcLJ3YgQ0l2vm2kH0MXBAE/bw1wWYMwPRRbPk3arj0QHbNyu9l+pg1Ix4DUAoyl
dS7AlJMsZwpBCbwmV/EROGFFECD27Gc8nn+XfqNi0tatCCSR0vQ3poIi1crv+sMh
9K9qalY2OjqFIyPMxebvHERi3Y0ugHCpJCED/tua7e9vBnKRZEc8aMba3jW+1FM=
=DlJE
-----END PGP SIGNATURE-----

--10AxbcBAbBOxkJp7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171219131732.GR1226>