{"push_id":1403663839,"size":2,"distinct_size":2,"ref":"refs/heads/cm-14.1","head":"eb6b05ba9bb5c6b987e0b50418147442c08ae4ad","before":"99c0ff198e5e17a68091fd5e5534697bd99362e1","commits":[{"sha":"3c2c5710b13a787d86bd6bdd5c62da58f0c0ea5d","author":{"name":"Andrey Vagin","email":"94e0a78365855762efb4dc69e66e1b9e1db47c59@openvz.org"},"message":"BACKPORT: signal: allow to send any siginfo to itself\n\nThe idea is simple.  We need to get the siginfo for each signal on\ncheckpointing dump, and then return it back on restore.\n\nThe first problem is that the kernel doesn't report complete siginfos to\nuserspace.  In a signal handler the kernel strips SI_CODE from siginfo.\nWhen a siginfo is received from signalfd, it has a different format with\nfixed sizes of fields.  The interface of signalfd was extended.  If a\nsignalfd is created with the flag SFD_RAW, it returns siginfo in a raw\nformat.\n\nrt_sigqueueinfo looks suitable for restoring signals, but it can't send\nsiginfo with a positive si_code, because these codes are reserved for\nthe kernel.  In the real world each person has right to do anything with\nhimself, so I think a process should able to send any siginfo to itself.\n\nThis patch:\n\nThe kernel prevents sending of siginfo with positive si_code, because\nthese codes are reserved for kernel.  I think we can allow a task to\nsend such a siginfo to itself.  This operation should not be dangerous.\n\nThis functionality is required for restoring signals in\ncheckpoint/restart.\n\nChange-Id: I2fb882e2a8b678a9a4717df3bdcd7f8218a605c9\nSigned-off-by: Andrey Vagin <avagin@openvz.org>\nCc: Serge Hallyn <serge.hallyn@canonical.com>\nCc: \"Eric W. Biederman\" <ebiederm@xmission.com>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Michael Kerrisk <mtk.manpages@gmail.com>\nCc: Pavel Emelyanov <xemul@parallels.com>\nCc: Cyrill Gorcunov <gorcunov@openvz.org>\nCc: Michael Kerrisk <mtk.manpages@gmail.com>\nReviewed-by: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/zeroblade1984/android_kernel_lge_g3/commits/3c2c5710b13a787d86bd6bdd5c62da58f0c0ea5d"},{"sha":"eb6b05ba9bb5c6b987e0b50418147442c08ae4ad","author":{"name":"Liam Mark","email":"db460ca79fa3459eb33cde4b2632331670821bd4@codeaurora.org"},"message":"ion: disable system contig heap\n\nA malicious application can take advantage of the ION contig heap to\ncreate a specific memory chunk size to exercise a rowhammer attack on the\nphysical hardware.\nSo remove support for the ION contig heap.\n\nChange-Id: I9cb454cebb74df291479cecc3533d2c684363f77\nSigned-off-by: Liam Mark <lmark@codeaurora.org>\nSigned-off-by: Prakash Gupta <guptap@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/zeroblade1984/android_kernel_lge_g3/commits/eb6b05ba9bb5c6b987e0b50418147442c08ae4ad"}]}
{"actor":{"display_login":"zeroblade1984"}}