committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|5a517088||behlendorf1||Aug. 18, 2016, 8 p.m.||Update zfs_create_(009,010)_neg.ksh|
|be9cb745||markj||Aug. 18, 2016, 5:27 p.m.||Add a SIGINFO handler for dtrace(1).|
|32d41fb7||behlendorf1||Aug. 18, 2016, 4:26 p.m.||OpenZFS 7176 - Yet another hole birth issue
This is another bug in the long line of hole-birth related issues. In this particular case, it was discovered that a previous hole-birth fix (illumos bug 6513, commit bc77ba73) did not cover as many cases as we thought it did. While the issue worked in the case of hole-punching (writing zeroes to a large part of a file), it did not deal with truncation, and then writing beyond the new end of the file. The problem is that dbuf_findbp will return ENOENT if the block it's trying to find is beyond the end of the file. If that happens, we assume there is no birth time, and so we lose that information when we write out new blkptrs. We should teach dbuf_findbp to look for things that are beyond the current end, but not beyond the absolute end of the file. Authored by: Paul Dagnelie <email@example.com> Reviewed by: Matthew Ahrens firstname.lastname@example.org Reviewed by: George Wilson email@example.com Ported-by: kernelOfTruth <firstname.lastname@example.org> Signed-off-by: Boris Protopopov <email@example.com> Signed-off-by: Brian Behlendorf <firstname.lastname@example.org> OpenZFS-issue: https://www.illumos.org/issues/7176 OpenZFS-commit: https://github.com/openzfs/openzfs/pull/173/commits/8b9f3ad Upstream-bugs: DLPX-46009 Porting notes: - Fix ISO C90 mixed declaration error in dbuf.c ( int nlevels, epbs; ) ; keep previous position of the initializationcgit
|19820439||emaste||Aug. 18, 2016, 4:22 p.m.||vt: fix old keyboard release in CONS_SETKBD|
|3e7e2333||gnn||Aug. 18, 2016, 10:54 a.m.||Remove the obsolete and unused openbsd_poll system call. (Phase 2)|
|5cba398b||gnn||Aug. 18, 2016, 10:50 a.m.||Remove unusedd and obsolete openbsd_poll system call. (Phase 1)|
|db68f783||bz||Aug. 18, 2016, 10:26 a.m.||Try to fix gcc compilation errors (which are right).|
|4e78ecd2||ache||Aug. 18, 2016, 10:18 a.m.||Fix TAB replaced with spaces in prev. commit.|
|7dc445f8||hselasky||Aug. 18, 2016, 8:49 a.m.||Add support for setting blocking and non-blocking mode on /dev/rdma_cm|
|9ab0e2a7||yongari||Aug. 18, 2016, 7:11 a.m.||When device is detached make sure to stop the controller and make|
|15b5fb58||yongari||Aug. 18, 2016, 6:46 a.m.||In axge_stop(), clear medium receive enable bit which will stop RX|
|310d2ce0||kevlo||Aug. 18, 2016, 6:39 a.m.||Remove <sys/types.h> from the SYNOPSIS.|
|2948462d||yongari||Aug. 18, 2016, 6:35 a.m.||When usbd_transfer_setup() fails, don't call|
|a5d82655||yongari||Aug. 18, 2016, 6:29 a.m.||Introduce axge_rxfilter() which configures RX filtering and replace
axge_setmulti()/axge_setpromisc() with axge_rxfilter(). Multicast filter programming and promiscuous mode requires access to a common RX configuration register so there is no need to use separate functions with added complexity. axge_rxfilter() does not read back AXGE_RCR register since accessing a register in USB is too slow and we already have all knowledge of required configuration. Rebuilding RX filter configuration is simpler and faster than manipulating every bits after reading back the register. Note, axge_rxfilter() does not set RCR_IPE(IP header alignment on 32bit boundary) to disable extra padding bytes insertion. The extra padding wastes ethernet to USB host bandwidth as well as complicating RX handling logic. Current USB framework requires copying RX frames to mbufs so there is no need to worry about alignment. Previously axge_rx_frame() performed wrong bound check due to the extra padding and it was broken when RX checksum offloading is disabled. See added comment in axge_rx_frame () for actual RX packet layout. In axge_init(), disable WOL. It's meaningless to enable WOL in normal operation. In axge_rxeof(), use properly sized mbuf rather than blindly allocating a mbuf cluster. Use RX H/W checksum offloading only when administrator requested RX checksum offloading. Previously it always used RX H/W checksum offloading result regardless of RX checksum offloading state. Separate L4 checksum offloading validation from L3 one and properly set required offloading bits for each layer. This is to fix setting L4 checksum offloading bits for L3 packets. There are still lots of RX errors(probably RX FIFO overflows) under moderate load. Users are strongly recommended to enable ethernet flow control. Reviewed by: kevlo (initial version), hselaskycgit ViewVC
|5afcbd41||sephe||Aug. 18, 2016, 6:03 a.m.||hyperv/kvp: Remove unnecessary function parameter.|