> On 12. Dec 2024, at 20.27, Kai Mäkisara (Kolumbus) <kai.makisara@xxxxxxxxxxx> wrote: > > While doing some detective work, I found a serious problem. So, please hold these patches again. > More about the reason below. ... > The problem is that no driver options for the device can be set before something has > been done to clear the blocking. For instance, the stinit tool is a recommended method > to set the options based on a configuration file, but it fails. > > Note that this problem has existed since commit 9604eea5bd3ae1fa3c098294f4fc29ad687141ea > (for version 6.6) that added recognition of POR UA as an additional method to detect > resets. Nobody seems to have noticed this problem in the "real world". (Using > was_reset was not problematic because it caught only resets initiated by the midlevel.) > > A solution might be to add some more ioctls to the list of allowed commands. > But I must think about this a little more. This does not seem to be a promising direction. I think it is better to see that the first test_ready() (called from st_open()) does not set the pos_unknown flag. If there are no objections, I will add this to the next version of the patches. The justification for this solution is that just after the device is detected by st, the position of the tape is known to the user and there is no need to prevent, for instance, writing to the tape.
