On 6/29/25 4:26 AM, Uwe Kleine-K?nig wrote: > Hello Roland, > > On Sun, Jun 29, 2025 at 11:46:00AM +0200, Roland Sommer wrote: >> [correcting CC recipients] > > Huh, how did I manage that (rhetorical question)? Thanks > >>> Ahh, now that makes sense. pktsetup calls `/sbin/modprobe pktcdvd` >>> explicitly, the blacklist entry doesn't help for that. Without the >>> kernel module renamed, does the 2nd DVD-RAM result in the blocking >>> behaviour? >> >> Yes. > > OK, that makes sense. So udev does in this order: > > - auto-load the module (which is suppressed with the backlist entry) > - call blkid (which blocks if the module is loaded) > - call pktsetup (which loads the module even in presence of the > blacklist entry). > >>> Thanks for your report and helpful testing, >> >> You're welcome. This is the way how OSS should be treated (at least in >> my opinion). > > I fully agree, still this looks different in practise more often that > not :-\ > > I created > https://salsa.debian.org/kernel-team/linux/-/merge_requests/1564 now.
I tried removing pktcdvd not that long ago, but someone claimed they used it still... I haven't worked on it in decades. The original intent of it was to support the 32k packet writing devices. DVD-RAM doesn't need it, it was for cd-rw devices. IMHO it should just be killed with fire. -- Jens Axboe
