DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082021-05-27T04:40:52ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Submit #3276 (New): Add option controlling whether gpt expand expands the last par...https://bugs.dragonflybsd.org/issues/32762021-05-27T04:40:52Zfalsifian
<p>Just today I needed a version of the "gpt expand" command that doesn't extend the last partition. The attached patch adds a -x option; the last partition is only expanded if -x is specified.</p>
<p>I have done minimal testing:</p>
<p>- I successfully used it without <del>x after copying my laptop's data to a larger SSD, leaving plenty of space at the end for me to install DragonflyBSD on top of the two existing OSs :</del>)</p>
<p>- I did a really quick test with the -x option on a hastily created vnode disk initialized with gpt init. I just verified that after expanding with -x, the Dfly partition got bigger.</p>
<p>I'm happy to do more testing if requested, though I'm not sure exactly what to try.</p>
<p>(This patch changes the default behaviour. I suppose it could be reversed, but a "don't expand the last partition option" seems a bit more convoluted conceptually.)</p>
<p>Patch is vs. commit 42a874b478.</p> DragonFlyBSD - Submit #3227 (New): Add HAMMER2 instructions in the installation medium READMEhttps://bugs.dragonflybsd.org/issues/32272020-03-26T22:34:50Zdaftaupepierre-alain@toret.fr
<p>As it has been discussed on irc, here's an attempt to give at least basic instructions on how to install manually using HAMMER2.</p> DragonFlyBSD - Submit #3154 (New): Update serial handling in bootloaderhttps://bugs.dragonflybsd.org/issues/31542018-11-01T19:43:25Zddegroot
<p>Allow changing serial baud rate in bootloader during boot1/boot2. The speed will automatically be taken over by the loader.</p>
<p>The patch contains multiple changes to improve serial handling through the bootprocess and <br />can be found here: <a class="external" href="https://github.com/DragonFlyBSD/DragonFlyBSD/pull/7">https://github.com/DragonFlyBSD/DragonFlyBSD/pull/7</a></p> DragonFlyBSD - Submit #3147 (New): Enable headless installationhttps://bugs.dragonflybsd.org/issues/31472018-10-08T10:20:30Zddegroot
<p>This patch allow installer frontend (dfuife_curses) to connect to the backend from a remote machine.</p>
<p>Patch also includes a small change to two installer makefiles, so that it can be build correctly from the /usr/src/nrelease directory (not sure if this change is formatted in a way that is acceptable).</p> DragonFlyBSD - Submit #3135 (New): Add EVFILT_RECV and EVFILT_SENDhttps://bugs.dragonflybsd.org/issues/31352018-05-26T04:59:15Ztautolog
<p>This isn't complete yet, as I need to add entries in the manual, and I would like to add some more filtering code for listen sockets, and some other types of files. But I wanted to show this theory, and get feedback.</p>
<p>I spend a lot of time trying to optimize network event loops. What I end up doing is writing code that speculates on the state of the socket buffers. Level-triggering works okay for reading for some time, but if the protocol handler gets blocked, it needs to deregister or get itself into an event spin, so there ends up being a lot of de-registering and re-registering in a sophisticated platform. So then EV_ONESHOT can be used, or EV_DISPATCH with EV_ENABLE, which basically gives you edge-triggering, but then you need to register all the time. Luckily, kqueue allows you to batch these registrations, so the overhead isn't so bad, but it requires adding codepaths that aren't required in linux. So, I came up with something that I think is even better, after looking at how to add edge-triggering into kqueue.</p>
<p>kqueue has the data field that reports the socket availability in bytes. The issue with level-triggering is that the userland side only needs to be made aware of changes to that state. I realized that a more optimal interface would be for the userland to register once for each side of the connection, and then the kernel gives a single update per change to any of the socket state. Then the application can merely store the latest kevent struct on its connection struct, and always have the latest information that the kernel has on the state of the socket buffers. Then, sophisticated optimizations become straightforward. See the example echo network server in kqsbtest.c.</p> DragonFlyBSD - Submit #3041 (New): firmware: Remove embedding of multiple images in one module.https://bugs.dragonflybsd.org/issues/30412017-05-25T12:23:23ZAnonymous
<p>Hello,</p>
<p>this patch removes possibility of embedding more than one firmware image in one kernel module through the parent reference in the firmware_register() function.</p>
<p>This patch is a preparation for firmware subsystem modification for moving firmware images from kernel modules to userland.</p>
<p>The mechanism is not used and it can be functionally fully replaced by putting each firmware image in its own module.</p>
<p>Removing the functionality significantly simplifies handling of firmware images. If firmware images are moved to userland the logical grouping of modules could be expressed by putting the related firmware images into one directory if needed.</p>
<p>jan</p> DragonFlyBSD - Submit #2933 (New): Remove unix domain socket support from cat(1)https://bugs.dragonflybsd.org/issues/29332016-08-02T01:09:06Zsevanventure37@geeklan.co.uk
<p>Introduced in FreeBSD<sup><a href="#fn1">1</a></sup> and inherited in DragonFly BSD, cat(1) has the ability to utilise a unix domain socket but the usecase is somewhat limited & better served by other tools eg netcat. Attached diff removes the functionality & restores previous behaviour. This feature is exclusive to FreeBSD & DragonFly BSD and has not been adopted by the other BSDs.</p>
<p>[1] <a class="external" href="https://svnweb.freebsd.org/base/head/bin/cat/cat.c?r1=78732&r2=83482&view=patch">https://svnweb.freebsd.org/base/head/bin/cat/cat.c?r1=78732&r2=83482&view=patch</a></p> DragonFlyBSD - Submit #2921 (New): Allow moused to accept userland mouse eventshttps://bugs.dragonflybsd.org/issues/29212016-06-10T21:38:01Ztautolog
<p>Allow moused to work with sysmouse when the port is a pipe,<br /> not a real mouse device with working ioctls. Allows simple userland injection<br /> of mouse events.</p>
<p>Attached is an example that works with the Griffin PowerMate<br /><a class="external" href="https://www.amazon.com/Griffin-Technology-NA16029-Multimedia-Controller/dp/B003VWU2WA/">https://www.amazon.com/Griffin-Technology-NA16029-Multimedia-Controller/dp/B003VWU2WA/</a></p>
<p>Just run `./scrollwheel.py scroller.fifo` as a user account, and then run `moused -p scroller.fifo -t sysmouse` as root.</p>
<p>If you press down the wheel, it will multiply scrolls by 32, so you can fly through code like in the movies.</p> DragonFlyBSD - Submit #2790 (New): filedesc softrefs increment code factoringhttps://bugs.dragonflybsd.org/issues/27902015-02-21T12:00:29Zdclinkdevnexen@gmail.com
<p>Just putting locking + sifters field update in common function ...</p> DragonFlyBSD - Submit #2721 (Feedback): Some few zalloc calls to objcache ones replacementshttps://bugs.dragonflybsd.org/issues/27212014-08-30T17:12:51Zdclinkdevnexen@gmail.comDragonFlyBSD - Submit #2717 (Feedback): Out of range numeric handlinghttps://bugs.dragonflybsd.org/issues/27172014-08-22T12:36:50Zdclinkdevnexen@gmail.com
<p>In a similar way than OpenBSD, the numeric values overflows are checked.</p> DragonFlyBSD - Submit #2438 (Feedback): TRIM fixeshttps://bugs.dragonflybsd.org/issues/24382012-10-22T04:59:20ZAnonymous
<p>This patch is to fix bugs associated with TRIM.</p>
<p>If trim is on as a option, display that when typing "mount".</p>
<p>Change post-trim ffs_blkfree_cg() to use taskqueue_swi_mp and get mp token when modifying freemap.</p>
<p>Make sure TRIM works with softdep. Stash a copy of that vnode's mount point in the ufs inode so that if we are using softdep, we can get access to the mount point through the faked up inode (created in freeblocks). The original mount point path (ip->i_devvp->v_mount->mnt_flag) doesn't have the mount point options.</p>
<p>Tim</p> DragonFlyBSD - Submit #2098 (New): [PATCH] correct ath man page example (/usr/src/share/man/man4/...https://bugs.dragonflybsd.org/issues/20982011-06-29T04:12:50Znobody
<p>152c152<br />< wepmode on wepkey 0x8736639624 weptxkey 1 up<br />---<br /> > wepmode on wepkey 0x8736639624</p> DragonFlyBSD - Submit #1398 (In Progress): hdestroy(3) restricts hash key to point to malloc'ed s...https://bugs.dragonflybsd.org/issues/13982009-06-11T02:08:49ZAnonymous
<p>Salute.</p>
<p>hdestroy(3) frees the memory pointed to by the hash key. In other words it expects the user to always have malloc()'ed rather than used static allocation for the hash key. This doesn't apply to the data associated with the key.</p>
<p>Although POSIX standard doesn't say much on this particular topic:</p>
<ol>
<li>This is unnecessarily restrictive. If the user wants static allocation, we should allow this. If she wants dynamic then let <strong>her</strong> free the memory she malloc()'ed.</li>
<li>It is in conflict with the example code in the POSIX page. The code segfaults if you add an hdestroy() call in the end of it.</li>
<li>Programs that target other implementations may segfault in DragonFly (that'show I discovered it). AFAIK sunOS 5.10 and a recent glibc work fine, whereas {Net, Free, DragonFly}BSD all are affected because they share the same code. (One could argue that all programs written with the *BSD version in mind would<br />result in a memory leak. But still I think these programs (if any) should be fixed.)</li>
</ol>
<p>Any thoughts ?</p>
<p>Cheers,<br />Stathis</p> DragonFlyBSD - Submit #1192 (New): KKASSERTs in sys/kern/uipc_{msg,socket}.c are too stricthttps://bugs.dragonflybsd.org/issues/11922008-12-30T06:05:00Zrumcic
<p>The code for nfs root mounts does not use kmalloc-ed space for some vars, while<br />some KKASSERTs in the mentioned files only check for the supplied pointers if<br />they were kmalloc-ed or not.<br />The attached patch adds a check if the supplied pointers are not in user stack<br />(if they are in kernel stack) ... since kmalloc-ed space also resides in the<br />addresses not in user stack, maybe kva_p should be removed (is it used<br />anywhere else?)?<br />-- <br />Regards,<br />Rumko</p>