Applied, thanks.
> And then kernel mode fault at 0x5a5a5a5e
Can you get a stack trace from that crash?
> Just before the crash it warns about winch_interrupt : read failed,
> errno = 9 fd 57 is losing SIGWINCH support
This looks different. Is it consistently the same file descriptor? If so,
put a breakpoint on close and see who's closing it who isn't supposed to.
> @@ -863,6 +863,7 @@
> return(-EFAULT);
> return(0);
> }
> + return -ENOTTY;
> }
I did a check of some of the other block drivers, and they mostly seem to
do -EINVAL rather than -ENOTTY. There was an oddball -ENOSYS, but I guess
I'll stick with -EINVAL.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/