[Bug 127912] In theory, uncompress(1) may crash and SEGV

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=127912

NGie Cooper  changed:

   What|Removed |Added

 CC||n...@freebsd.org

--- Comment #1 from NGie Cooper  ---
This is the line that the OP is suggesting have  a conditional added to it:
https://svnweb.freebsd.org/base/head/usr.bin/compress/zopen.c?revision=146336=markup=146336#l619
.

-- 
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 204554] Intel 6300ESB SATA150 cannot find disk and boot rerun of 127391

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204554

Alexander Motin  changed:

   What|Removed |Added

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

--- Comment #2 from Alexander Motin  ---
The patch is committed to FreeBSD head.

-- 
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 204554] Intel 6300ESB SATA150 cannot find disk and boot rerun of 127391

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204554

--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mav
Date: Sun Nov 15 10:58:02 UTC 2015
New revision: 290855
URL: https://svnweb.freebsd.org/changeset/base/290855

Log:
  Increase reset assertion time from 10 to 100us.

  On my own tests I see no effect from this change, but I also can't
  reproduce the reported problem in general.

  PR:127391
  PR:204554
  Submitted by:s...@iranger.com
  MFC after:2 weeks

Changes:
  head/sys/dev/ata/chipsets/ata-intel.c

-- 
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 127391] [ata] [patch] Intel 6300ESB SATA150 cannot find disk and boot under 6.3 [regression]

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=127391

--- Comment #17 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mav
Date: Sun Nov 15 10:58:02 UTC 2015
New revision: 290855
URL: https://svnweb.freebsd.org/changeset/base/290855

Log:
  Increase reset assertion time from 10 to 100us.

  On my own tests I see no effect from this change, but I also can't
  reproduce the reported problem in general.

  PR:127391
  PR:204554
  Submitted by:s...@iranger.com
  MFC after:2 weeks

Changes:
  head/sys/dev/ata/chipsets/ata-intel.c

-- 
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 127391] [ata] [patch] Intel 6300ESB SATA150 cannot find disk and boot under 6.3 [regression]

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=127391

Alexander Motin  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|m...@freebsd.org
 Depends on||204554
 CC||m...@freebsd.org

--- Comment #18 from Alexander Motin  ---
The patch is committed to FreeBSD head.

-- 
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 204568] gif(4) interface remembers configuration after being destroyed

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204568

Bug ID: 204568
   Summary: gif(4) interface remembers configuration after being
destroyed
   Product: Base System
   Version: 10.2-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: felic...@torchbox.com

FreeBSD mayflower.choxf.torchbox.net 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #5
r290741: Sat Nov 14 16:56:58 GMT 2015
r...@mayflower.choxf.torchbox.net:/usr/src/sys/amd64/compile/MAYFLOWER  amd64

mayflower:/root# ifconfig gif1
gif1: flags=8051 metric 0 mtu 1480
tunnel inet 78.32.251.196 --> 193.227.244.121
nd6 options=29
mayflower:/root# ifconfig gif1 destroy
mayflower:/root# ifconfig gif1
ifconfig: interface gif1 does not exist
mayflower:/root# ifconfig gif1 create
mayflower:/root# ifconfig gif1
gif1: flags=8051 metric 0 mtu 1480
tunnel inet 78.32.251.196 --> 193.227.244.121
nd6 options=29
mayflower:/root#

-- 
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 204571] sort with multiple numerical keys fail in sparc64

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204571

Bug ID: 204571
   Summary: sort with multiple numerical keys fail in sparc64
   Product: Base System
   Version: 10.2-STABLE
  Hardware: sparc64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: rodr...@freebsd.org

If you have a file with numerical values like the one bellow :

% cat testfile
12 1 3
19 1 6
2 1 1
7 1 2
1 2 1
16 2 4

% sort -k2n testfile
2 1 1
7 1 2
12 1 3
19 1 6
1 2 1
16 2 4

% sort -k2n -k1n testfile

returns nothing but error 255
The same if we try any combination if the first key is numeric

Investigations on the code shows that we fail in mt_sort() function.

-- 
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 204340] [panic] nfsd, em, msix, fatal trap 9

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340

Rick Macklem  changed:

   What|Removed |Added

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

--- Comment #2 from Rick Macklem  ---
Created attachment 163160
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163160=edit
patch that might fix this problem

I think this crash might have been caused by a race
between svcpool_destroy() and the socket upcall.
The code in svcpool_destroy() assumes that SVC_RELEASE(xprt)
drops the ref cnt to 0, so that SVC_DESTROY() is called.
-->SVC_DESTROY() shuts down the socket upcall.
--> If the ref cnt doesn't go to 0, svcpool_destroy() will
mtx_destroy() the mutexes prematurely.

I am not sure, but the race might have been introduced by
r267228 since, prior to this there was a single mutex for
the pool, held while all xprt's are unregistered.
After r267228, there is a group of mutexes, where the code
only held one at a time, so I think an xprt might get re-registered
on another group after that group has had all de-registered.

The attached little patch moves the mtx_lock() calls to a
separate loop before the xprt_unregister loops, so that all
locks are held while all are de-registered.

I've added mav@ to the cc list, since he might be the guy
that actually understands this.

Anyhow, if you could test the attached patch with msi interrupts
re-enabled and see if the crashes go away, that would be great.
(I don't think that this indicates that the em(4) driver is broken.
 I suspect that it just affects timing of the interrupts that tripped
 over this race.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list 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 68690] [libc] write(2) returns wrong value when EFAULT

2015-11-15 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=68690

NGie Cooper  changed:

   What|Removed |Added

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

--- Comment #4 from NGie Cooper  ---
Taking for the RETEST.

-- 
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"