[dropping microblaze and roland] On Fri, 2011-05-13 at 15:18 +0200, Ingo Molnar wrote: > * Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > > On Fri, 2011-05-13 at 14:54 +0200, Ingo Molnar wrote: > > > I think the sanest semantics is to run all active callbacks as well. > > > > > > For example if this is used for three stacked security policies - as if 3 LSM > > > modules were stacked at once. We'd call all three, and we'd determine that at > > > least one failed - and we'd return a failure. > > > > But that only works for boolean functions where you can return the > > multi-bit-or of the result. What if you need to return the specific > > error code. > > Do you mean that one filter returns -EINVAL while the other -EACCES? > > Seems like a non-problem to me, we'd return the first nonzero value. Sounds so easy! Why haven't LSMs stacked already? Because what happens if one of these hooks did something stateful? Lets say on open, hook #1 returns EPERM. hook #2 allocates memory. The open is going to fail and hooks #2 is never going to get the close() which should have freed the allocation. If you can be completely stateless its easier, but there's a reason that stacking security modules is hard. Serge has tried in the past and both dhowells and casey schaufler are working on it right now. Stacking is never as easy as it sounds :) -Eric
