Pavel Machek <pavel@xxxxxx> writes: >> >> I certainly am not interested in debugging or maintaining the stacking >> >> inode code that would be necessary to close this theoretical corner >> >> case. There are much more real bugs that need attention. >> > >> > But if we can get trivial 10-liner, that should be acceptable, right? >> >> How many linux shell scripts and other applications that use /dev/fd/N >> or /proc/self/fd/N will you be breaking? > > Zero. (Well unless someone is exploiting it in wild). There are other differences like different offsets etc that may matter. >> Closing a theoretical security hole at the expense of breaking real >> applications is a show stopper. > > I don't plan to remove /proc/*/fd; but I would like it to behave like > dup(). > > (I still hope some security team does work for me :-). Seriously turning this into dup is about 20 lines of code in follow link. Just look at the open intent in the nameidata. nfs should have an exampled of using the open intent somewhere. I bet you will get a lot more traction and discussion if you write a basic mostly working version of the patch. Eric -- 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
