Daniel Walker wrote:
> From a reviews perspective what I would want is each set of changes,
> file system, networking, arch, etc split into separate patches. For
> example you have a number of patches just adding header files. You could
> merge the header file with the hook additions. Then you have a natural
> code split up which should be easier to review..
Filesystem part to fsdevel, socket operation part to netdev. That's OK.
But I wonder where to post the rest part.
Since the patches for passing "struct vfsmount" to LSM has been rejected,
TOMOYO has been unable to use LSM.
Thus, I proposed this patch set as a non-LSM version, but it bothers me
where to post this patch. If you know, please teach me where to post.
> > --- linux-2.6.25-rc8-mm1.orig/include/linux/init_task.h
> > +++ linux-2.6.25-rc8-mm1/include/linux/init_task.h
> > @@ -197,6 +197,10 @@ extern struct group_info init_groups;
> > INIT_IDS \
> > INIT_TRACE_IRQFLAGS \
> > INIT_LOCKDEP \
> > + /***** TOMOYO Linux start. *****/ \
> > + .domain_info = &KERNEL_DOMAIN, \
> > + .tomoyo_flags = 0, \
> > + /***** TOMOYO Linux end. *****/ \
> > }
>
> ifdef's ?
Or security_initcall()?
> > @@ -1278,6 +1283,10 @@ struct task_struct {
> > int latency_record_count;
> > struct latency_record latency_record[LT_SAVECOUNT];
> > #endif
> > + /***** TOMOYO Linux start. *****/
> > + struct domain_info *domain_info;
> > + u32 tomoyo_flags;
> > + /***** TOMOYO Linux end. *****/
> > };
>
> ifdefs?
>
I see.
Thank you.
--
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
