[Bug 219453] tcpmd5 kernel module regression

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453

--- Comment #3 from Marek Zarychta  ---
FYI something was broken between 11.0-STABLE r318137 and 11.1-PRERELEASE
r318590.
In our setup, TCP MD5 signed packets originate from vlan interface created on
lagg interface, so the issue could be VLAN or LAGG specific. 
I don't know if freshest PRERELEASE works fine. For sure r318137 recompiled
from sources works correctly, although just after the bootup, some packets with
bad signatures occurred:

# netstat -sp tcp | grep signature
8794 packets with matching signature received
18 packets with bad signature received
0 times failed to make signature due to no SA
1 time unexpected signature received
1 time no signature provided by segment

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Any holes?

2017-05-22 Thread The Doctor
Just tried to compile a port of www/firefox and most service
except httpd was offline from 90 minutes and www/firefox just stopted compiling
and most services was restored.

Just had to restart a number of Linux boxes virtualised here.

Is this a memory, kernel or Hardware Issue?

The server was purchased from IXSystems using Supermicro  MB

Dual 1.7GHz CPUS

and 16 GB memory 

replacing again BSD/OS 4.3 servers

and have been in service for 10 months now.


-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
UK Stop Theresa MAy MT V2 and Impotent Corbyn, Vote Farron and LDEm!!
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219467] `mtree -R type -k flags` prints out type= keyword attributes, contrary to what the manpage says it should do

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219467

--- Comment #1 from Ngie Cooper  ---
(In reply to Ngie Cooper from comment #0)

*clear omit -> omit

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219467] `mtree -R type -k flags` prints out type= keyword attributes, contrary to what the manpage says it should do

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219467

Bug ID: 219467
   Summary: `mtree -R type -k flags` prints out type= keyword
attributes, contrary to what the manpage says it
should do
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: n...@freebsd.org

Per mtree(8), passing `-R type -k flags` should clear omit type keywords from
the spec created via mtree:

 -k keywordsUse the type keyword plus the specified (whitespace or
comma separated) keywords instead of the current set
of keywords.  If `all' is specified, use all of the
other keywords.  If the type keyword is not desired,
suppress it with -R type.

Trying this though, demonstrates that that is not the case:

$ sudo mtree -cn -R type -k flags -p /usr/bin/ -x | grep type=
/set type=file flags=uarch
.   type=dir
chfntype=link
chshtype=link
cpiotype=link
mailq   type=link
newaliases  type=link
perltype=link
perl5   type=link
pgrep   type=link
pkill   type=link
stelnet type=link
tar type=link
ypchfn  type=link
ypchpasstype=link
ypchsh  type=link
yppasswdtype=link

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219464] [PATCH] linux_getrandom always returns 0

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219464

Maciej Pasternacki  changed:

   What|Removed |Added

 CC||dcha...@freebsd.org

--- Comment #1 from Maciej Pasternacki  ---
Cc: dchagin as r315505 committer

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219464] [PATCH] linux_getrandom always returns 0

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219464

Bug ID: 219464
   Summary: [PATCH] linux_getrandom always returns 0
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: mac...@pasternacki.net

Created attachment 182818
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182818=edit
linux_getrandom.patch

In a Linux-based jail, running Ubuntu 16.04, `lsb_release` command (which is
widely used in various scripts and during Factorio startup) hangs. `top` shows
it forks a `python3.5` process which uses 100% CPU. `truss` shows this process
repeatedly calls `linux_getrandom(…)`, which always returns 0.

`man 2 getrandom` on Ubuntu 16.04 specifies that this syscall should return
number of random bytes written
(http://man7.org/linux/man-pages/man2/getrandom.2.html). A short test program
shows that this it returns positive value on Linux, and returns 0 on FreeBSD
despite the fact that random bytes have been written to the buffer:

> $ cat test_getrandom.c
> #define _GNU_SOURCE
> #include 
> #include 
> #include 
> #include 
> 
> int main(void) {
> int rv;
> int buf = 0;
> rv = syscall(SYS_getrandom, , sizeof(buf), GRND_NONBLOCK);
> printf("getrandom(, %d, 0) => %d buf=%d\n", (int)sizeof(buf), rv, 
> buf);
> return 0;
> }

When this program runs natively on Linux, `getrandom(2)` returns size of
buffer:

> $ ./test_getrandom
> getrandom(, 4, 0) => 4 buf=-707083248

On FreeBSD 12-CURRENT (possibly also on 11-STABLE, r315505 which introduces
this implementation is marked for MFC after 1 month), the syscall always
returns 0:

> $ ./test_getrandom
> getrandom(, 4, 0) => 0 buf=-1643413282

After applying attached patch, return value reported from the test program is
the same as on native Linux, and `lsb_release` no longer hangs:

> $ ./test_getrandom
> getrandom(, 4, 0) => 4 buf=-943351330
> $ lsb_release -a
> No LSB modules are available.
> Distributor ID:   Ubuntu
> Description:  Ubuntu 16.04.2 LTS
> Release:  16.04
> Codename: xenial

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 219453] tcpmd5 kernel module regression

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453

--- Comment #2 from dgilb...@eicat.ca ---
Oh-and ... this all worked fine in 11.0-RELEASE (save the ipv6 bug ... which
was supposedly patched in 11.0-STABLE (nice if that stays "fixed" too)).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219453] tcpmd5 kernel module regression

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453

dgilb...@eicat.ca changed:

   What|Removed |Added

 CC||dgilb...@eicat.ca

--- Comment #1 from dgilb...@eicat.ca ---
This also affects quagga.  AFAICT, we're not sending MD5, either.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213092] tar(1) continues to run and error after non-existent file

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213092

Glen Barber  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200079] [patch] Canada Uses ISO 8601 for Dates

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200079

Glen Barber  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 216910] [patch] contrib/dma different behavior when called as "mailq" instead of "/usr/bin/mailq"

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216910

Glen Barber  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 210479] blacklistd(8) and sshd(8) causes login delays and syslog(8) spam

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479

Glen Barber  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219457] ZFS ARC eviction & system hangup

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219457

--- Comment #5 from Anton Sayetsky  ---
(In reply to Anton Sayetsky from comment #4)

It's better to duplicate last lines from truss output & procstat output here:

= truss output =
clock_gettime(13,{1495402129.0 })= 0 (0x0)
openat(0xff9c,0x80245b0a0,0x100601,0x1b6,0x7fffd580,0x801d13b20) = 3
(0x3)
fcntl(3,F_GETFD,)= 1 (0x1)
fstat(3,{ mode=crw-rw-rw- ,inode=8,size=0,blksize=4096 }) = 0 (0x0)
openat(0xff9c,0x8008bc804,0x10,0x0,0x80080245c7d7,0x0) = 4 (0x4)
fcntl(4,F_GETFD,)   

= procstar output related to tar =
75044 101901 bsdtar   -mi_switch+0xbe sleepq_wait+0x3a
_cv_wait+0x14d vmem_xalloc+0x568 vmem_alloc+0x3d kmem_malloc+0x33
uma_large_malloc+0x46 malloc+0x40 fdgrowtable+0x5b fdalloc+0x6c do_dup+0x18f
kern_fcntl+0x6dc kern_fcntl_freebsd+0xae amd64_syscall+0x307 Xfast_syscall+0xfb

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219457] ZFS ARC eviction & system hangup

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219457

--- Comment #4 from Anton Sayetsky  ---
Created attachment 182807
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182807=edit
output of "truss tar cvf /dev/null /usr/ports" that starts ARC eviction

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219457] ZFS ARC eviction & system hangup

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219457

--- Comment #3 from Anton Sayetsky  ---
Created attachment 182806
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182806=edit
output of "procstat -kka" when ARC reaches minimum

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219457] ZFS ARC eviction & system hangup

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219457

--- Comment #2 from Anton Sayetsky  ---
Created attachment 182805
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182805=edit
output of "vmstat -z" when ARC reaches minimum

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219457] ZFS ARC eviction & system hangup

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219457

--- Comment #1 from Anton Sayetsky  ---
Created attachment 182804
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182804=edit
output of "zfs-stats -a" when ARC reaches minimum

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219457] ZFS ARC eviction & system hangup

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219457

Bug ID: 219457
   Summary: ZFS ARC eviction & system hangup
   Product: Base System
   Version: 10.3-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: vsasja...@gmail.com

I have a machine with 256 GiB of RAM (249 GiB managed) that serves files over
plain HTTP with nginx & AIO.
After system starup ARC grows to its maximum size - ~233 GiB (so about ten gigs
are always free), then it slightly drops down to ~228 GiB. Only after that if I
start some processes:
1. They will immediately hang in "D" state;
2. pagedaemon/uma enters clearing state;
3. ARC starts to evict till its minimum size;
4. When ARC reaches minimum entire system becomes unresponsive with a delay
(from 5 mins to 8 hours).

Some examples of hanging processes:
1. conftest when building devel/m4 (PR in "See Also");
2. tar on any directory, e.g. tar cvf /dev/null /usr/ports.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219431] MFC https://svnweb.freebsd.org/base?view=revision=311361

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219431

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|adr...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219433] ZFS volume cannot be created by delegated user

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219433

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219453] tcpmd5 kernel module regression

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453

Mark Linimon  changed:

   What|Removed |Added

 CC||lini...@freebsd.org
   Keywords||regression

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219453] tcpmd5 kernel module regression

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453

Marek Zarychta  changed:

   What|Removed |Added

Summary|tcpmd5 kernel module|tcpmd5 kernel module
   |regrassion  |regression

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 219451] [dtrace] Certain llquantize() parameters trigger assertion

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219451

Bug ID: 219451
   Summary: [dtrace] Certain llquantize() parameters trigger
assertion
   Product: Base System
   Version: 11.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: f...@fabiankeil.de
CC: freebsd-dtr...@freebsd.org

Created attachment 182796
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182796=edit
libdtrace: Prevent an assertion from triggering with certain llquantize()
parameters

On a system based on r318579/0c33b79a4 the following dtrace command reliably
triggers an
assertion when printing output:

 fk@t520 ~ $sudo dtrace -n 'syscall::read:return /execname ==
"privoxy"/ { @[execname] = llquantize(arg0, 100, 0, 10, 100); @m = max(arg0)}'
 [...]
 9800 | 0
 9900 | 0
1 | 37
2 | 0
 Assertion failed: (value < next), file
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c,
line 1083.
 Abort trap

 (gdb) where
 #0  0x0008011effda in thr_kill () from /lib/libc.so.7
 #1  0x0008011effa4 in __raise (s=6) at
/usr/src/lib/libc/gen/raise.c:52
 #2  0x0008011eff19 in abort () at
/usr/src/lib/libc/stdlib/abort.c:65
 #3  0x00080088c3b2 in __assert (expr=0x8008d3172 "value < next",
file=0x8008d3078
"/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c",
line=1083)
 at
/usr/src/cddl/lib/libdtrace/../../../cddl/compat/opensolaris/include/assert.h:56
 #4  0x00080088c190 in dt_print_llquantize (dtp=0x802633000,
fp=0x8014c37e8, addr=0x80269a110, size=7840, normal=1) at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume
.c:1083
 #5  0x00080088e37d in dt_print_datum (dtp=0x802633000,
fp=0x8014c37e8, rec=0x8026900e8, addr=0x80269a110 "d", size=7848,
aggdata=0x802690150, normal=1, pd=0x7fffe750)
 at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c:2211
 #6  0x00080088dc12 in dt_print_aggs (aggsdata=0x7fffe630,
naggvars=1, arg=0x7fffe750) at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c:2313
 #7  0x00080088e6cf in dt_print_agg (aggdata=0x802690150,
arg=0x7fffe750) at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c:2361
 #8  0x000800895f8b in dt_aggregate_walk_sorted (dtp=0x802633000,
func=0x80088e610 , arg=0x7fffe750, sfunc=0x0)
 at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c:1585
 #9  0x000800895d39 in dtrace_aggregate_walk_sorted
(dtp=0x802633000, func=0x80088e610 , arg=0x7fffe750)
 at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c:1605
 #10 0x000800897f12 in dtrace_aggregate_print (dtp=0x802633000,
fp=0x8014c37e8, func=0x800895d10 )
 at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c:2130
 #11 0x00403a5e in main (argc=, argv=) at
/usr/src/cddl/usr.sbin/dtrace/../../../cddl/contrib/opensolaris/cmd/dtrace/dtrace.c:2005
 (gdb) f 4
 #4  0x00080088c190 in dt_print_llquantize (dtp=0x802633000,
fp=0x8014c37e8, addr=0x80269a110, size=7840, normal=1) at
/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume
.c:1083
 1083   assert(value < next);
 (gdb) p step
 $2915 = 77662796314522419
 (gdb) p value
 $2916 = 7834326075677972872
 (gdb) p next
 $2917 = 7766279631452241920

It works as expected when replacing the 10 with a 5.

Various other parameter combinations work as expected as well and I've used
similar commands for weeks without issues.

The problem is reproducible with other execnames as long as the probe fires.

The "@m = max(arg0)" part isn't required to trigger the assertion but I only
noticed it
after already patching the system where libdtrace is build with reduced
optimizations.

The attached patch prevents the assertion from triggering but may not be the
best solution.

The code flow in dt_print_llquantize() seems strange to me and maybe the
loop should break if "bin" reaches "last_bin" instead. My 

[Bug 219356] Using AES-GCM with IPSEC with aesni module loaded panics FreeBSD 11 stable

2017-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219356

Andrey V. Elsukov  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|a...@freebsd.org
 Status|New |In Progress

--- Comment #4 from Andrey V. Elsukov  ---
Created attachment 182793
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182793=edit
Proposed patch (untested)

Thanks. The last trace is very helpful. Can you try this patch? It should be
applicable to both stable/11 and head/.

The problem triggered by error in crypto code. When AES-GCM fails authenticate
decrypted data, it returns EBADMSG error code. This error code was handled
incorrectly in new IPsec code and double free occurred for SA reference. This
patch removed extra free().

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"