Date: Fri, 28 May 2021 15:41:39 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 168298] VirtualBox using AIO on a zvol crashes Message-ID: <bug-168298-27103-lsn7BJiYR4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-168298-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-168298-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298 Guido Falsi <madpilot@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madpilot@FreeBSD.org --- Comment #51 from Guido Falsi <madpilot@FreeBSD.org> --- (In reply to Tom Rushworth from comment #50) I sent a small patch to their mailing list (seems to be the only available channel). My intention was (and maybe I'll still try) to package some FreeBSD port patches and push them upstream. you can read the whole exchange here: https://www.virtualbox.org/pipermail/vbox-dev/2021-March/015627.html (follow the thread) I'll cite here this small exchange: ---- > BTW is there some review tool you are using? Sending patches as > attachments via mailing list does not look very efficient for review. And yet, the Linux kernel managed 15,477 commits between 5.10 and 5.11, for an average around 170 per day, the vast majority of which weren't attachments but up in the main body of the email. ---- So it looks like, since the linux kernel does things this way(do they really? Never coded for linux kernel), it's got to be good for everyone. I then sent my small patch inline and got no further feedback. Personally I'm not looking forward to further interfacing with them, and will do it only for patches I created. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-168298-27103-lsn7BJiYR4>