James Morris wrote: > On Wed, 4 Oct 2006, [EMAIL PROTECTED] wrote: > >>This patchset includes an update to the NetLabel/secid-reconciliation patch, >>replacing my "v3" patch from earlier this week, and a bugfix patch to cure a >>race condition found during testing this week. The bugfix patch does not >>rely on the secid patches and should be merged regardless as it fixes a bug >>which has been around since the very first NetLabel patches (not sure why I >>didn't see this sooner). > > So, patch 2/2 should go in on it's own against upstream? If so, in 5B > future, please post such patches separately.
Yes, please commit patch 2/2 regardless as it fixes a bug which is not dependent on any of the secid patches which are being discussed. My apologies for including it in the same patchset, I'll be sure to split it up next time. > As for the rest of the network labeling, please work together with Venkat > and the SELinux developers on a final patchset which meets all of the > design goals and has been tested, with policy which has been merged > upstream and is available via Fedora devel. Please keep the discussion > going, but ensure that the final patchset for review and merge > consideration is a complete set against the current git kernel coming from > one person. I'm trying :) When I posted the NetLabel secid support patch last week I asked Venkat if he could merge it with the main secid patchset (due to size and dependencies that seemed like the most reasonable course of action). For reasons I'm not aware of he chose not to. As a result I keep posting updated patches backed against Venkat's latest and incorporating the latest feedback. Venkat, can you please merge the latest my latest NetLabel secid support patch in with your next release? If not, would you have a problem if I pushed out a patchset which included your latest patches with the NetLabel secid support patch and we used this patchset as the basis for future work? -- paul moore linux security @ hp - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
