{"push_id":556075498,"size":4,"distinct_size":4,"ref":"refs/heads/code_blue-l-beta","head":"c4bacbf4184aea02bc6cf9c2646b720253805705","before":"f5a4590b5aa7c5950a29f9795b4b60947fd83ce2","commits":[{"sha":"458ba52962d58351942f5af320a230c9cc9ed910","author":{"email":"88a1d58bf22a647dce58dd91f9595600dceabba9@redhat.com","name":"Paul Moore"},"message":"selinux: correctly label /proc inodes in use before the policy is loaded\n\ncommit f64410ec665479d7b4b77b7519e814253ed0f686 upstream.\n\nThis patch is based on an earlier patch by Eric Paris, he describes\nthe problem below:\n\n  \"If an inode is accessed before policy load it will get placed on a\n   list of inodes to be initialized after policy load.  After policy\n   load we call inode_doinit() which calls inode_doinit_with_dentry()\n   on all inodes accessed before policy load.  In the case of inodes\n   in procfs that means we'll end up at the bottom where it does:\n\n     /* Default to the fs superblock SID. */\n     isec->sid = sbsec->sid;\n\n     if ((sbsec->flags & SE_SBPROC) && !S_ISLNK(inode->i_mode)) {\n             if (opt_dentry) {\n                     isec->sclass = inode_mode_to_security_class(...)\n                     rc = selinux_proc_get_sid(opt_dentry,\n                                               isec->sclass,\n                                               &sid);\n                     if (rc)\n                             goto out_unlock;\n                     isec->sid = sid;\n             }\n     }\n\n   Since opt_dentry is null, we'll never call selinux_proc_get_sid()\n   and will leave the inode labeled with the label on the superblock.\n   I believe a fix would be to mimic the behavior of xattrs.  Look\n   for an alias of the inode.  If it can't be found, just leave the\n   inode uninitialized (and pick it up later) if it can be found, we\n   should be able to call selinux_proc_get_sid() ...\"\n\nOn a system exhibiting this problem, you will notice a lot of files in\n/proc with the generic \"proc_t\" type (at least the ones that were\naccessed early in the boot), for example:\n\n   # ls -Z /proc/sys/kernel/shmmax | awk '{ print $4 \" \" $5 }'\n   system_u:object_r:proc_t:s0 /proc/sys/kernel/shmmax\n\nHowever, with this patch in place we see the expected result:\n\n   # ls -Z /proc/sys/kernel/shmmax | awk '{ print $4 \" \" $5 }'\n   system_u:object_r:sysctl_kernel_t:s0 /proc/sys/kernel/shmmax\n\nCc: Eric Paris <eparis@redhat.com>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nAcked-by: Eric Paris <eparis@redhat.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/engstk/hammerhead-5.0/commits/458ba52962d58351942f5af320a230c9cc9ed910"},{"sha":"053815b8cf6590efe8b9cedb6412fba2850c8b2b","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"msm: bam_dmux: Reduce debug logs to avoid watchdog bite\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/engstk/hammerhead-5.0/commits/053815b8cf6590efe8b9cedb6412fba2850c8b2b"},{"sha":"23e90c8916164e9c1d6479b8a6399d3051063ffc","author":{"email":"d316c38b3127db4a8d19f369f757269f344aa63c@codeaurora.org","name":"Syed Rameez Mustafa"},"message":"lib: spinlock_debug: increase spin dump timeout to one second\n\nIncrease spin dump timeout so that it is back in sync with the\nupstream value.\n\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>\n\nConflicts:\n\tlib/spinlock_debug.c","distinct":true,"url":"https://api.github.com/repos/engstk/hammerhead-5.0/commits/23e90c8916164e9c1d6479b8a6399d3051063ffc"},{"sha":"c4bacbf4184aea02bc6cf9c2646b720253805705","author":{"email":"743c2818a341d71b99ed2b566f9f80c2fc288f93@canonical.com","name":"Maarten Lankhorst"},"message":"arch: Make __mutex_fastpath_lock_retval return whether fastpath succeeded or not\n\nThis will allow me to call functions that have multiple\narguments if fastpath fails. This is required to support ticket\nmutexes, because they need to be able to pass an extra argument\nto the fail function.\n\nOriginally I duplicated the functions, by adding\n__mutex_fastpath_lock_retval_arg. This ended up being just a\nduplication of the existing function, so a way to test if\nfastpath was called ended up being better.\n\nThis also cleaned up the reservation mutex patch some by being\nable to call an atomic_set instead of atomic_xchg, and making it\neasier to detect if the wrong unlock function was previously\nused.\n\nSigned-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>\nAcked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nCc: dri-devel@lists.freedesktop.org\nCc: linaro-mm-sig@lists.linaro.org\nCc: robclark@gmail.com\nCc: rostedt@goodmis.org\nCc: daniel@ffwll.ch\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/20130620113105.4001.83929.stgit@patser\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/engstk/hammerhead-5.0/commits/c4bacbf4184aea02bc6cf9c2646b720253805705"}]}