Skip to contentSkip to conversation

Module stacking next steps

DISCUSSION James Morris 4 participants 6 messages Apr 30, 2015 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 4 lines · Casey Schaufler

James, do you want to take the module stacking changes in through the security tree? Are there remaining objections or concerns? What procedure would you like to follow?

What's the overall consensus on this -- do people generally see it as useful and necessary, and is it ready to go in?

Any objections or concerns?

Signature · 2 lines
James Morris
<[email protected]>
#2 lore raw
Quoted 9 lines · James Morris
Quoted 4 lines · Casey Schaufler

James, do you want to take the module stacking changes in through the security tree? Are there remaining objections or concerns? What procedure would you like to follow?

What's the overall consensus on this -- do people generally see it as useful and necessary, and is it ready to go in?

At the very worst, I see it as a very nice clean up.

At best, I see it as extremely useful for the things I want to do, with various "minor" LSM working together.

Quoted 1 line

Any objections or concerns?

As far as I'm concerned, I'm very happy with it.

Thanks!

-Kees

Signature · 1 line
Kees Cook                                            @outflux.net
#3 lore raw
In reply to James Morris
Quoted 12 lines · James Morris
Quoted 4 lines · Casey Schaufler

James, do you want to take the module stacking changes in through the security tree? Are there remaining objections or concerns? What procedure would you like to follow?

What's the overall consensus on this -- do people generally see it as useful and necessary, and is it ready to go in?

Any objections or concerns?

No objections, and I know there are several people interested in seeing this land.

I am happy with the code, and my only concerns lie with things that this explicitly doesn't support yet (ie. larger lsm stacking, secids, ...)

#4 lore raw
Quoted 11 lines · John Johansen
Quoted 10 lines · James Morris
Quoted 4 lines · Casey Schaufler

James, do you want to take the module stacking changes in through the security tree? Are there remaining objections or concerns? What procedure would you like to follow?

What's the overall consensus on this -- do people generally see it as useful and necessary, and is it ready to go in?

Quoted 7 lines
Quoted 2 lines

Any objections or concerns?

No objections, and I know there are several people interested in seeing this land.

I am happy with the code, and my only concerns lie with things that this explicitly doesn't support yet (ie. larger lsm stacking, secids, ...)

Ok, Casey, please send an updated final version for everyone to check.

Signature · 2 lines
James Morris
<[email protected]>
#5 lore raw
Quoted 11 lines · James Morris
Quoted 9 lines · John Johansen
Quoted 8 lines · James Morris
Quoted 3 lines · Casey Schaufler

James, do you want to take the module stacking changes in through the security tree? Are there remaining objections or concerns? What procedure would you like to follow?

What's the overall consensus on this -- do people generally see it as useful and necessary, and is it ready to go in?

Quoted 8 lines
Quoted 7 lines
Quoted 2 lines

Any objections or concerns?

No objections, and I know there are several people interested in seeing this land.

I am happy with the code, and my only concerns lie with things that this explicitly doesn't support yet (ie. larger lsm stacking, secids, ...)

Ok, Casey, please send an updated final version for everyone to check.

Are you planning to update security-next soon? I think that it will be easier for everyone if I base it on the 4.1-rc than the 4.0-rc. Alternatively, I could base it on 4.0. I can do any of 'em, but I'd hate to have to do it more often than I have to.

#6 lore raw
Quoted 17 lines · Casey Schaufler
Quoted 16 lines · James Morris
Quoted 14 lines · John Johansen
Quoted 10 lines · James Morris
Quoted 3 lines · Casey Schaufler

James, do you want to take the module stacking changes in through the security tree? Are there remaining objections or concerns? What procedure would you like to follow?

What's the overall consensus on this -- do people generally see it as useful and necessary, and is it ready to go in?

Any objections or concerns?

No objections, and I know there are several people interested in seeing this land.

Quoted 7 lines
Quoted 3 lines
Quoted 2 lines

I am happy with the code, and my only concerns lie with things that this explicitly doesn't support yet (ie. larger lsm stacking, secids, ...)

Ok, Casey, please send an updated final version for everyone to check.

Are you planning to update security-next soon? I think that it will be easier for everyone if I base it on the 4.1-rc than the 4.0-rc. Alternatively, I could base it on 4.0. I can do any of 'em, but I'd hate to have to do it more often than I have to.

Whoops! I read mail addressed directly to me before I read what goes just to lists. I see that security-next is updated. I will have the update ready as quickly as possible. Thank you.