On Thu, Sep 01, 2022 at 11:26:10AM +0800, Ming Lei wrote:
On Wed, Aug 31, 2022 at 04:06:16PM +0100, Richard W.M. Jones wrote:
I have also added the changes to Fedora:
https://koji.fedoraproject.org/koji/taskinfo?taskID=91468555
Please consider becoming a Fedora packager so you can comaintain this package.
OK, is there any guide about how to be a Fedora packager?
You will need to follow the steps here: https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package...
On the subject of the kernel issue, I have been running builds and git clones in a loop for many hours on a local (virtio-scsi) filesystem, and I have *not* seen the kernel memory corruption problem happening.
I will go back to testing ublk again to see if the kernel memory corruption bug is reproducible.
I am also running xfstests on both ublk and nbd, and compares results from the two.
I hit this issue again last night (see other email for dmesg output). I had a git clone and a large build looping in parallel on the NBD disk for 12+ hours. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v