{"push_id":657161540,"size":1,"distinct_size":0,"ref":"refs/heads/grsec-3.2","head":"3e41f672cd5392f5d260cafa75913ab6e9699d9e","before":"24acb983d24ecb5d80196274660e2c55a9fc8ccf","commits":[{"sha":"3e41f672cd5392f5d260cafa75913ab6e9699d9e","author":{"email":"be467f0e1be1cd5d65704bcad86a587c7f8efd36@grsecurity.net","name":"Brad Spengler"},"message":"grsec: Apply grsecurity-3.1-3.2.68-201505072053.patch\n\ncommit 813308a7db37854542b4452ef7808ee38f25f1d2\nMerge: 9d08c90 f1cc348\nAuthor: Brad Spengler <spender@grsecurity.net>\nDate:   Thu May 7 18:28:38 2015 -0400\n\n    Merge branch 'pax-stable' into grsec-stable\n\ncommit f1cc348c69051d8a58237bdbb3fdb771c0d2a4ad\nAuthor: Brad Spengler <spender@grsecurity.net>\nDate:   Thu May 7 18:28:04 2015 -0400\n\n    Update to pax-linux-3.2.68-test173.patch:\n    - worked around a gcc induced intentional overflow in the bunzip decompressor, reported by Martin Filo (https://bugs.gentoo.org/show_bug.cgi?id=548508)\n    - F_SETPIPE_SZ handling ignored pipe_min_size and could trigger the size overflow instrumentation, reported by minipli\n    - fixed an integer signedness mixup in a parameter of semop and semtimedop, by minipli\n\n fs/pipe.c                |   13 ++++++++-----\n include/linux/compat.h   |    2 +-\n include/linux/syscalls.h |    4 ++--\n ipc/compat.c             |    2 +-\n ipc/sem.c                |    4 ++--\n lib/decompress_bunzip2.c |    3 ++-\n 6 files changed, 16 insertions(+), 12 deletions(-)\n\ncommit 9d08c9084b135cacccd2fe9ea0ca7e41ae6a8d84\nAuthor: Brad Spengler <spender@grsecurity.net>\nDate:   Thu May 7 18:01:36 2015 -0400\n\n    Even though in the history of autoconfig it has never tripped anyone\n    up under realistic use cases (e.g. nobody starts a config, enables\n    only CONFIG_GRKERNSEC, then exits menuconfig, then loads it back up\n    and tries to apply an autoconfig setting) explicitly mention that you\n    cannot do it and expect the autoconfig to work.  Due to how the Kbuild\n    system works, we can't apply defaults and also allow them to be modified\n    via custom settings -- if they're 'select'ed then they can't be modified,\n    and using 'select' violates any dependencies that may exist.  Therefore\n    we have to resort to using 'default', which after a user has already chosen\n    all the settings by virtue of enabling CONFIG_GRKERNSEC and then saving their\n    complete kernel config, cannot have any effect as the options have now all\n    been chosen and there's no 'default' applicable.\n\n security/Kconfig |    5 +++++\n 1 files changed, 5 insertions(+), 0 deletions(-)\n\nSignature-tree: 1339c434bf9c2053ee4438f3d36386e60bc080bb","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/3e41f672cd5392f5d260cafa75913ab6e9699d9e"}]}