[gentoo-hardened] Re: aufs2 Monday GIT release

[Thomas Sachau]

Since this is a conflict between aufs2 and pax/grsec patches, i would like to see the view of the
pax team too. Below are the two mails from aufs2 upstream together with the latest patch, which does
workaround the problem and contains some additional comments.

Since he is not subscribed, please keep him in CC.

Am 25.05.2010 06:32, schrieb sfjro@×××××××××××××××××.net:
>
> "Tommy[D]":
>> just tried to compile aufs2-standalone against my local kernel sources, b=
>> ut get the attached failure
>> for 2.6.33. The kernel is a development kernel from Gentoo with additiona=
>> l pax and grsec patches.
>
> I found the pax and grsec patches declare members as 'const'.
> grsecurity-2.1.14-2.6.33.4-201005151340.patch
> pax-linux-2.6.33.4-test19.patch
>
> For instance,
>
>  struct address_space_operations {
> -	int (*writepage)(struct page *page, struct writeback_control *wbc);
> -	int (*readpage)(struct file *, struct page *);
> -	void (*sync_page)(struct page *);
> +	int (* const writepage)(struct page *page, struct writeback_control *wbc);
> +	int (* const readpage)(struct file *, struct page *);
> +	void (* const sync_page)(struct page *);
>
> It means setting writepage (and other members) is prohibited. But aufs
> sets them dynamically. I think this is the cause of your problem.
> I don't know whether making them 'const' is necessary or not.
>
>
> J. R. Okajima
>
> ------------------------------------------------------------------------------
>
>

and

>> If you really need to co-work aufs and grsec/pax, then this patch will
>> > solve the problem. But I don't think it a good approach.
> It was broken. Here is an updated one.
>
> J. R. Okajima
>


-- 
Thomas Sachau

Gentoo Linux Developer