/etc/group is supposed to be world-reable, right? Tools like groups or pw
groupshow certainly seem to think so:
[rstone@rstone-server ~]groups
1001 920
[rstone@rstone-server ~]ls -l /etc/group
-rw--- 1 root 0 482 Nov 14 21:02 /etc/group
[rstone@rstone-server ~]sudo chmod a+r /etc/group
Hi
I have this consistently with:
FreeBSD firewall2.jnb1.gp-online.net 10.0-CURRENT FreeBSD 10.0-CURRENT #30
r243156: Fri Nov 16 20:12:33 SAST 2012
i...@firewall2.jnb1.gp-online.net:/usr/obj/usr/src/sys/FIREWALL amd64
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id =
Wow. So apparently things are even more broken than I though. Let's play,
What group am I in?
root@group-testing:/usr/home/rstone # cd /tmp
root@group-testing:/tmp # pw groupadd testing
root@group-testing:/tmp # mkdir testdir
root@group-testing:/tmp # chown root:testing testdir/
It's a NULL ponter deref. This is my line 484 in if_ethersubr.c:
eh = mtod(m, struct ether_header *);
.. if that's yours, see if eh is NULL?
adrian
On 17 November 2012 07:07, Ian FREISLICH i...@cloudseed.co.za wrote:
Hi
I have this consistently with:
FreeBSD
On Sat, Nov 17, 2012 at 11:20:21AM -0500, Ryan Stone wrote:
Wow. So apparently things are even more broken than I though. Let's play,
What group am I in?
root@group-testing:/usr/home/rstone # cd /tmp
root@group-testing:/tmp # pw groupadd testing
root@group-testing:/tmp # mkdir testdir
Adrian Chadd wrote:
It's a NULL ponter deref. This is my line 484 in if_ethersubr.c:
eh = mtod(m, struct ether_header *);
.. if that's yours, see if eh is NULL?
(kgdb) frame 7
#7 0x8050f534 in ether_nh_input (m=0xfe012521e700)
at
Check what mtod() is doing.
mbuf.h:#define mtod(m, t) ((t)((m)-m_data))
.. so if m-m_data is NULL, bam.
The question is why is m_data NULL here. Someone mbuf cluey is going
to have to answer that. I don't know whether the MH_dat stuff is being
treated as valid but m_data isn't being
Panics along these lines often occur if there is a concurrency bug in a device
driver such that it modifies an mbuf after dispatching to the network stack.
E.g., by freeing it, reusing it, an errant dereference, etc. Not guaranteed,
but that is where I'd start.
Robert
On Sat, 17 Nov 2012,
On Sat, Nov 17, 2012 at 05:07:54PM +0200, Ian FREISLICH wrote:
I I have this consistently with:
I
I FreeBSD firewall2.jnb1.gp-online.net 10.0-CURRENT FreeBSD 10.0-CURRENT #30
r243156: Fri Nov 16 20:12:33 SAST 2012
i...@firewall2.jnb1.gp-online.net:/usr/obj/usr/src/sys/FIREWALL amd64
TB --- 2012-11-17 21:10:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-11-17 21:10:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
W dniu 2012-11-16 17:17, Guido Falsi pisze:
On 11/16/12 16:45, Andriy Gapon wrote:
on 13/11/2012 18:16 Guido Falsi said the following:
My idea, but is just a speculation, i could be very wrong, is that
the geom
tasting code has some problem with multiple vdev root pools.
Guido,
you are
TB --- 2012-11-17 21:10:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-11-17 21:10:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
Or cluster allocation failed, and only the mbuf was used.
Sent from my iPhone
On Nov 17, 2012, at 1:31 PM, Robert Watson rwat...@freebsd.org wrote:
Panics along these lines often occur if there is a concurrency bug in a
device driver such that it modifies an mbuf after dispatching to the
TB --- 2012-11-17 21:10:01 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-11-17 21:10:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
TB --- 2012-11-18 00:56:08 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-11-18 00:56:08 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
TB --- 2012-11-18 01:02:49 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-11-18 01:02:49 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
On 17 November 2012 18:35, FreeBSD Tinderbox tinder...@freebsd.org wrote:
cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
Adrian Chadd adr...@freebsd.org wrote
in CAJ-VmonbG+6vhR=hzg7gnxvgco+1bmh8sk8dye5x0cs7ep2...@mail.gmail.com:
ad On 17 November 2012 18:35, FreeBSD Tinderbox tinder...@freebsd.org wrote:
ad
ad cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes
On every IPv6 address of my card and router and every broadcast and
link-local scope addresses I see now:
kernel: sa6_recoverscope: assumption failure (non 0 ID): ipv6 address
What does it mean and why there are so many of them? I have plain local
net with IPv6 router, nothing unusual.
IPv6
19 matches
Mail list logo
