Comment 1 for bug 48731

Revision history for this message
In , Graham Knap (graham-knap-rogers) wrote : This printk was introduced in Linux 2.6.10

It looks like the kernel code change that made this problem visible
occurred in 2.6.10. I've attached part of a diff between "sg.c" of
Linux 2.6.9 versus 2.6.10.

Interestingly, it appears that the diagnostic message is the only thing
that was added. You can see that the code does not alter any variables,
etc.

So the question remains: is this printk erroneous... or does it
correctly identify a bug in cdparanoia?

-- graham