In message <1168362231.6054.38.camel@xxxxxxxxxxxxxxxxxx>, Trond Myklebust writes: > I'm saying that at the very least it should not Oops in these > situations. As to whether or not they are something you want to handle > more gracefully, that is up to you, but Oopses are definitely a > showstopper. > > Trond I totally agree: oopsing is unacceptable. Instead Unionfs should handle it more gracefully than an oops. Now, a lot of this "scare" in the past couple of days had been the result of our documentation, which was intended to prevent people from mucking with the lower f/s. As Jeff said already yesterday, many of the possible oopses were already fixed, and you'll be hard pressed right now to be able to tickle more oopses. But, to be sure, we'll run more tests, and fix whatever else we can. Erez. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
