RE: Future of pf / firewall in FreeBSD ? - does it have one ?

[bycn82]

i thought the nat in ipfw is as elegant as in iptables :)
but it is good to know that because different opinion actually is a chance to 
improve.
and why not share with us why the ipfw nat is cumbersome or how to be not 
cumbersome.


> -Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Allan Jude
> Sent: 22 July, 2014 7:13
> To: freebsd-current@freebsd.org
> Subject: Re: Future of pf / firewall in FreeBSD ? - does it have one ?
> 
> On 2014-07-21 09:57, bycn82 wrote:
> > There is no doubt that PF is a really good firewall, But we should
> noticed that there is an ipfw which is originally from FreeBSD while PF
> is from OpenBSD.
> >
> > If there is a requirement that PF can meet but ipfw cannot, then I
> think it is better to improve the ipfw. But if you just like the PF
> style, then I think choose OpenBSD is the better solution. Actually
> OpenBSD is another really good operating system.
> >
> > Like myself, I like CentOS and ipfw, so no choice :)
> >
> >
> 
> The only thing I've really found lacking in IPFW is the NAT
> implementation. Specifically, when trying to do port-forwarding. All of
> the rules have to go in the single 'ipfw nat' rule, and it makes it
> cumbersome to manage.
> 
> 
> --
> Allan Jude


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

NPF (was Re: Future of pf / firewall in FreeBSD ? - does it have one ?)

[Pedro Giffuni]

FWIW, and while I still wonder why we need three packet filters …

There is yet another firewall implementation in NetBSD:

http://www.netbsd.org/~rmind/npf/

It seems to be more portable, it is thought with SMP-friendliness in mind and 
according to a EuroBSDCon talk ports for FreeBSD and Illumos were being 
considered.

Good to have more options … I think.

Pedro. 


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[Allan Jude]

On 2014-07-21 09:57, bycn82 wrote:
> There is no doubt that PF is a really good firewall, But we should noticed 
> that there is an ipfw which is originally from FreeBSD while PF is from 
> OpenBSD.
> 
> If there is a requirement that PF can meet but ipfw cannot, then I think it 
> is better to improve the ipfw. But if you just like the PF style, then I 
> think choose OpenBSD is the better solution. Actually OpenBSD is another 
> really good operating system. 
> 
> Like myself, I like CentOS and ipfw, so no choice :)
> 
> 

The only thing I've really found lacking in IPFW is the NAT
implementation. Specifically, when trying to do port-forwarding. All of
the rules have to go in the single 'ipfw nat' rule, and it makes it
cumbersome to manage.


-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature

clang assertion failure+coredump in clang 3.4.1

[Benjamin Kaduk]

Building some out-of-tree software with a rather long set of compiler 
flags, I can reliably get our clang to crash.
The system is current as of r267362 (June 11), with clang reporting itself 
as FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 
20140512

Target: x86_64-unknown-freebsd11.0
(freefall's clang crashes as well.)

Unfortunately, I don't have debug symbols around for that clang binary.
If someone does have a clang with debug symbols handy, I'd be interested 
in seeing the backtrace.


The processed source file and invocation shell script may be found at:
http://web.mit.edu/kaduk/Public/clang/dumptool-09e584.c(1.1M)
http://web.mit.edu/kaduk/Public/clang/dumptool-09e584.sh


Thanks,

Ben
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[Franco Fichtner]

Hi Julian,

On 21 Jul 2014, at 05:15, Julian Elischer  wrote:

> Most people I talk to just use ipfw and couldn't care whether pf lives or 
> dies.  They have simple requirements and almost any filter would suffice.  I 
> haven't found anything I'd want to use pf for that ipfw doesn't allow me to 
> do. There are things pf does that ipfw doesn't... I just never want them..

this is quite insightful.  The gist of this discussion and the apparent
lack of upgrades to pf(4) seem to indicate that:

(a) other packet filters do the required jobs equally or better
or performance doesn't matter at all.

(b) for more progressive setups and requirements, FreeBSD servers
may as well be complemented with commercial firewalls, hand-rolled
or non-FreeBSD solutions

Is that somewhat accurate, or is there more to the story?


Cheers,
Franco
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Problems starting X on Mac using vesa, radeon or intel drivers when running FreeBSD-CURRENT in EFI

[David King]

> Last week, I created a custom ISO from the latest -CURRENT sources which 
> contained an EFI image that is bootable on my MacBook Pro.
> Both installation and booting from this new FreeBSD 11 EFI system goes 
> without any problems.

Somewhat off-topic, but can you detail how you did this? I've been at this 
unsuccessfully. Did you just do this 
?


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [PATCHES] Extend service(8) and rc(8) was: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

[Lars Engels]

On Sat, Jul 19, 2014 at 12:56:42PM -0700, Adrian Chadd wrote:
> Hi!
> 
> I like it! It's a useful command line API.
> 
> Eventually people will realise there needs to be a more formal method
> for describing/controlling the underlying framework, but I leave that
> up to bapt to figure out and .. well, push people to do. :)
> 
> Thanks!
> 
> 
> 
> -a
> 

[CC trimmed]

I added a -s flag to allow the usage of /etc/rc.conf.d/$script for use
with puppet, etc.

 https://phabric.freebsd.org/D451


pgpCJKyU5Wu9p.pgp
Description: PGP signature

RE: Future of pf / firewall in FreeBSD ? - does it have one ?

[bycn82]

There is no doubt that PF is a really good firewall, But we should noticed that 
there is an ipfw which is originally from FreeBSD while PF is from OpenBSD.

If there is a requirement that PF can meet but ipfw cannot, then I think it is 
better to improve the ipfw. But if you just like the PF style, then I think 
choose OpenBSD is the better solution. Actually OpenBSD is another really good 
operating system. 

Like myself, I like CentOS and ipfw, so no choice :)


> -Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Andreas Nilsson
> Sent: 21 July, 2014 19:46
> To: sth...@nethelp.no
> Cc: Maxim Khitrov; Current FreeBSD; Mailinglists FreeBSD
> Subject: Re: Future of pf / firewall in FreeBSD ? - does it have one ?
> 
> On Mon, Jul 21, 2014 at 8:56 AM,  wrote:
> 
> > > > > Also, the openbsd stack has some essential features missing in
> > freebsd,
> > > > > like mpls and md5 auth for bgp sessions.
> > > >
> > > > I use MD5 auth for BGP sessions every day (and have been doing so
> > > > for several releases). One could definitely wish for better
> > > > integration - having to specify MD5 key both in /etc/ipsec.conf
> > > > and in the Quagga bgpd config is not nice. But it works.
> > > >
> > > As far as I know you can only send out correctly authed stuff but
> > > not validate incoming. Has that changed?
> >
> > Have a look at tcp_signature_verify(), called from tcp_input.c. Added
> > in r221023, see
> >
> > http://svnweb.freebsd.org/base/head/sys/netinet/tcp_input.c?view=log
> >
> > Steinar Haug, Nethelp consulting, sth...@nethelp.no
> >
> > --
> >
> > Revision 221023 - (view) (download) (annotate) - [select for diffs]
> > Modified Mon Apr 25 17:13:40 2011 UTC (3 years, 2 months ago) by
> > attilio File length: 106717 byte(s) Diff to previous 220560 Add the
> > possibility to verify MD5 hash of incoming TCP packets.
> > As long as this is a costy function, even when compiled in (along with
> > the option TCP_SIGNATURE), it can be disabled via the
> > net.inet.tcp.signature_verify_input sysctl.
> >
> > Sponsored by:   Sandvine Incorporated
> > Reviewed by:emaste, bz
> > MFC after:  2 weeks
> >
> > I stand corrected. Excellent news ( for me, that is) :)
> 
> Best regards
> Andeas
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-
> unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[Andreas Nilsson]

On Mon, Jul 21, 2014 at 8:56 AM,  wrote:

> > > > Also, the openbsd stack has some essential features missing in
> freebsd,
> > > > like mpls and md5 auth for bgp sessions.
> > >
> > > I use MD5 auth for BGP sessions every day (and have been doing so for
> > > several releases). One could definitely wish for better integration -
> > > having to specify MD5 key both in /etc/ipsec.conf and in the Quagga
> > > bgpd config is not nice. But it works.
> > >
> > As far as I know you can only send out correctly authed stuff but not
> > validate incoming. Has that changed?
>
> Have a look at tcp_signature_verify(), called from tcp_input.c. Added
> in r221023, see
>
> http://svnweb.freebsd.org/base/head/sys/netinet/tcp_input.c?view=log
>
> Steinar Haug, Nethelp consulting, sth...@nethelp.no
>
> --
>
> Revision 221023 - (view) (download) (annotate) - [select for diffs]
> Modified Mon Apr 25 17:13:40 2011 UTC (3 years, 2 months ago) by attilio
> File length: 106717 byte(s)
> Diff to previous 220560
> Add the possibility to verify MD5 hash of incoming TCP packets.
> As long as this is a costy function, even when compiled in (along with
> the option TCP_SIGNATURE), it can be disabled via the
> net.inet.tcp.signature_verify_input sysctl.
>
> Sponsored by:   Sandvine Incorporated
> Reviewed by:emaste, bz
> MFC after:  2 weeks
>
> I stand corrected. Excellent news ( for me, that is) :)

Best regards
Andeas
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[Andrey V. Elsukov]

On 20.07.2014 18:15, Maxim Khitrov wrote:
> In my opinion, the way forward is to forget (at least temporarily) the
> SMP changes, bring pf in sync with OpenBSD, put a policy in place to
> follow their releases as closely as possible, and then try to
> reintroduce all the SMP work. I think the latter has to be done
> upstream, otherwise it'll always be a story of diverging codebases.
> Furthermore, if FreeBSD developers were willing to spend some time
> improving pf performance on OpenBSD, then Henning and other OpenBSD
> developers might be more receptive to changes that make the porting
> process easier.

Even if you just drop current PF from FreeBSD, there is nobody, who want
to port new PF from OpenBSD. And this is not easy task, as you may
think. Gleb has worked on rewriting PF more than half year. So, return
back all improvements after import will be hard enough and, again,
nobody want to do it. :)

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature

Re: [PANIC][vboxdrv] use afer free/iprtheap

[Larry Rosenman]

Ignore previous, here's the right core:

borg.lerctr.org dumped core - see /var/crash/vmcore.6

Mon Jul 21 03:13:37 CDT 2014

FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #54 r268932M: Sun Jul 
20 19:26:23 CDT 2014 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64

panic: Most recently used by iprtheap

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
Memory modified after free 0xf8056da02d00(120) val=e69eedef @ 
0xf8056da02d10
panic: Most recently used by iprtheap

cpuid = 2
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe100c947360
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe100c947410
vpanic() at vpanic+0x126/frame 0xfe100c947450
panic() at panic+0x43/frame 0xfe100c9474b0
mtrash_ctor() at mtrash_ctor+0x8a/frame 0xfe100c9474e0
uma_zalloc_arg() at uma_zalloc_arg+0x4d1/frame 0xfe100c947550
malloc() at malloc+0x194/frame 0xfe100c9475a0
rtR0MemAllocEx() at rtR0MemAllocEx+0xd2/frame 0xfe100c947600
RTMemAllocZTag() at RTMemAllocZTag+0x14/frame 0xfe100c947620
rtR0MemObjNew() at rtR0MemObjNew+0x2f/frame 0xfe100c947650
rtR0MemObjFreeBSDAllocPhysPages() at rtR0MemObjFreeBSDAllocPhysPages+0x31/frame 
0xfe100c9476a0
rtR0MemObjNativeAllocPhysNC() at rtR0MemObjNativeAllocPhysNC+0x2e/frame 
0xfe100c9476c0
g_aUnits() at g_aUnits+0x58d9/frame 0xfe100c947720
g_aUnits() at g_aUnits+0x266a/frame 0xfe100c9477a0
g_aUnits() at g_aUnits+0x1f9f/frame 0xfe100c947820
g_aUnits() at 0x83257c35/frame 0xfe100c947870
g_aUnits() at 0x8325a0de/frame 0xfe100c9478b0
g_aUnits() at 0x83259c23/frame 0xfe100c9478f0
supdrvIOCtlInnerUnrestricted() at supdrvIOCtlInnerUnrestricted+0x5a1/frame 
0xfe100c947970
VBoxDrvFreeBSDIOCtl() at VBoxDrvFreeBSDIOCtl+0x1e6/frame 0xfe100c9479d0
devfs_ioctl_f() at devfs_ioctl_f+0xfb/frame 0xfe100c947a30
kern_ioctl() at kern_ioctl+0x22b/frame 0xfe100c947a90
sys_ioctl() at sys_ioctl+0x13c/frame 0xfe100c947ae0
amd64_syscall() at amd64_syscall+0x25a/frame 0xfe100c947bf0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe100c947bf0
--- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80128f5ca, rsp = 
0x7f8a5c58, rbp = 0x7f8a5c60 ---
Uptime: 7h12m25s
Dumping 7915 out of 64463 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

Reading symbols from /boot/kernel/linux.ko.symbols...done.
Loaded symbols for /boot/kernel/linux.ko.symbols
Reading symbols from /boot/kernel/if_lagg.ko.symbols...done.
Loaded symbols for /boot/kernel/if_lagg.ko.symbols
Reading symbols from /boot/kernel/snd_envy24ht.ko.symbols...done.
Loaded symbols for /boot/kernel/snd_envy24ht.ko.symbols
Reading symbols from /boot/kernel/snd_spicds.ko.symbols...done.
Loaded symbols for /boot/kernel/snd_spicds.ko.symbols
Reading symbols from /boot/kernel/coretemp.ko.symbols...done.
Loaded symbols for /boot/kernel/coretemp.ko.symbols
Reading symbols from /boot/kernel/ichsmb.ko.symbols...done.
Loaded symbols for /boot/kernel/ichsmb.ko.symbols
Reading symbols from /boot/kernel/smbus.ko.symbols...done.
Loaded symbols for /boot/kernel/smbus.ko.symbols
Reading symbols from /boot/kernel/ichwd.ko.symbols...done.
Loaded symbols for /boot/kernel/ichwd.ko.symbols
Reading symbols from /boot/kernel/cpuctl.ko.symbols...done.
Loaded symbols for /boot/kernel/cpuctl.ko.symbols
Reading symbols from /boot/kernel/crypto.ko.symbols...done.
Loaded symbols for /boot/kernel/crypto.ko.symbols
Reading symbols from /boot/kernel/cryptodev.ko.symbols...done.
Loaded symbols for /boot/kernel/cryptodev.ko.symbols
Reading symbols from /boot/kernel/dtraceall.ko.symbols...done.
Loaded symbols for /boot/kernel/dtraceall.ko.symbols
Reading symbols from /boot/kernel/profile.ko.symbols...done.
Loaded symbols for /boot/kernel/profile.ko.symbols
Reading symbols from /boot/kernel/cyclic.ko.symbols...done.
Loaded symbols for /boot/kernel/cyclic.ko.symbols
Reading symbols from /boot/kernel/dtrace.ko.symbols...done.
Loaded symbols for /boot/kernel/dtrace.ko.symbols
Reading symbols from /boot/kernel/systrace_freebsd32.ko.symbols...done.
Loaded symbols for /boot/kernel/systrace_freebsd32.ko.symbols
Reading symbols from /boot/kernel/systrace.ko.symbols...done.
Loaded symbols for /boot/kernel/systrace.ko.symbols
Reading symbols from /boot/kernel/sdt.ko.symbols...done.
Loaded symbols for /boot/kernel/sdt.ko.symbols
Reading symbols from /boot/kernel/lockstat.ko.symbols...done.
Loaded symbols for /boot/kernel/lockstat.ko.symbols
Reading symbols from /boot/kernel/fasttrap.ko.symbols...done.
Loaded symbols for /boot/kernel/fasttr

[PANIC][vboxdrv] use afer free/iprtheap

[Larry Rosenman]

Got the following panic this morning


borg.lerctr.org dumped core - see /var/crash/vmcore.5

Sun Jul 20 03:28:12 CDT 2014

FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #50 r268894M: Sat Jul 
19 18:06:08 CDT 2014 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64

panic: solaris assert: !(zio->io_flags & ZIO_FLAG_DELEGATED), file: 
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 2874

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
panic: solaris assert: !(zio->io_flags & ZIO_FLAG_DELEGATED), file: 
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 2874
cpuid = 7
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe100c49f930
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe100c49f9e0
vpanic() at vpanic+0x126/frame 0xfe100c49fa20
panic() at panic+0x43/frame 0xfe100c49fa80
assfail() at assfail+0x1d/frame 0xfe100c49fa90
zio_vdev_io_assess() at zio_vdev_io_assess+0x2ed/frame 0xfe100c49fac0
zio_execute() at zio_execute+0x1e9/frame 0xfe100c49fb20
taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfe100c49fb80
taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfe100c49fbb0
fork_exit() at fork_exit+0x84/frame 0xfe100c49fbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe100c49fbf0
--- trap 0, rip = 0, rsp = 0xfe100c49fcb0, rbp = 0 ---
Uptime: 8h57m17s
(ada2:ahcich2:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00
(ada2:ahcich2:0:0:0): CAM status: Command timeout
(ada2:ahcich2:0:0:0): Error 5, Retries exhausted
(ada2:ahcich2:0:0:0): Synchronize cache failed
Dumping 7745 out of 64463 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

Reading symbols from /boot/kernel/linux.ko.symbols...done.
Loaded symbols for /boot/kernel/linux.ko.symbols
Reading symbols from /boot/kernel/if_lagg.ko.symbols...done.
Loaded symbols for /boot/kernel/if_lagg.ko.symbols
Reading symbols from /boot/kernel/snd_envy24ht.ko.symbols...done.
Loaded symbols for /boot/kernel/snd_envy24ht.ko.symbols
Reading symbols from /boot/kernel/snd_spicds.ko.symbols...done.
Loaded symbols for /boot/kernel/snd_spicds.ko.symbols
Reading symbols from /boot/kernel/coretemp.ko.symbols...done.
Loaded symbols for /boot/kernel/coretemp.ko.symbols
Reading symbols from /boot/kernel/ichsmb.ko.symbols...done.
Loaded symbols for /boot/kernel/ichsmb.ko.symbols
Reading symbols from /boot/kernel/smbus.ko.symbols...done.
Loaded symbols for /boot/kernel/smbus.ko.symbols
Reading symbols from /boot/kernel/ichwd.ko.symbols...done.
Loaded symbols for /boot/kernel/ichwd.ko.symbols
Reading symbols from /boot/kernel/cpuctl.ko.symbols...done.
Loaded symbols for /boot/kernel/cpuctl.ko.symbols
Reading symbols from /boot/kernel/crypto.ko.symbols...done.
Loaded symbols for /boot/kernel/crypto.ko.symbols
Reading symbols from /boot/kernel/cryptodev.ko.symbols...done.
Loaded symbols for /boot/kernel/cryptodev.ko.symbols
Reading symbols from /boot/kernel/dtraceall.ko.symbols...done.
Loaded symbols for /boot/kernel/dtraceall.ko.symbols
Reading symbols from /boot/kernel/profile.ko.symbols...done.
Loaded symbols for /boot/kernel/profile.ko.symbols
Reading symbols from /boot/kernel/cyclic.ko.symbols...done.
Loaded symbols for /boot/kernel/cyclic.ko.symbols
Reading symbols from /boot/kernel/dtrace.ko.symbols...done.
Loaded symbols for /boot/kernel/dtrace.ko.symbols
Reading symbols from /boot/kernel/systrace_freebsd32.ko.symbols...done.
Loaded symbols for /boot/kernel/systrace_freebsd32.ko.symbols
Reading symbols from /boot/kernel/systrace.ko.symbols...done.
Loaded symbols for /boot/kernel/systrace.ko.symbols
Reading symbols from /boot/kernel/sdt.ko.symbols...done.
Loaded symbols for /boot/kernel/sdt.ko.symbols
Reading symbols from /boot/kernel/lockstat.ko.symbols...done.
Loaded symbols for /boot/kernel/lockstat.ko.symbols
Reading symbols from /boot/kernel/fasttrap.ko.symbols...done.
Loaded symbols for /boot/kernel/fasttrap.ko.symbols
Reading symbols from /boot/kernel/fbt.ko.symbols...done.
Loaded symbols for /boot/kernel/fbt.ko.symbols
Reading symbols from /boot/kernel/dtnfscl.ko.symbols...done.
Loaded symbols for /boot/kernel/dtnfscl.ko.symbols
Reading symbols from /boot/kernel/dtmalloc.ko.symbols...done.
Loaded symbols for /boot/kernel/dtmalloc.ko.symbols
Reading symbols from /boot/modules/vboxdrv.ko...done.
Loaded symbols for /boot/modules/vboxdrv.ko
Reading symbols from /boot/kernel/ipmi.ko.symbols...done.
Loaded symbols for /boot/kernel/ipmi.ko.symbols
Reading symbols from /boot/kernel/ipmi_linux.ko.symbols...done.
Load

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

[Larry Rosenman]

On 2014-07-21 00:24, Florian Smeets wrote:

On 21/07/14 01:46, Steven Hartland wrote:

- Original Message - From: "Larry Rosenman" 
To: "Steven Hartland" 
Cc: ; 
Sent: Monday, July 21, 2014 12:22 AM
Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548



On 2014-07-20 18:21, Steven Hartland wrote:

Can you try reverting r265321 and see if you still see the
same crash?

   Regards
   Steve

I'll do the revert, but it's been a ONE TIME hit.

There was a followup to mine with a reproducible poudriere crash like
mine.


If you don't have a reproducable senario I'd hold off.

Florian, is yours reproducable and can you send me
a pretty print of the crashing zio?




can you set print pretty on
and then reprint the zio?

That makes it "pretty" for Steve.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org
US Mail: 108 Turvey Cove, Hutto, TX 78634-5688
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"