No subject


Wed Aug 4 16:07:55 CEST 2010


vfs level, which somehow leads to sock_ioctl() call which in turn fails
because it isn't supposed to be called for vfs. This could mean that
filp->f_op->unlocked_ioctl() is set incorrectly to sock_ioctl. And this
means that actual problem is somewhere in kernel, but is rises only
after some magic ioctl call from drbdadm.

Can anybody from DRBD devs look at this issue?

Best,
Vladislav


More information about the drbd-user mailing list