Hadrien Grasland <grasland@xxxxxxxxxxxx> writes: > I've never patched a kernel module before, but I assume it should > involve something like getting a copy of my kernel's sources, applying > the patch, rebuilding the relevant module, unloading the old module and > putting the new one in its place, right? You can also build the kernel and directly boot the resulting binary in a qemu vm. You can find many tutorials for this online: http://ncmiller.github.io/2016/05/14/linux-and-qemu.html https://www.collabora.com/news-and-blog/blog/2017/01/16/setting-up-qemu-kvm-for-kernel-development/ etc I'd also suggest using the bridge setup described here so you can access your host network from the vm transparently. http://blog.elastocloud.org/2015/07/qemukvm-bridged-network-with-tap.html Depending on your experience you might find this easier. -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
