[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Oct 2016 17:01:15 +0000
From: "Reshetova, Elena" <elena.reshetova@...el.com>
To: Colin Vidal <colin@...dal.org>, "kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>
Subject: RE: self introduction
> Yes, just in our patch series we only made implementation for x86.
> But if you look into Grsecurity/PaX patches, it has support for others
> implemented.
>OK, got it! Thanks for this clarification.
>So, I will try to start to port PAX_REFCOUNT arm-specific features to hardened_atomic_on_next, and keep you in touch. Is there a deadline?
>(4.10 / 5.0 merge window?)
I don't think we have any particular deadline in mind: getting it in the upstream and making it behaving correctly is more of a priority.
>Just to be sure, the patch [1] and documentation [2] of PaX are still up-to-date, or there is another references I missed?
I don't think there are any other significant references. Where we functionaly deviate from PaX/Grsecurity, we documented it in commit messages (so far only on percpu refcount thing) .
Best Regards,
Elena.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
