Quoting Christoph Lameter (cl@xxxxxxxxx): > Ok 4.0-rc1 is out and this patch has been sitting here for a couple of > weeks without comment after an intensive discussion about the RFCs. > > Since there were no objections: Is there any chance to get this into -next > somehow? Andrew Morgan and Andy Lutomirski appear to have a similar concern but competing ideas on how to address them. We need them to agree on an approach. The core concern for amorgan is that an unprivileged user not be able to cause a privileged program to run in a way that it fails to drop privilege before running unprivileged-user-provided code. Andy Lutomirski's concern is simply that code which is currently doing the right thing to drop privilege not be run in a way that it thinks it is dropping privilege, but in fact is not. (Please correct me where I've mis-spoken or misunderstood) Since your desire is precisely for a mode where dropping privilege works as usual, but exec then re-gains some or all of that privilege, we need to either agree on a way to enter that mode that ordinary use caes can't be tricked into using, or find a way for legacy users to be tpiped off as to what's going on (without having to be re-written) -serge -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
