From: Greg KH <greg@kroah.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening][RFC PATCH v2 01/12] x86: add PAX_REFCOUNT support
Date: Thu, 17 Dec 2015 10:11:43 -0800 [thread overview]
Message-ID: <20151217181143.GA18680@kroah.com> (raw)
In-Reply-To: <CAEXv5_j8Bo9u1WUTH2QwYwye+j9270S+rgzjnsvcbojrYW7sfQ@mail.gmail.com>
On Thu, Dec 17, 2015 at 12:55:44PM -0500, David Windsor wrote:
> On Thu, Dec 17, 2015 at 12:16 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Thu, Dec 17, 2015 at 09:57:39AM -0500, David Windsor wrote:
> >> --- a/include/linux/sched.h
> >> +++ b/include/linux/sched.h
> >> @@ -749,6 +749,17 @@ struct signal_struct {
> >> #ifdef CONFIG_TASKSTATS
> >> struct taskstats *stats;
> >> #endif
> >> +
> >> +#ifdef CONFIG_GRKERNSEC
> >> + u32 curr_ip;
> >> + u32 saved_ip;
> >> + u32 gr_saddr;
> >> + u32 gr_daddr;
> >> + u16 gr_sport;
> >> + u16 gr_dport;
> >> + u8 used_accept:1;
> >> +#endif
> >> +
> >
> > Why is this here in this patch?
> >
>
> For pax_report_refcount_overflow in fs/exec.c:
>
> 1754: if (current->signal->curr_ip)
>
> This is guarded by CONFIG_PAX_REFCOUNT, which, as it stands, should
> depend on CONFIG_GRKERNSEC. The Kconfig options likely need to
> change, depending on the naming of these features moving forward.
But that has nothing to do with this patch, and as that config option
isn't present in the kernel at this point in time, this change is not
needed at all, right?
Or am I missing something?
thanks,
greg k-h
next prev parent reply other threads:[~2015-12-17 18:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 14:57 [kernel-hardening][RFC PATCH v2 00/12] Add PAX_REFCOUNT overflow protection David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 01/12] x86: add PAX_REFCOUNT support David Windsor
2015-12-17 17:16 ` Greg KH
2015-12-17 17:55 ` David Windsor
2015-12-17 18:11 ` Greg KH [this message]
2015-12-17 18:23 ` David Windsor
2015-12-17 19:46 ` Greg KH
2015-12-18 2:59 ` David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 02/12] percpu_ref: decrease per-CPU refcount bias David Windsor
2015-12-17 20:56 ` Kees Cook
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 03/12] kernel: opt out of PAX_REFCOUNT protection David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 04/12] mm: " David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 05/12] fs: " David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 06/12] net: " David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 07/12] security: " David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 08/12] drivers: opt out of PAX_REFCOUNT protection (1 of 2) David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 09/12] drivers: opt out of PAX_REFCOUNT protection (2 " David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 10/12] pax: opt out of PAX_REFCOUNT protection David Windsor
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 11/12] security: add Kconfig options for PAX_REFCOUNT David Windsor
2015-12-17 20:53 ` Kees Cook
2015-12-17 14:57 ` [kernel-hardening][RFC PATCH v2 12/12] lkdtm: add test for atomic_t underflow/overflow David Windsor
2015-12-17 20:55 ` [kernel-hardening][RFC PATCH v2 00/12] Add PAX_REFCOUNT overflow protection Kees Cook
2016-01-19 19:07 ` Kees Cook
2016-01-20 13:11 ` David Windsor
2016-02-02 11:33 ` David Windsor
2016-02-04 18:19 ` Kees Cook
2016-04-21 20:37 ` Kees Cook
2016-04-28 12:16 ` [kernel-hardening][RFC PATCH 0/5] " David Windsor
2016-01-20 20:57 ` [kernel-hardening][RFC PATCH v2 00/12] " Yves-Alexis Perez
2016-01-20 23:39 ` Kees Cook
2016-01-21 1:01 ` Daniel Micay
2016-01-21 12:45 ` Yves-Alexis Perez
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=20151217181143.GA18680@kroah.com \
--to=greg@kroah.com \
--cc=kernel-hardening@lists.openwall.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.