From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Cc: sfjro@users.sourceforge.net
Subject: [gentoo-hardened] Re: aufs2 Monday GIT release
Date: Fri, 28 May 2010 14:16:24 +0200 [thread overview]
Message-ID: <4BFFB418.801@gentoo.org> (raw)
In-Reply-To: <11262.1274761932@jrobl>
[-- Attachment #1.1: Type: text/plain, Size: 1777 bytes --]
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@users.sourceforge.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
[-- Attachment #1.2: a.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 2024 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next parent reply other threads:[~2010-05-28 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26440.1274664907@jrobl>
[not found] ` <4BFA856B.5090203@gmx.de>
[not found] ` <11262.1274761932@jrobl>
2010-05-28 12:16 ` Thomas Sachau [this message]
2010-05-28 12:35 ` [gentoo-hardened] Re: aufs2 Monday GIT release pageexec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFFB418.801@gentoo.org \
--to=tommy@gentoo.org \
--cc=gentoo-hardened@lists.gentoo.org \
--cc=sfjro@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox