| <?xml version="1.0" encoding="utf-8"?><manifest revision="267a0935f202464987ffa427cb204381b6d1ef2c"> |
| <notice>Your sources have been sync'd successfully.</notice> |
| <remote fetch="https://android.googlesource.com" name="aosp" review="https://android-review.googlesource.com"/> |
| <remote alias="cros" fetch="https://chromium.googlesource.com/" name="chromium"/> |
| <remote fetch="https://chromium.googlesource.com" name="cros" review="https://chromium-review.googlesource.com"/> |
| <default remote="cros" revision="refs/heads/master" sync-j="8"/> |
| <project name="aosp/platform/external/dbus-binding-generator" path="src/aosp/external/dbus-binding-generator" revision="bce0483dd09f592d6f9f989f0e34fc930d206810" upstream="refs/heads/master"/> |
| <project name="aosp/platform/external/libbrillo" path="src/aosp/external/libbrillo" revision="16c285d16813172eaacd12d3396df90a3894cbc5" upstream="refs/heads/master"/> |
| <project name="aosp/platform/external/libchrome" path="src/aosp/external/libchrome" revision="e637cea7d02ce79682ccf4c675a7661809ca4466" upstream="refs/heads/master"/> |
| <project name="aosp/platform/external/minijail" path="src/aosp/external/minijail" revision="472581ace012ae755f3136870bba8bdd5cdb8331" upstream="refs/heads/master"/> |
| <project name="aosp/platform/external/modp_b64" path="src/third_party/modp_b64" revision="99dc13926931cedfd2e4e582c33ef657d0645c5c" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/connectivity/apmanager" path="src/aosp/system/connectivity/apmanager" revision="b606f03ee5a4d7a5f5f78cc980a447f08d94f9df" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/connectivity/shill" path="src/aosp/system/connectivity/shill" revision="496f396f9178b2830a60e3f667321f7eae5c482c" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/firewalld" path="src/aosp/system/firewalld" revision="90c4a0d3a66a84270aa8a8b4d46a97e6172074e9" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/tpm" path="src/aosp/system/tpm" revision="a6f1627c725e3218305afb47a215dc1564d8103d" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/update_engine" path="src/aosp/system/update_engine" revision="696faf4dffebca4d15959251cf3fb88b0727d801" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/webservd" path="src/aosp/system/webservd" revision="b470b41a117a213f5b8cf2d7badcc208da001b72" upstream="refs/heads/master"/> |
| <project name="chromium/deps/libmtp" path="chromium/src/third_party/libmtp" revision="0680a2d0c4cec58f8163fe115de80cff8852fd8b" upstream="refs/heads/master"/> |
| <project name="chromium/src/third_party/hwcplus" revision="e66a31e54e12906e86dc59f95b458889f025c505" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="chromium/tools/depot_tools" revision="9d20675998f69ae543c3ebed4bcc14f748f3797e"/> |
| <project groups="minilayout,buildtools,labtools" name="chromiumos/chromite" path="chromite" revision="8f2c7dfd01585b97cf9e36c59a107defcf4056eb" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/manifest" path="manifest" revision="49ef9671d35ef92f1e2f0eea163ef17a4e167f12" upstream="refs/heads/master"/> |
| <project groups="minilayout" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="f382e8270e28ee4c47c60a06d5458e245cb3941d" upstream="refs/heads/master"/> |
| <project groups="minilayout,labtools" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="3f429bda54265f850711d4eeb1b5ac17dfbb0dd8" sync-c="true" upstream="refs/heads/master"/> |
| <project groups="minilayout,labtools" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="161edc9f4dddd54a867ae6ce521a32971ba48f30" upstream="refs/heads/master"/> |
| <project groups="minilayout,labtools" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="6b67343eb5c26cb57a9ab0a2ddff2d7733e13c56" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/assets" path="src/platform/assets" revision="5fc15dee29d1d967ccc46071a732d802d3b34655" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="547ee7b5c86235308527c0ddd5e43c1673e7fcf1" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/battery_updater" path="src/platform/battery_updater" revision="32463c6de8e8c98d4b1711937bc7678afc121a85" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bmpblk" path="src/platform/bmpblk" revision="563ac6b7db7e742045b02ed29cc5ecc81ff58531" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bootcache" path="src/platform/bootcache" revision="ebe3a0995e90026433ffc62b7aeed6cad1f28694" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/btsocket" path="src/platform/btsocket" revision="1b65449a647c99556511df30b8ab660b98acce7f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chameleon" path="src/platform/chameleon" revision="5d067bf2f813e81e2cf2b5f0db22c3307be37cea" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chromiumos-assets" path="src/platform/chromiumos-assets" revision="05ce8d3c59a2d8e765b3beb2e1a69e7fcf59e5ba" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="chromiumos/platform/crostestutils" path="src/platform/crostestutils" revision="0d4ff6c83c9f6ce674e49bf461f370ec77de6809" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools,labtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="d3b04f983508fe2644f765509062dadbf488ec5c" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="79e83cfe19fc05e764110b3bb9fea3fcc16dfb5f" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="338baee8d01efce080fd752c310c8e3700924798" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="c4df284b32558f631862f79c75fc03af4f5ca68a" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="fa0547a876bf0e1ac3740ea2a9cf8c7999acb87f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/ec" path="src/platform/ec" revision="db1b3b34c21530672118754e84ddbe879925542e" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/factory" path="src/platform/factory" revision="d849029e68d19d793d4c46b98f3ce2797104f3c0" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="312f06df6f921915f15f976f936eea335c51b236" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/firmware" path="src/platform/firmware" revision="70f79da7a3bd18c942fa65a6b21fea589bbb5516" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="e6d4280a6bd62ffca2d0bdeee177423b3fc5a223" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="9d27a36fdd3727d7fdebe96fd24013bc601a58df" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/glbench/images" path="src/platform2/glbench/images" revision="5fd5ce655833f65d46b1950bec4eedeb4e96959b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/go-seccomp" path="src/platform/go-seccomp" revision="0280326e5bd212fcfbe3696e113730045debae74" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/google-breakpad" path="src/third_party/breakpad" revision="67d5567177301d0c24303f26ad119ab7bd7fab40" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/imageloader" path="src/platform/imageloader" revision="d8088ed05a36d269ca82ce92eed99cde277c57e0" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="1a710721263b8b93ab49af6a6f749a778483f3df" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/inputcontrol" path="src/platform/inputcontrol" revision="ae0b15dc322bab9bf6d7c4fcd5f77d488766a275" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/jabra_vold" path="src/platform/jabra_vold" revision="5ee665e7c68856d3b6ce8bb0f610d43503e603af" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/libevdev" path="src/platform/libevdev" revision="6647f24f432fa0746dd9561cbe9e8e34fbe3bbd6" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/memento_softwareupdate" path="src/platform/memento_softwareupdate" revision="3c7204287bbc8f4341f546857216389bdff58e51" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/microbenchmark" path="src/platform/microbenchmark" revision="d5ea30febe406c5b486325dfae926564f3a46efd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/minigbm" path="src/platform/minigbm" revision="f9e7c4c8e91fb354abf714c7a5c89b4990814ff3" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/monitor_reconfig" path="src/platform/monitor_reconfig" revision="f022d19d84f232290b596beeb26347f62442e7eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="d6725baa03d7883d18b31e879cf0db23fad1b34b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtpd" path="src/platform/mtpd" revision="44148fe605b952132644f0d0e5ccea7cfcc6d6c8" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtplot" path="src/platform/mtplot" revision="5e4f631e633384751f582bd9db5f4d6eb2112494" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mttools" path="src/platform/mttools" revision="9efd0e1723cd45709bd0d34e8e7bbfd15967f0d5" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/punybench" path="src/platform/punybench" revision="5a230ee17756dc43ff732932dcb52899c06a4d09" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/system_api" path="src/platform/system_api" revision="c74bf51d2bc256adf09b6cfb2e353262fa43a736" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="1973ced7b023bdb4d095dff3e779bb4afacfe4f4" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_noise_filter" path="src/platform/touch_noise_filter" revision="6b0aba12a385f4d3a7a47641a3a919018032f6f8" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="3f379a2b8808a435dc14a333f3f7ad82e54e2511" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchbot" path="src/platform/touchbot" revision="75d8f1bfbbb3dfc870fcbc22f53cd16b66ac7f23" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touchpad-tests" path="src/platform/touchpad-tests" revision="d2e7d94a834b54511ca57e6359839f9ca86d6d04" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm" path="src/third_party/tpm" revision="0cba6cadd1bea1ce3717779201d594c4c9131dc2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tpm_lite" path="src/platform/tpm_lite" revision="066c7f963b3ef733716251b666e0af0afd03b4fe" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/trunks" path="src/platform/trunks" revision="92dbe8c9e7fcf8acf67805fd5e25e85aa371f673" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/uboot-env" path="src/platform/uboot-env" revision="108ebbfac4d13d11e1940216434c368384ee0c0b" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/platform/vboot" path="src/platform/vboot" revision="2d30a2f5b1c81eb61de4bf82180a910d45f22e81" upstream="refs/heads/master"/> |
| <project groups="buildtools" name="chromiumos/platform/vboot_reference" path="src/platform/vboot_reference" revision="1becb0dabecf6d15b0e7d88704fda86b3912be4c" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="3e4cf4867fff44491b4f4c294eee9c77b92d4440" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/wireless_automation" path="src/platform/wireless_automation" revision="d7177dbd464f2952e10309bf1eef56bb31a7f8ad" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/workarounds" path="src/platform/workarounds" revision="30cab56de921f5be2d24c2e83bcd4ad5631b2d9b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xf86-input-cmt" path="src/platform/xf86-input-cmt" revision="3f2ffc921952e57a4343463b0679d90b80b51fc7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="141199fa101370af0aed16a44f7122fea43f7c30" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="998fd7d7b667ecb7fe06a2112975d16d229bf0b6" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools,labtools" name="chromiumos/repohooks" path="src/repohooks" revision="fdbac8e95ef6153ab23370ea1586a86f462dbe5f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="305b2e610ce5d023aa8cda7adee571c5da8bcc0b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/android_mtdutils" path="src/third_party/android_mtdutils" revision="9bcfc3ee238f16925e9aaa4573129784ebb397e7" upstream="chromeos"/> |
| <project name="chromiumos/third_party/arm-trusted-firmware" path="src/third_party/arm-trusted-firmware" revision="a7e530331d7cf4b58618f0715e61b5a872176f07"> |
| <annotation name="branch-mode" value="create"/> |
| </project> |
| <project name="chromiumos/third_party/atheros" path="src/third_party/atheros" revision="52a5bdaa8930c14ee42518354de3e5ec09911c6b" upstream="refs/heads/master"/> |
| <project groups="buildtools,labtools" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="84ec4f482b7fd97199e5d2ef2e7f68f1c2127c97" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="58d9cf6e6ebbb1ce60e6da37943bb252b5c28557" upstream="refs/heads/chromeos-5.39"/> |
| <project name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="5ac54e8d3d305c2c6c7297e8e54d3cf7e4629b29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/broadcom" path="src/third_party/broadcom" revision="4070e7161f2f1a1a22027a744eb868500688f0b6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cbootimage" path="src/third_party/cbootimage" revision="b7d5b2d6a6dd05874d86ee900ff441d261f9034c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/chrontel" path="src/third_party/chrontel" revision="7bcd0328d0eeef6a0539bd0ba80cd9a545e6cf4a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="7abc4c7635624e8fdde4acde00784ad71f3fba81" upstream="refs/heads/chromeos-2016.05"/> |
| <project name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="9ba07035ed0acb28902cce826ea833cf531d57c1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cryptoc" path="src/third_party/cryptoc" revision="5319e836704fcf2df75c7425addebb89bb973714" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cypress-tools" path="src/third_party/cypress-tools" revision="043fba1c35f89cce95f804bf6d4f01cfc23a6c21" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/daisydog" path="src/third_party/daisydog" revision="3182aa85c087446e4358370549adc45db21ec124" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-cplusplus" path="src/third_party/dbus-c++" revision="f140c0aa430e1db1c0f31d23d3eb2397d47f209e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/dbus-spy" path="src/third_party/dbus-spy" revision="0e04421c73b24536de7fcc1886da469d8b7a2a41" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="chromiumos/third_party/dpkt" path="chromite/third_party/dpkt" revision="f5259728b1294412bee945df9708efba09ea9160"> |
| <annotation name="branch-mode" value="pin"/> |
| </project> |
| <project name="chromiumos/third_party/edk2" path="src/third_party/edk2" revision="0aa39d284043be61b5f1222afdffd39a5abaf3aa" upstream="refs/heads/chromeos-2014.04"/> |
| <project name="chromiumos/third_party/em100" path="src/third_party/em100" revision="6e60dbae5bf62cd0ffffb9fc5ca9ba93e831ee88" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/flashmap" path="src/third_party/flashmap" revision="aaaf66654dba797f152066df4d1dc4144b492c66" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/flashrom" path="src/third_party/flashrom" revision="d75cd67ac2c9e04c3e7722bb4d28a888ac9fa911" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gcc" path="src/third_party/gcc" revision="a2bc87ab8851051e765d60626a6997f63ddfe00e" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="chromiumos/third_party/gdata" path="chromite/third_party/gdata" revision="fe7e5c90a9827feb66ed446b2d297a1618b25272" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gdmwimax" path="src/third_party/gdmwimax" revision="e8236b4b2d66b1972e4f84955a238134acd7f6a1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gobi3k-sdk" path="src/third_party/gobi3k-sdk" revision="69702c400e274984a24d08fcaefe3952d5dcb36e" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/grub2" path="src/third_party/grub2" revision="df6034c59cb2d847f9e780cf2def30c5c9b8305f" upstream="refs/heads/master"/> |
| <project groups="labtools" name="chromiumos/third_party/hdctools" path="src/third_party/hdctools" revision="be00b142ca9d17a58520f0ee931c3a80871969b8" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="6fcb866534544ea8ce69c2134871cfcbdc1eb6d3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hwcplus-drm" path="src/third_party/hwcplus-drm" revision="7376a8da1c961115a61d7a3cb23bb13e4153583d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ibus-chewing" path="src/third_party/ibus-chewing/files" revision="7a9514a0844eb5eb90ab96f62484a6af9e4a0d6d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ibus-xkb-layouts" path="src/third_party/ibus-xkb-layouts/files" revision="6af015110aa92dc2eed88a9f704634c3eff53b14" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.8" revision="74c1be9358d02d760004bf7ff2cabc107aa071f4" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="9fcf599aaea72859c9097b2642edaa71cbb2337d" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="3b510eadd5076f614243362749ede0508b4c4bab" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="c40455bf67bbafd312542dbc91a85b1b1bc53437" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.4" revision="28dcf0381c5c0c96f8e3b8f692ffa3241916cb1a" upstream="refs/heads/chromeos-4.4"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="dceee6ef99b968fd11d9c6058448202db835bc0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libc-bench" path="src/third_party/libc-bench" revision="76793dd4b09191a78a78180012718e72d792717f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libdrm" path="src/third_party/libdrm" revision="a30fa998eb0ba2288017b4fd9f616bee81180f63" upstream="refs/heads/chromeos-2.4.66"/> |
| <project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="c4e2949edeed01ca3b810729a7af0d265c49629b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="a436c551cf226af66cdb3dd74ee3971d0b1dae04" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libresample" path="src/third_party/libresample" revision="cc9f20f439396b7d45e94b8301edd95d33f26a46" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libscrypt" path="src/third_party/libscrypt" revision="b45c53f9418a6eff2c8ed98703a55f96029304b1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libsigrok" path="src/third_party/libsigrok" revision="199fe31115c76231746f5953271795d58679561c" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrok-cli" path="src/third_party/sigrok-cli" revision="c9edfa218e5a5972531b6f4a3ece8d33a44ae1b5" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libsigrokdecode" path="src/third_party/libsigrokdecode" revision="3279c2825684c7009775b731d0a9e37815778282" upstream="refs/heads/chromeos"/> |
| <project name="chromiumos/third_party/libv4lplugins" path="src/third_party/libv4lplugins" revision="61eb2eceaed6f66a36aa9fc3ed2bd55b8aa3eafe" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/linux-firmware" path="src/third_party/linux-firmware" revision="13556f5f77128189571ecd2ffabd985ca837ff29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="7fea30a4ad5b7b4e99865afcee8b6bfd19ec8b03" upstream="refs/heads/chromeos-20150119"/> |
| <project name="chromiumos/third_party/marvell" path="src/third_party/marvell" revision="db05d126a42a1540a503a2e5b49c3746c03df77d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/memtest" path="src/third_party/memtest" revision="3d4be6e3bfd819856e38a82e35c206fec4551851" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/arc-mesa" revision="b2b27d09c1d7f694a37a80f7b04e4f79df557b1f" upstream="refs/heads/arc-11.3.0-pre1"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="6ef50efc1079e544d7fe912aba219e8907cb0cbd" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa-img" revision="129178893b2260df22db96327c5ca9c2ce7db046" upstream="refs/heads/mesa-img"/> |
| <project name="chromiumos/third_party/minifakedns" path="src/third_party/miniFakeDns" revision="6184bea119dea53da539727fe8c2a116f98cef24" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mmc-utils" path="src/third_party/mmc-utils" revision="bcc3e2e4246431be511be3959a11cd9733bedd29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="d759387adb6b4079241f7d1f2a145738acad929b" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/opencryptoki" path="src/third_party/opencryptoki" revision="b67690aeeb4174b2253db18a9c1b19eeb219a4ef" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ply-image" path="src/third_party/ply-image" revision="6cf4e4cd968bb72ade54e423e2b97eb3a80c6de9" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="chromiumos/third_party/pyelftools" path="chromite/third_party/pyelftools" revision="19b3e610c86fcadb837d252c794cb5e8008826ae" upstream="refs/heads/master-0.22"/> |
| <project name="chromiumos/third_party/rootdev" path="src/third_party/rootdev" revision="5d7d7ff513315abd103d0c95e92ae646c1a7688c" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/seabios" path="src/third_party/seabios" revision="3004147dd3707e600772ec6c5d37beac7f4b8eb4" upstream="refs/heads/chromeos-2014.11.03"/> |
| <project name="chromiumos/third_party/sysbios" path="src/third_party/sysbios" revision="33e1db34b8162de72a5e9bbbc44e6bce38978396" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegra-power-query" path="src/third_party/tegra-power-query" revision="66f1f0d949f4ca4836c1a65b622629205240e37a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegrastats" path="src/third_party/tegrastats" revision="1be161a89525d840e1f6d1f21b3f45645a7dedb3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="0c4b13bf15b8e5773b79e6317121fba5e97a154f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm-emulator" path="src/third_party/tpm-emulator" revision="310a21ef24ace14b4d6e8095172445494f54ff25" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tpm2" path="src/third_party/tpm2" revision="716a46a8f2e9516bd9ac64674a5811374f446792" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="416d30f74a9c1dc08b95b907d8b7e81edf6c9db0" upstream="refs/heads/master-0.3.13"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/files" revision="cc72f5c47c758892b0f41257b0dd441a506ffdcd" upstream="refs/heads/chromeos-v2013.06"/> |
| <project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/next" revision="b30f38206f17aa73cda0a2fdaf4dc705527315ba" upstream="refs/heads/chromeos-v2015.07-rc1"/> |
| <project name="chromiumos/third_party/whining" path="src/third_party/whining" revision="bcf721d62d6a4c4c162c63714371fa4349df53bc" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/xf86-video-armsoc" path="src/third_party/xf86-video-armsoc" revision="30370e9dbf7ba0e457ee7de297d2ad6c269a00be" upstream="refs/heads/master"/> |
| <project groups="minilayout,buildtools" name="external/swarming.client" path="chromite/third_party/swarming.client" revision="715861067a7cc8d20d2d629b6d76d796c004feb4"/> |
| <project name="linux-syscall-support" path="src/third_party/breakpad/src/third_party/lss" revision="9292030109847793f7a6689adac1ddafb412fe14"/> |
| <project name="platform/bootable/recovery" path="src/aosp/bootable/recovery" remote="aosp" revision="a82ee456bbb2fdcd77b782d52500650bd06d04e9" upstream="refs/heads/master"/> |
| <project name="platform/external/bsdiff" path="src/aosp/external/bsdiff" remote="aosp" revision="58632a3b7c85b2c0157d6f4d250ad397bd8fbe44" upstream="refs/heads/master"/> |
| <project name="platform/hardware/libhardware" path="src/platform/libhardware" remote="aosp" revision="69ed5d9a8306ee0427f378abe85cabfc5c3c1f17" upstream="refs/heads/master"/> |
| <project name="platform/system/bt" path="src/platform/bt" remote="aosp" revision="3a2dc880ce9b84b94e2ca53cb61b34c3aba19fc8" upstream="refs/heads/master"/> |
| <project name="platform/system/core" path="src/platform/core" remote="aosp" revision="c4be85fbba5957bc09a728940067104ed4339bc7" upstream="refs/heads/master"/> |
| <project name="toolchain/binutils" path="src/aosp/toolchain/binutils" remote="aosp" revision="6422a80df992e4542dbd4fb70a04f316065674af" upstream="refs/heads/master"/> |
| <project name="toolchain/gcc" path="src/aosp/toolchain/gcc" remote="aosp" revision="fe767fbb6d580458aeea609ac5c82b600acce63d"/> |
| <repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/> |
| <pending_commit branch="chromeos-3.14" change_id="If270431978be967d240b833023a454b7980a76f8" commit="dccea25d2d47568a7b16e273f6d62cd295847adb" commit_message="UPSTREAM: cpuset: inherit ancestor's masks if effective_{cpus, mems} becomes empty We're going to have separate user-configured masks and effective ones. Eventually configured masks can only be changed by writing cpuset.cpus and cpuset.mems, and they won't be restricted by parent cpuset. While effective masks reflect cpu/memory hotplug and hierachical restriction, and these are the real masks that apply to the tasks in the cpuset. We calculate effective mask this way: - top cpuset's effective_mask == online_mask, otherwise - cpuset's effective_mask == configured_mask & parent effective_mask, if the result is empty, it inherits parent effective mask. Those behavior changes are for default hierarchy only. For legacy hierarchy, effective_mask and configured_mask are the same, so we won't break old interfaces. To make cs->effective_{cpus,mems} to be effective masks, we need to - update the effective masks at hotplug - update the effective masks at config change - take on ancestor's mask when the effective mask is empty The last item is done here. This won't introduce behavior change. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 554b0d1c845e42ef01d7f6f5f24b3e4c6129ce8f) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: If270431978be967d240b833023a454b7980a76f8 Reviewed-on: https://chromium-review.googlesource.com/359851 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359851" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/51/359851/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I36478fe702a0a23a5520cd2e1e5ebb2b118b20a9" commit="b934b61af0d906421b4651b283287af8b4a4bec3" commit_message="UPSTREAM: cpuset: use effective cpumask to build sched domains We're going to have separate user-configured masks and effective ones. Eventually configured masks can only be changed by writing cpuset.cpus and cpuset.mems, and they won't be restricted by parent cpuset. While effective masks reflect cpu/memory hotplug and hierachical restriction, and these are the real masks that apply to the tasks in the cpuset. We calculate effective mask this way: - top cpuset's effective_mask == online_mask, otherwise - cpuset's effective_mask == configured_mask & parent effective_mask, if the result is empty, it inherits parent effective mask. Those behavior changes are for default hierarchy only. For legacy hierarchy, effective_mask and configured_mask are the same, so we won't break old interfaces. We should partition sched domains according to effective_cpus, which is the real cpulist that takes effects on tasks in the cpuset. This won't introduce behavior change. v2: - Add a comment for the call of rebuild_sched_domains(), suggested by Tejun. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 8b5f1c52dcd1accd3a940cfcb148bef6de589524) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I36478fe702a0a23a5520cd2e1e5ebb2b118b20a9 Reviewed-on: https://chromium-review.googlesource.com/359852 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359852" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/52/359852/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="Icf00e00b8ad7408b07688bdffbb3ede66c3558a9" commit="c0187aa94cb89bca1f0e4e0f90755c3ae01baa88" commit_message="UPSTREAM: cpuset: initialize top_cpuset's configured masks at mount We now have to support different behaviors for default hierachy and legacy hiearchy, top_cpuset's configured masks need to be initialized accordingly. Suppose we've offlined cpu1. On default hierarchy: # mount -t cgroup -o __DEVEL__sane_behavior xxx /cpuset # cat /cpuset/cpuset.cpus 0-15 On legacy hierarchy: # mount -t cgroup xxx /cpuset # cat /cpuset/cpuset.cpus 0,2-15 Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 39bd0d15eca5af15ee1492964f317ecdb024a9d6) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Icf00e00b8ad7408b07688bdffbb3ede66c3558a9 Reviewed-on: https://chromium-review.googlesource.com/359853 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359853" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/53/359853/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I01278156af5ac3cfd59e7124189aaf6dda9db6cf" commit="de73f85e948842fdae6d16aff8ca448c06ad7d4e" commit_message="UPSTREAM: cpuset: apply cs->effective_{cpus,mems} Now we can use cs->effective_{cpus,mems} as effective masks. It's used whenever: - we update tasks' cpus_allowed/mems_allowed, - we want to retrieve tasks_cs(tsk)'s cpus_allowed/mems_allowed. They actually replace effective_{cpu,node}mask_cpuset(). effective_mask == configured_mask & parent effective_mask except when the reault is empty, in which case it inherits parent effective_mask. The result equals the mask computed from effective_{cpu,node}mask_cpuset(). This won't affect the original legacy hierarchy, because in this case we make sure the effective masks are always the same with user-configured masks. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit ae1c802382f7af60aa54879fb4f5920a9df1ff48) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I01278156af5ac3cfd59e7124189aaf6dda9db6cf Reviewed-on: https://chromium-review.googlesource.com/359854 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359854" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/54/359854/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I2e9cbb0516b66c4a92e5c3b5a4ceb06741fde1e8" commit="ae415bab978c1b70803b9d62385f9bc3e226cc30" commit_message="UPSTREAM: cpuset: make cs->{cpus, mems}_allowed as user-configured masks Now we've used effective cpumasks to enforce hierarchical manner, we can use cs->{cpus,mems}_allowed as configured masks. Configured masks can be changed by writing cpuset.cpus and cpuset.mems only. The new behaviors are: - They won't be changed by hotplug anymore. - They won't be limited by its parent's masks. This ia a behavior change, but won't take effect unless mount with sane_behavior. v2: - Add comments to explain the differences between configured masks and effective masks. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 7e88291beefbb758fa3b27e500ee2e0c888d6e44) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I2e9cbb0516b66c4a92e5c3b5a4ceb06741fde1e8 Reviewed-on: https://chromium-review.googlesource.com/359855 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359855" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/55/359855/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I591eec84141924d92f9949afb5093a5a3e91504e" commit="875d11bb4bb993d16955cc5d14b30be25a5044ce" commit_message="UPSTREAM: cpuset: refactor cpuset_hotplug_update_tasks() We mix the handling for both default hierarchy and legacy hierarchy in the same function, and it's quite messy, so split into two functions. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 390a36aadf39e241c83035469aae48ed1a144088) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I591eec84141924d92f9949afb5093a5a3e91504e Reviewed-on: https://chromium-review.googlesource.com/359856 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359856" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/56/359856/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I8cafe520fea0d30189563ca62f8442c9351a3ce0" commit="4848553c4bd5328b72e9e386b5b65e103638140a" commit_message="UPSTREAM: cpuset: enable onlined cpu/node in effective masks Firstly offline cpu1: # echo 0-1 > cpuset.cpus # echo 0 > /sys/devices/system/cpu/cpu1/online # cat cpuset.cpus 0-1 # cat cpuset.effective_cpus 0 Then online it: # echo 1 > /sys/devices/system/cpu/cpu1/online # cat cpuset.cpus 0-1 # cat cpuset.effective_cpus 0-1 And cpuset will bring it back to the effective mask. The implementation is quite straightforward. Instead of calculating the offlined cpus/mems and do updates, we just set the new effective_mask to online_mask & congifured_mask. This is a behavior change for default hierarchy, so legacy hierarchy won't be affected. v2: - make refactoring of cpuset_hotplug_update_tasks() as seperate patch, suggested by Tejun. - make hotplug_update_tasks_insane() use @new_cpus and @new_mems as hotplug_update_tasks_sane() does. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit be4c9dd7aee5ecf3e748da68c27b38bdca70d444) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I8cafe520fea0d30189563ca62f8442c9351a3ce0 Reviewed-on: https://chromium-review.googlesource.com/359857 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359857" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/57/359857/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I9f10d0b68c3549631d574b0941ef9c42f6fe46ef" commit="bdb181a755b1e7ca8686d9ccc4038b690d94d9a0" commit_message="UPSTREAM: cpuset: allow writing offlined masks to cpuset.cpus/mems As the configured masks won't be limited by its parent, and the top cpuset's masks won't change when hotplug happens, it's natural to allow writing offlined masks to the configured masks. If on default hierarchy: # echo 0 > /sys/devices/system/cpu/cpu1/online # mkdir /cpuset/sub # echo 1 > /cpuset/sub/cpuset.cpus # cat /cpuset/sub/cpuset.cpus 1 If on legacy hierarchy: # echo 0 > /sys/devices/system/cpu/cpu1/online # mkdir /cpuset/sub # echo 1 > /cpuset/sub/cpuset.cpus -bash: echo: write error: Invalid argument Note the checks don't need to be gated by cgroup_on_dfl, because we've initialized top_cpuset.{cpus,mems}_allowed accordingly in cpuset_bind(). Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 5d8ba82c3a1f10b77bf39ee3e7670d6789a8d149) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I9f10d0b68c3549631d574b0941ef9c42f6fe46ef Reviewed-on: https://chromium-review.googlesource.com/359858 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359858" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/58/359858/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I7c016d8045c4b95a462070804a09c00fb2d66b9f" commit="bb73150b61004c5bd4858ed3ac62878fc869d6e2" commit_message="UPSTREAM: cpuset: export effective masks to userspace cpuset.cpus and cpuset.mems are the configured masks, and we need to export effective masks to userspace, so users know the real cpus_allowed and mems_allowed that apply to the tasks in a cpuset. v2: - export those masks unconditionally, suggested by Tejun. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit afd1a8b3e0bc4d045d762dfdbc4d0cee189893a4) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I7c016d8045c4b95a462070804a09c00fb2d66b9f Reviewed-on: https://chromium-review.googlesource.com/359859 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359859" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/59/359859/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I5e91046d4363c083edc3b916d5a2d7d4c3843642" commit="df9ca8f987d56a737016a880e8cb4b0c0ed10c99" commit_message="UPSTREAM: cgroup: split cgroup_base_files[] into cgroup_{dfl|legacy}_base_files[] Currently cgroup_base_files[] contains the cgroup core interface files for both legacy and default hierarchies with each file tagged with CFTYPE_INSANE and CFTYPE_ONLY_ON_DFL. This is difficult to read. Let's separate it out to two separate tables, cgroup_dfl_base_files[] and cgroup_legacy_base_files[], and use the appropriate one in cgroup_mkdir() depending on the hierarchy type. This makes tagging each file unnecessary. This patch doesn't introduce any behavior changes. v2: cgroup_dfl_base_files[] was missing the termination entry triggering WARN in cgroup_init_cftypes() for 0day kernel testing robot. Fixed. Signed-off-by: Tejun Heo <tj@kernel.org> Acked-by: Li Zefan <lizefan@huawei.com> Cc: Jet Chen <jet.chen@intel.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit a14c6874be09a05a48093df8df87ca021f310332) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I5e91046d4363c083edc3b916d5a2d7d4c3843642 Reviewed-on: https://chromium-review.googlesource.com/359860 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359860" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/60/359860/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I59e261401b481bfaa491cf17e80194cd3591cedb" commit="2c23f2a9715f9fb017b25e976d73d63949e55c37" commit_message="UPSTREAM: cgroup: rename cgroup_subsys->base_cftypes to ->legacy_cftypes Currently, cgroup_subsys->base_cftypes is used for both the unified default hierarchy and legacy ones and subsystems can mark each file with either CFTYPE_ONLY_ON_DFL or CFTYPE_INSANE if it has to appear only on one of them. This is quite hairy and error-prone. Also, we may end up exposing interface files to the default hierarchy without thinking it through. cgroup_subsys will grow two separate cftype arrays and apply each only on the hierarchies of the matching type. This will allow organizing cftypes in a lot clearer way and encourage subsystems to scrutinize the interface which is being exposed in the new default hierarchy. In preparation, this patch renames cgroup_subsys->base_cftypes to cgroup_subsys->legacy_cftypes. This patch is pure rename. Signed-off-by: Tejun Heo <tj@kernel.org> Acked-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Li Zefan <lizefan@huawei.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@suse.cz> Cc: Vivek Goyal <vgoyal@redhat.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Paul Mackerras <paulus@samba.org> Cc: Ingo Molnar <mingo@redhat.com> Cc: Arnaldo Carvalho de Melo <acme@kernel.org> Cc: Aristeu Rozanski <aris@redhat.com> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 5577964e64692e17cc498854b7e0833e6532cd64) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I59e261401b481bfaa491cf17e80194cd3591cedb Reviewed-on: https://chromium-review.googlesource.com/359861 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359861" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/61/359861/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="Id60bae109eddb688e57e58f06dd5bb01e37bb990" commit="7ad11448ad852b0070a26f23bd933ba53fe56875" commit_message="UPSTREAM: cgroup: replace cgroup_add_cftypes() with cgroup_add_legacy_cftypes() Currently, cftypes added by cgroup_add_cftypes() are used for both the unified default hierarchy and legacy ones and subsystems can mark each file with either CFTYPE_ONLY_ON_DFL or CFTYPE_INSANE if it has to appear only on one of them. This is quite hairy and error-prone. Also, we may end up exposing interface files to the default hierarchy without thinking it through. cgroup_subsys will grow two separate cftype addition functions and apply each only on the hierarchies of the matching type. This will allow organizing cftypes in a lot clearer way and encourage subsystems to scrutinize the interface which is being exposed in the new default hierarchy. In preparation, this patch adds cgroup_add_legacy_cftypes() which currently is a simple wrapper around cgroup_add_cftypes() and replaces all cgroup_add_cftypes() usages with it. While at it, this patch drops a completely spurious return from __hugetlb_cgroup_file_init(). This patch doesn't introduce any functional differences. Signed-off-by: Tejun Heo <tj@kernel.org> Acked-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Li Zefan <lizefan@huawei.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@suse.cz> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 2cf669a58dc08fa065a8bd0dca866c0e6cb358cc) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Id60bae109eddb688e57e58f06dd5bb01e37bb990 Reviewed-on: https://chromium-review.googlesource.com/359862 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359862" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/62/359862/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I6e050a281b849d13777e79e61514b925ead63ad9" commit="060f73fd2248ebeccc3a2d2f515f3a4f9183f2e7" commit_message="UPSTREAM: cgroup: distinguish the default and legacy hierarchies when handling cftypes Until now, cftype arrays carried files for both the default and legacy hierarchies and the files which needed to be used on only one of them were flagged with either CFTYPE_ONLY_ON_DFL or CFTYPE_INSANE. This gets confusing very quickly and we may end up exposing interface files to the default hierarchy without thinking it through. This patch makes cgroup core provide separate sets of interfaces for cftype handling so that the cftypes for the default and legacy hierarchies are clearly distinguished. The previous two patches renamed the existing ones so that they clearly indicate that they're for the legacy hierarchies. This patch adds the interface for the default hierarchy and apply them selectively depending on the hierarchy type. * cftypes added through cgroup_subsys->dfl_cftypes and cgroup_add_dfl_cftypes() only show up on the default hierarchy. * cftypes added through cgroup_subsys->legacy_cftypes and cgroup_add_legacy_cftypes() only show up on the legacy hierarchies. * cgroup_subsys->dfl_cftypes and ->legacy_cftypes can point to the same array for the cases where the interface files are identical on both types of hierarchies. * This makes all the existing subsystem interface files legacy-only by default and all subsystems will have no interface file created when enabled on the default hierarchy. Each subsystem should explicitly review and compose the interface for the default hierarchy. * A boot param "cgroup__DEVEL__legacy_files_on_dfl" is added which makes subsystems which haven't decided the interface files for the default hierarchy to present the legacy files on the default hierarchy so that its behavior on the default hierarchy can be tested. As the awkward name suggests, this is for development only. * memcg's CFTYPE_INSANE on "use_hierarchy" is noop now as the whole array isn't used on the default hierarchy. The flag is removed. v2: Updated documentation for cgroup__DEVEL__legacy_files_on_dfl. v3: Clear CFTYPE_ONLY_ON_DFL and CFTYPE_INSANE when cfts are removed as suggested by Li. Signed-off-by: Tejun Heo <tj@kernel.org> Acked-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Li Zefan <lizefan@huawei.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@suse.cz> Cc: Vivek Goyal <vgoyal@redhat.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Paul Mackerras <paulus@samba.org> Cc: Ingo Molnar <mingo@redhat.com> Cc: Arnaldo Carvalho de Melo <acme@kernel.org> Cc: Aristeu Rozanski <aris@redhat.com> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit a8ddc8215e1a4cd9dc5d6210811cfc381a489ec2) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I6e050a281b849d13777e79e61514b925ead63ad9 Reviewed-on: https://chromium-review.googlesource.com/359863 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359863" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/63/359863/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I5537d256d7b2139902142b81bcce5c2b949b41ea" commit="9e23057ab18af58dac15c55a728c70cd874c996a" commit_message="UPSTREAM: cgroup: make CFTYPE_ONLY_ON_DFL and CFTYPE_NO_ internal to cgroup core cgroup now distinguishes cftypes for the default and legacy hierarchies more explicitly by using separate arrays and CFTYPE_ONLY_ON_DFL and CFTYPE_INSANE should be and are used only inside cgroup core proper. Let's make it clear that the flags are internal by prefixing them with double underscores. CFTYPE_INSANE is renamed to __CFTYPE_NOT_ON_DFL for consistency. The two flags are also collected and assigned bits >= 16 so that they aren't mixed with the published flags. v2: Convert the extra ones in cgroup_exit_cftypes() which are added by revision to the previous patch. Signed-off-by: Tejun Heo <tj@kernel.org> Acked-by: Li Zefan <lizefan@huawei.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 05ebb6e60f044a9cef2549b6204559276500f363) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I5537d256d7b2139902142b81bcce5c2b949b41ea Reviewed-on: https://chromium-review.googlesource.com/359864 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359864" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/64/359864/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I2709b380c209f68408eb645d1ec30c015be4156b" commit="fe5d1faf209a321f9ab5fd0abe922c9b7cfd861f" commit_message="UPSTREAM: cgroup: initialize cgrp_dfl_root_inhibit_ss_mask from !->dfl_files test cgrp_dfl_root_inhibit_ss_mask determines which subsystems are not supported on the default hierarchy and is currently initialized statically and just includes the debug subsystem. Now that there's cgroup_subsys->dfl_files, we can easily tell which subsystems support the default hierarchy or not. Let's initialize cgrp_dfl_root_inhibit_ss_mask by testing whether cgroup_subsys->dfl_files is NULL. After all, subsystems with NULL ->dfl_files aren't useable on the default hierarchy anyway. Signed-off-by: Tejun Heo <tj@kernel.org> Acked-by: Li Zefan <lizefan@huawei.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 5de4fa13c4df302db41e80ca679df24fdad0d661) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I2709b380c209f68408eb645d1ec30c015be4156b Reviewed-on: https://chromium-review.googlesource.com/359865 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359865" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/65/359865/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="Ie4cf2e275f3f98a0b292b468c73d5f50ca604c45" commit="1f35fafb12c7117cd6ea414effa437415d5d392a" commit_message="UPSTREAM: cgroup: fix broken css_has_online_children() After running: # mount -t cgroup cpu xxx /cgroup && mkdir /cgroup/sub && \ rmdir /cgroup/sub && umount /cgroup I found the cgroup root still existed: # cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset 0 1 1 cpu 1 1 1 ... It turned out css_has_online_children() is broken. Signed-off-by: Li Zefan <lizefan@huawei.com> Sigend-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 99bae5f94185c2cc65701e95c54e31e2f4345b88) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ie4cf2e275f3f98a0b292b468c73d5f50ca604c45 Reviewed-on: https://chromium-review.googlesource.com/359866 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359866" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/66/359866/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I416f2707283769e9e87a3248ae8ab8c08b980b22" commit="844f9c0a3bb4368056fe4d8d9de2174eeae70e07" commit_message="UPSTREAM: cgroup: fix top cgroup refcnt leak As mount() and kill_sb() is not a one-to-one match, If we mount the same cgroupfs in serveral mount points, and then umount all of them, kill_sb() will be called only once. Try: # mount -t cgroup -o cpuacct xxx /cgroup # mount -t cgroup -o cpuacct xxx /cgroup2 # cat /proc/cgroups | grep cpuacct cpuacct 2 1 1 # umount /cgroup # umount /cgroup2 # cat /proc/cgroups | grep cpuacct cpuacct 2 1 1 You'll see cgroupfs will never be freed. Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit c6b3d5bcd67c75961a1e8b9564d1475c0f194a84) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I416f2707283769e9e87a3248ae8ab8c08b980b22 Reviewed-on: https://chromium-review.googlesource.com/359867 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359867" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/67/359867/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I2f2734caa2b591d5adc512495775fbd99064878d" commit="ce0ed6effed54a6d9caed143006138945d43f965" commit_message="UPSTREAM: cgroup: fix mount failure in a corner case # cat test.sh #! /bin/bash mount -t cgroup -o cpu xxx /cgroup umount /cgroup mount -t cgroup -o cpu,cpuacct xxx /cgroup umount /cgroup # ./test.sh mount: xxx already mounted or /cgroup busy mount: according to mtab, xxx is already mounted on /cgroup It's because the cgroupfs_root of the first mount was under destruction asynchronously. Fix this by delaying and then retrying mount for this case. v3: - put the refcnt immediately after getting it. (Tejun) v2: - use percpu_ref_tryget_live() rather that introducing percpu_ref_alive(). (Tejun) - adjust comment. tj: Updated the comment a bit. Cc: <stable@vger.kernel.org> # 3.15 Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 970317aa48c6ef66cd023c039c2650c897bad927) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I2f2734caa2b591d5adc512495775fbd99064878d Reviewed-on: https://chromium-review.googlesource.com/359868 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359868" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/68/359868/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I7529d89d3466af5d53b36c72446ba0271d8c32bb" commit="d4a0776e74d25af662f4a11799707adbd56e6fc4" commit_message="UPSTREAM: kernfs, sysfs, cgroup: restrict extra perm check on open to sysfs The kernfs open method - kernfs_fop_open() - inherited extra permission checks from sysfs. While the vfs layer allows ignoring the read/write permissions checks if the issuer has CAP_DAC_OVERRIDE, sysfs explicitly denied open regardless of the cap if the file doesn't have any of the UGO perms of the requested access or doesn't implement the requested operation. It can be debated whether this was a good idea or not but the behavior is too subtle and dangerous to change at this point. After cgroup got converted to kernfs, this extra perm check also got applied to cgroup breaking libcgroup which opens write-only files with O_RDWR as root. This patch gates the extra open permission check with a new flag KERNFS_ROOT_EXTRA_OPEN_PERM_CHECK and enables it for sysfs. For sysfs, nothing changes. For cgroup, root now can perform any operation regardless of the permissions as it was before kernfs conversion. Note that kernfs still fails unimplemented operations with -EINVAL. While at it, add comments explaining KERNFS_ROOT flags. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Andrey Wagin <avagin@gmail.com> Tested-by: Andrey Wagin <avagin@gmail.com> Cc: Li Zefan <lizefan@huawei.com> References: http://lkml.kernel.org/g/CANaxB-xUm3rJ-Cbp72q-rQJO5mZe1qK6qXsQM=vh0U8upJ44+A@mail.gmail.com Fixes: 2bd59d48ebfb ("cgroup: convert to kernfs") Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 555724a831b4a146e7bdf16ecc989cda032b076d) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I7529d89d3466af5d53b36c72446ba0271d8c32bb Reviewed-on: https://chromium-review.googlesource.com/359869 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359869" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/69/359869/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="Id13e6e92d875fab62385f03051826774c810d7a9" commit="6e974c5a8561f033c4f8f590d3cf60081c54615c" commit_message="UPSTREAM: kernfs: move the last knowledge of sysfs out from kernfs There is still one residue of sysfs remaining: the sb_magic SYSFS_MAGIC. However this should be kernfs user specific, so this patch moves it out. Kerrnfs user should specify their magic number while mouting. Signed-off-by: Jianyu Zhan <nasa4836@gmail.com> Acked-by: Tejun Heo <tj@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 26fc9cd200ec839e0b3095e05ae018f27314e7aa) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Id13e6e92d875fab62385f03051826774c810d7a9 Reviewed-on: https://chromium-review.googlesource.com/359870 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359870" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/70/359870/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I92bfacb4b81ac8817d59fb8ba429d956d31eccb0" commit="17d52ba94090d1332772d14b4770698b77efa865" commit_message="UPSTREAM: kernfs: kernfs_notify() must be useable from non-sleepable contexts d911d9874801 ("kernfs: make kernfs_notify() trigger inotify events too") added fsnotify triggering to kernfs_notify() which requires a sleepable context. There are already existing users of kernfs_notify() which invoke it from an atomic context and in general it's silly to require a sleepable context for triggering a notification. The following is an invalid context bug triggerd by md invoking sysfs_notify() from IO completion path. BUG: sleeping function called from invalid context at kernel/locking/mutex.c:586 in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk] #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240 irq event stamp: 33518 hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230 hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72 softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0x50 softirqs last disabled at (33517): [<ffffffff810a29e0>] irq_enter+0x60/0x80 CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.16.0-0.rc2.git2.1.fc21.x86_64 #1 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 0000000000000000 f90db13964f4ee05 ffff88007d403b80 ffffffff81807b4c 0000000000000000 ffff88007d403ba8 ffffffff810d4f14 0000000000000000 0000000000441800 ffff880078fa1780 ffff88007d403c38 ffffffff8180caf2 Call Trace: <IRQ> [<ffffffff81807b4c>] dump_stack+0x4d/0x66 [<ffffffff810d4f14>] __might_sleep+0x184/0x240 [<ffffffff8180caf2>] mutex_lock_nested+0x42/0x440 [<ffffffff812d76a0>] kernfs_notify+0x90/0x150 [<ffffffff8163377c>] bitmap_endwrite+0xcc/0x240 [<ffffffffa00de863>] close_write+0x93/0xb0 [raid1] [<ffffffffa00df029>] r1_bio_write_done+0x29/0x50 [raid1] [<ffffffffa00e0474>] raid1_end_write_request+0xe4/0x260 [raid1] [<ffffffff813acb8b>] bio_endio+0x6b/0xa0 [<ffffffff813b46c4>] blk_update_request+0x94/0x420 [<ffffffff813bf0ea>] blk_mq_end_io+0x1a/0x70 [<ffffffffa00392c2>] virtblk_request_done+0x32/0x80 [virtio_blk] [<ffffffff813c0648>] __blk_mq_complete_request+0x88/0x120 [<ffffffff813c070a>] blk_mq_complete_request+0x2a/0x30 [<ffffffffa0039066>] virtblk_done+0x66/0xe0 [virtio_blk] [<ffffffffa002535a>] vring_interrupt+0x3a/0xa0 [virtio_ring] [<ffffffff81116177>] handle_irq_event_percpu+0x77/0x340 [<ffffffff8111647d>] handle_irq_event+0x3d/0x60 [<ffffffff81119436>] handle_edge_irq+0x66/0x130 [<ffffffff8101c3e4>] handle_irq+0x84/0x150 [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 [<ffffffff818122f2>] common_interrupt+0x72/0x72 <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 [<ffffffff81025454>] default_idle+0x24/0x230 [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 [<ffffffff8104df1b>] start_secondary+0x25b/0x300 This patch fixes it by punting the notification delivery through a work item. This ends up adding an extra pointer to kernfs_elem_attr enlarging kernfs_node by a pointer, which is not ideal but not a very big deal either. If this turns out to be an actual issue, we can move kernfs_elem_attr->size to kernfs_node->iattr later. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Josh Boyer <jwboyer@fedoraproject.org> Cc: Jens Axboe <axboe@kernel.dk> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit ecca47ce8294843045e7465d76fee84dbf07a004) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I92bfacb4b81ac8817d59fb8ba429d956d31eccb0 Reviewed-on: https://chromium-review.googlesource.com/359871 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359871" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/71/359871/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I209aac8bcf4851fc99d69c88535cc4372f9993ff" commit="9253eab128f13683291a8aff4883d9654740d1c8" commit_message="UPSTREAM: kernfs: introduce kernfs_pin_sb() kernfs_pin_sb() tries to get a refcnt of the superblock. This will be used by cgroupfs. v2: - make kernfs_pin_sb() return the superblock. - drop kernfs_drop_sb(). tj: Updated the comment a bit. [ This is a prerequisite for a bugfix. ] Cc: <stable@vger.kernel.org> # 3.15 Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 4e26445faad366d67d7723622bf6a60a6f0f5993) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I209aac8bcf4851fc99d69c88535cc4372f9993ff Reviewed-on: https://chromium-review.googlesource.com/359872 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359872" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/72/359872/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="Iba004822b5a12c5a20113ad29712a7d01a2e283c" commit="6e6e85e3812f6a617aaa471248a0e33d24db1c2c" commit_message="UPSTREAM: cgroup: fix a race between cgroup_mount() and cgroup_kill_sb() We've converted cgroup to kernfs so cgroup won't be intertwined with vfs objects and locking, but there are dark areas. Run two instances of this script concurrently: for ((; ;)) { mount -t cgroup -o cpuacct xxx /cgroup umount /cgroup } After a while, I saw two mount processes were stuck at retrying, because they were waiting for a subsystem to become free, but the root associated with this subsystem never got freed. This can happen, if thread A is in the process of killing superblock but hasn't called percpu_ref_kill(), and at this time thread B is mounting the same cgroup root and finds the root in the root list and performs percpu_ref_try_get(). To fix this, we try to increase both the refcnt of the superblock and the percpu refcnt of cgroup root. v2: - we should try to get both the superblock refcnt and cgroup_root refcnt, because cgroup_root may have no superblock assosiated with it. - adjust/add comments. tj: Updated comments. Renamed @sb to @pinned_sb. Cc: <stable@vger.kernel.org> # 3.15 Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 3a32bd72d77058d768dbb38183ad517f720dd1bc) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Iba004822b5a12c5a20113ad29712a7d01a2e283c Reviewed-on: https://chromium-review.googlesource.com/359873 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359873" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/73/359873/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="Ie79ef71e61dd2a2301738df84879851319cdd0d0" commit="73ed6d748af4e01b5f6f7ea06127cc44362e1592" commit_message="UPSTREAM: cpuset,mempolicy: fix sleeping function called from invalid context When runing with the kernel(3.15-rc7+), the follow bug occurs: [ 9969.258987] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:586 [ 9969.359906] in_atomic(): 1, irqs_disabled(): 0, pid: 160655, name: python [ 9969.441175] INFO: lockdep is turned off. [ 9969.488184] CPU: 26 PID: 160655 Comm: python Tainted: G A 3.15.0-rc7+ #85 [ 9969.581032] Hardware name: FUJITSU-SV PRIMEQUEST 1800E/SB, BIOS PRIMEQUEST 1000 Series BIOS Version 1.39 11/16/2012 [ 9969.706052] ffffffff81a20e60 ffff8803e941fbd0 ffffffff8162f523 ffff8803e941fd18 [ 9969.795323] ffff8803e941fbe0 ffffffff8109995a ffff8803e941fc58 ffffffff81633e6c [ 9969.884710] ffffffff811ba5dc ffff880405c6b480 ffff88041fdd90a0 0000000000002000 [ 9969.974071] Call Trace: [ 9970.003403] [<ffffffff8162f523>] dump_stack+0x4d/0x66 [ 9970.065074] [<ffffffff8109995a>] __might_sleep+0xfa/0x130 [ 9970.130743] [<ffffffff81633e6c>] mutex_lock_nested+0x3c/0x4f0 [ 9970.200638] [<ffffffff811ba5dc>] ? kmem_cache_alloc+0x1bc/0x210 [ 9970.272610] [<ffffffff81105807>] cpuset_mems_allowed+0x27/0x140 [ 9970.344584] [<ffffffff811b1303>] ? __mpol_dup+0x63/0x150 [ 9970.409282] [<ffffffff811b1385>] __mpol_dup+0xe5/0x150 [ 9970.471897] [<ffffffff811b1303>] ? __mpol_dup+0x63/0x150 [ 9970.536585] [<ffffffff81068c86>] ? copy_process.part.23+0x606/0x1d40 [ 9970.613763] [<ffffffff810bf28d>] ? trace_hardirqs_on+0xd/0x10 [ 9970.683660] [<ffffffff810ddddf>] ? monotonic_to_bootbased+0x2f/0x50 [ 9970.759795] [<ffffffff81068cf0>] copy_process.part.23+0x670/0x1d40 [ 9970.834885] [<ffffffff8106a598>] do_fork+0xd8/0x380 [ 9970.894375] [<ffffffff81110e4c>] ? __audit_syscall_entry+0x9c/0xf0 [ 9970.969470] [<ffffffff8106a8c6>] SyS_clone+0x16/0x20 [ 9971.030011] [<ffffffff81642009>] stub_clone+0x69/0x90 [ 9971.091573] [<ffffffff81641c29>] ? system_call_fastpath+0x16/0x1b The cause is that cpuset_mems_allowed() try to take mutex_lock(&callback_mutex) under the rcu_read_lock(which was hold in __mpol_dup()). And in cpuset_mems_allowed(), the access to cpuset is under rcu_read_lock, so in __mpol_dup, we can reduce the rcu_read_lock protection region to protect the access to cpuset only in current_cpuset_is_being_rebound(). So that we can avoid this bug. This patch is a temporary solution that just addresses the bug mentioned above, can not fix the long-standing issue about cpuset.mems rebinding on fork(): "When the forker's task_struct is duplicated (which includes ->mems_allowed) and it races with an update to cpuset_being_rebound in update_tasks_nodemask() then the task's mems_allowed doesn't get updated. And the child task's mems_allowed can be wrong if the cpuset's nodemask changes before the child has been added to the cgroup's tasklist." Signed-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com> Acked-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> Cc: stable <stable@vger.kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 391acf970d21219a2a5446282d3b20eace0c0d7a) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ie79ef71e61dd2a2301738df84879851319cdd0d0 Reviewed-on: https://chromium-review.googlesource.com/359874 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359874" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/74/359874/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I19bdc820137073c94b984785f574024437e3a14c" commit="99c32c42a0d02dcc946112fdcab44fc0250ee2a6" commit_message="UPSTREAM: cpuset: break kernfs active protection in cpuset_write_resmask() Writing to either "cpuset.cpus" or "cpuset.mems" file flushes cpuset_hotplug_work so that cpu or memory hotunplug doesn't end up migrating tasks off a cpuset after new resources are added to it. As cpuset_hotplug_work calls into cgroup core via cgroup_transfer_tasks(), this flushing adds the dependency to cgroup core locking from cpuset_write_resmak(). This used to be okay because cgroup interface files were protected by a different mutex; however, 8353da1f91f1 ("cgroup: remove cgroup_tree_mutex") simplified the cgroup core locking and this dependency became a deadlock hazard - cgroup file removal performed under cgroup core lock tries to drain on-going file operation which is trying to flush cpuset_hotplug_work blocked on the same cgroup core lock. The locking simplification was done because kernfs added an a lot easier way to deal with circular dependencies involving kernfs active protection. Let's use the same strategy in cpuset and break active protection in cpuset_write_resmask(). While it isn't the prettiest, this is a very rare, likely unique, situation which also goes away on the unified hierarchy. The commands to trigger the deadlock warning without the patch and the lockdep output follow. localhost:/ # mount -t cgroup -o cpuset xxx /cpuset localhost:/ # mkdir /cpuset/tmp localhost:/ # echo 1 > /cpuset/tmp/cpuset.cpus localhost:/ # echo 0 > cpuset/tmp/cpuset.mems localhost:/ # echo $$ > /cpuset/tmp/tasks localhost:/ # echo 0 > /sys/devices/system/cpu/cpu1/online ====================================================== [ INFO: possible circular locking dependency detected ] 3.16.0-rc1-0.1-default+ #7 Not tainted ------------------------------------------------------- kworker/1:0/32649 is trying to acquire lock: (cgroup_mutex){+.+.+.}, at: [<ffffffff8110e3d7>] cgroup_transfer_tasks+0x37/0x150 but task is already holding lock: (cpuset_hotplug_work){+.+...}, at: [<ffffffff81085412>] process_one_work+0x192/0x520 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (cpuset_hotplug_work){+.+...}: ... -> #1 (s_active#175){++++.+}: ... -> #0 (cgroup_mutex){+.+.+.}: ... other info that might help us debug this: Chain exists of: cgroup_mutex --> s_active#175 --> cpuset_hotplug_work Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(cpuset_hotplug_work); lock(s_active#175); lock(cpuset_hotplug_work); lock(cgroup_mutex); *** DEADLOCK *** 2 locks held by kworker/1:0/32649: #0: ("events"){.+.+.+}, at: [<ffffffff81085412>] process_one_work+0x192/0x520 #1: (cpuset_hotplug_work){+.+...}, at: [<ffffffff81085412>] process_one_work+0x192/0x520 stack backtrace: CPU: 1 PID: 32649 Comm: kworker/1:0 Not tainted 3.16.0-rc1-0.1-default+ #7 ... Call Trace: [<ffffffff815a5f78>] dump_stack+0x72/0x8a [<ffffffff810c263f>] print_circular_bug+0x10f/0x120 [<ffffffff810c481e>] check_prev_add+0x43e/0x4b0 [<ffffffff810c4ee6>] validate_chain+0x656/0x7c0 [<ffffffff810c53d2>] __lock_acquire+0x382/0x660 [<ffffffff810c57a9>] lock_acquire+0xf9/0x170 [<ffffffff815aa13f>] mutex_lock_nested+0x6f/0x380 [<ffffffff8110e3d7>] cgroup_transfer_tasks+0x37/0x150 [<ffffffff811129c0>] hotplug_update_tasks_insane+0x110/0x1d0 [<ffffffff81112bbd>] cpuset_hotplug_update_tasks+0x13d/0x180 [<ffffffff811148ec>] cpuset_hotplug_workfn+0x18c/0x630 [<ffffffff810854d4>] process_one_work+0x254/0x520 [<ffffffff810875dd>] worker_thread+0x13d/0x3d0 [<ffffffff8108e0c8>] kthread+0xf8/0x100 [<ffffffff815acaec>] ret_from_fork+0x7c/0xb0 Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Li Zefan <lizefan@huawei.com> Tested-by: Li Zefan <lizefan@huawei.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 76bb5ab8f6e3e7bebdcefec4146ff305e7d0b465) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I19bdc820137073c94b984785f574024437e3a14c Reviewed-on: https://chromium-review.googlesource.com/359875 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="5" gerrit_number="359875" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/75/359875/1" remote="cros" total_fail_count="5"/><pending_commit branch="chromeos-3.14" change_id="I6fbf3bd07f5f1991976c05a440c425949c7c0576" commit="eda2fed9c2b6b2aa0dd55f9ec5a41f2025af31fd" commit_message="UPSTREAM: cpuset: fix the WARN_ON() in update_nodemasks_hier() The WARN_ON() is used to check if we break the legal hierarchy, on which the effective mems should be equal to configured mems. Reported-by: Mike Qiu <qiudayu@linux.vnet.ibm.com> Tested-by: Mike Qiu <qiudayu@linux.vnet.ibm.com> Signed-off-by: Li Zefan <lizefan@huawei.com> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit a13812683f1118ee4deed88d8d9bc2c268358b2e) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I6fbf3bd07f5f1991976c05a440c425949c7c0576 Reviewed-on: https://chromium-review.googlesource.com/359876 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359876" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/76/359876/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I49fad22f31af2a6aaf92b36bef4ee0e51e3c3f80" commit="1a73204de66f2097c5d0b74e77522cd6a0569400" commit_message="UPSTREAM: cgroup: reject cgroup names with '\n' /proc/<pid>/cgroup contains one cgroup path on each line. If cgroup names are allowed to contain "\n", applications cannot parse /proc/<pid>/cgroup safely. Signed-off-by: Alban Crequy <alban.crequy@collabora.co.uk> Signed-off-by: Tejun Heo <tj@kernel.org> Cc: stable@vger.kernel.org BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 71b1fb5c4473a5b1e601d41b109bdfe001ec82e0) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I49fad22f31af2a6aaf92b36bef4ee0e51e3c3f80 Reviewed-on: https://chromium-review.googlesource.com/359877 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359877" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/77/359877/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I42c7f5263f23b2b2439d4da8c0a1db87a3d28edf" commit="17f0600bdf407c198779ef08681f76a226c79c13" commit_message="UPSTREAM: cgroup: Display legacy cgroup files on default hierarchy Kernel command line parameter cgroup__DEVEL__legacy_files_on_dfl forces legacy cgroup files to show up on default hierarhcy if susbsystem does not have any files defined for default hierarchy. But this seems to be working only if legacy files are defined in ss->legacy_cftypes. If one adds some cftypes later using cgroup_add_legacy_cftypes(), these files don't show up on default hierarchy. Update the function accordingly so that the dynamically added legacy files also show up in the default hierarchy if the target subsystem is also using the base legacy files for the default hierarchy. tj: Patch description and comment updates. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit fa8137be6ba632041e725e4623258ba27a2cf9be) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I42c7f5263f23b2b2439d4da8c0a1db87a3d28edf Reviewed-on: https://chromium-review.googlesource.com/359878 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359878" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/78/359878/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="Ibf16563b6431a876b8f416c5a7187285c955cfa1" commit="860c7b8291e34fdb563b063e13a560f8da14d58b" commit_message="UPSTREAM: cgroup: fix a typo in comment. There is no function named cgroup_enable_task_cg_links(). Instead, the correct function name in this comment should be cgroup_enabled_task_cg_lists(). Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 251f8c0364f99fc21fcc7b07e4ec6b4f3250d841) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ibf16563b6431a876b8f416c5a7187285c955cfa1 Reviewed-on: https://chromium-review.googlesource.com/359879 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359879" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/79/359879/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="Iba57bd2781d18c234ab8739b8d609793a89eab53" commit="823052975ab8b3a7cb617aea87e0904a94762b79" commit_message="UPSTREAM: cgroup: delay the clearing of cgrp->kn->priv Run these two scripts concurrently: for ((; ;)) { mkdir /cgroup/sub rmdir /cgroup/sub } for ((; ;)) { echo $$ > /cgroup/sub/cgroup.procs echo $$ > /cgroup/cgroup.procs } A kernel bug will be triggered: BUG: unable to handle kernel NULL pointer dereference at 00000038 IP: [<c10bbd69>] cgroup_put+0x9/0x80 ... Call Trace: [<c10bbe19>] cgroup_kn_unlock+0x39/0x50 [<c10bbe91>] cgroup_kn_lock_live+0x61/0x70 [<c10be3c1>] __cgroup_procs_write.isra.26+0x51/0x230 [<c10be5b2>] cgroup_tasks_write+0x12/0x20 [<c10bb7b0>] cgroup_file_write+0x40/0x130 [<c11aee71>] kernfs_fop_write+0xd1/0x160 [<c1148e58>] vfs_write+0x98/0x1e0 [<c114934d>] SyS_write+0x4d/0xa0 [<c16f656b>] sysenter_do_call+0x12/0x12 We clear cgrp->kn->priv in the end of cgroup_rmdir(), but another concurrent thread can access kn->priv after the clearing. We should move the clearing to css_release_work_fn(). At that time no one is holding reference to the cgroup and no one can gain a new reference to access it. v2: - move RCU_INIT_POINTER() into the else block. (Tejun) - remove the cgroup_parent() check. (Tejun) - update the comment in css_tryget_online_from_dir(). Cc: <stable@vger.kernel.org> # 3.15+ Reported-by: Toralf Frster <toralf.foerster@gmx.de> Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit a4189487da1b4f8260c6006b9dc47c3c4107a5ae) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Iba57bd2781d18c234ab8739b8d609793a89eab53 Reviewed-on: https://chromium-review.googlesource.com/359880 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359880" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/80/359880/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="Iadb614216ef17e7d4608f34c8532afa2c7b15b9d" commit="c4994b4e75b188a6e592f5ad9fb0dd0309571823" commit_message="UPSTREAM: cgroup: check cgroup liveliness before unbreaking kernfs When cgroup_kn_lock_live() is called through some kernfs operation and another thread is calling cgroup_rmdir(), we'll trigger the warning in cgroup_get(). ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1228 at kernel/cgroup.c:1034 cgroup_get+0x89/0xa0() ... Call Trace: [<c16ee73d>] dump_stack+0x41/0x52 [<c10468ef>] warn_slowpath_common+0x7f/0xa0 [<c104692d>] warn_slowpath_null+0x1d/0x20 [<c10bb999>] cgroup_get+0x89/0xa0 [<c10bbe58>] cgroup_kn_lock_live+0x28/0x70 [<c10be3c1>] __cgroup_procs_write.isra.26+0x51/0x230 [<c10be5b2>] cgroup_tasks_write+0x12/0x20 [<c10bb7b0>] cgroup_file_write+0x40/0x130 [<c11aee71>] kernfs_fop_write+0xd1/0x160 [<c1148e58>] vfs_write+0x98/0x1e0 [<c114934d>] SyS_write+0x4d/0xa0 [<c16f656b>] sysenter_do_call+0x12/0x12 ---[ end trace 6f2e0c38c2108a74 ]--- Fix this by calling css_tryget() instead of cgroup_get(). v2: - move cgroup_tryget() right below cgroup_get() definition. (Tejun) Cc: <stable@vger.kernel.org> # 3.15+ Reported-by: Toralf Frster <toralf.foerster@gmx.de> Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit aa32362f011c6e863132b16c1761487166a4bad2) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Iadb614216ef17e7d4608f34c8532afa2c7b15b9d Reviewed-on: https://chromium-review.googlesource.com/359881 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359881" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/81/359881/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="Ic0cf80ca84abbaf1064c59263e553dc011b555d9" commit="ef87c6c93d9b6b1116e9b7e1c39c0cf79b00e67e" commit_message="UPSTREAM: cgroup: remove some useless forward declarations Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 6213daab2547fdc0d02a86abf3ac209ac6881ae3) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ic0cf80ca84abbaf1064c59263e553dc011b555d9 Reviewed-on: https://chromium-review.googlesource.com/359882 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359882" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/82/359882/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I087fc7e401f31e18fa75a5fb2b9ada3721db0d81" commit="c5c5c682ccda8abecfb10860257162e0cf0a29ea" commit_message="UPSTREAM: cgroup: remove redundant code in cgroup_rmdir() We no longer clear kn->priv in cgroup_rmdir(), so we don't need to get an extra refcnt. Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 244bb9a6336d2aa53526261ec35c593ebd5c1a33) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I087fc7e401f31e18fa75a5fb2b9ada3721db0d81 Reviewed-on: https://chromium-review.googlesource.com/359883 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359883" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/83/359883/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I1b689d46f31b80f6fb568bb3345805a8b2d8f6c6" commit="53418aa253e0c0201b73271306db890097e651e5" commit_message="UPSTREAM: cgroup: remove bogus comments We never grab cgroup mutex in fork and exit paths no matter whether notify_on_release is set or not. Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 0c8fc2c1210556434835adfb2274f41704853e8a) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I1b689d46f31b80f6fb568bb3345805a8b2d8f6c6 Reviewed-on: https://chromium-review.googlesource.com/359884 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359884" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/84/359884/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="Ie6bb9a7decd7a3a1964331e1a13895dc3d9daa1e" commit="372b9fa7ee96572e4cd506ece7a809092cff7053" commit_message="UPSTREAM: cgroup: use a per-cgroup work for release agent Instead of using a global work to schedule release agent on removable cgroups, we change to use a per-cgroup work to do this, which makes the code much simpler. v2: use a dedicated work instead of reusing css->destroy_work. (Tejun) Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 971ff49355387fef41d1327434d8939721a4eb35) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ie6bb9a7decd7a3a1964331e1a13895dc3d9daa1e Reviewed-on: https://chromium-review.googlesource.com/359885 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359885" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/85/359885/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="Ib88814f4ba3f0e324e22ba7c4c738fdf821acf64" commit="e8bc9ad31b7d26180205170a7369c34c2b9ff066" commit_message="UPSTREAM: cgroup: simplify proc_cgroup_show() Use the ONE macro instead of REG, and we can simplify proc_cgroup_show(). Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 006f4ac49742b5f70ef7e39176fd42a500144ccc) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: Ib88814f4ba3f0e324e22ba7c4c738fdf821acf64 Reviewed-on: https://chromium-review.googlesource.com/359886 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359886" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/86/359886/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="If386ac0ae8b2be5ec89687b335633c8e62fd7567" commit="daf7c38c5ed35157514721ca86d9d7253b5dad83" commit_message="UPSTREAM: cgroup: remove redundant check in cgroup_ino() After we implemented default unified hierarchy, cgrp->kn can never be NULL. Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit f29374b146dd02f5f99742aedaddd6ef3512fc9c) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: If386ac0ae8b2be5ec89687b335633c8e62fd7567 Reviewed-on: https://chromium-review.googlesource.com/359887 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359887" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/87/359887/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I18a6ceea176da44ba2afa4aa09678b09e7329b9e" commit="c239f4dd8ccf65c2903f335b40513e61e7b5b5bf" commit_message="UPSTREAM: cgroup: remove CGRP_RELEASABLE flag We call put_css_set() after setting CGRP_RELEASABLE flag in cgroup_task_migrate(), but in other places we call it without setting the flag. I don't see the necessity of this flag. Moreover once the flag is set, it will never be cleared, unless writing to the notify_on_release control file, so it can be quite confusing if we look at the output of debug.releasable. # mount -t cgroup -o debug xxx /cgroup # mkdir /cgroup/child # cat /cgroup/child/debug.releasable 0 <-- shows 0 though the cgroup is empty # echo $$ > /cgroup/child/tasks # cat /cgroup/child/debug.releasable 0 # echo $$ > /cgroup/tasks && echo $$ > /cgroup/child/tasks # cat /proc/child/debug.releasable 1 <-- shows 1 though the cgroup is not empty This patch removes the flag, and now debug.releasable shows if the cgroup is empty or not. Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit a25eb52e81a40e986179a790fbb5a1f02f482b7a) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I18a6ceea176da44ba2afa4aa09678b09e7329b9e Reviewed-on: https://chromium-review.googlesource.com/359888 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359888" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/88/359888/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I263322417e4008d5c46735d5cda58cb38787cd03" commit="a325fa5239de99fac4dcc23010d9e57433aceb5f" commit_message="UPSTREAM: cgroup: fix missing unlock in cgroup_release_agent() The patch 971ff4935538: "cgroup: use a per-cgroup work for release agent" from Sep 18, 2014, leads to the following static checker warning: kernel/cgroup.c:5310 cgroup_release_agent() warn: 'mutex:&cgroup_mutex' is sometimes locked here and sometimes unlocked. Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Zefan Li <lizefan@huawei.com> Signed-off-by: Tejun Heo <tj@kernel.org> BUG=b:29259708 TEST=Built and booted Minnie (cherry picked from commit 3e2cd91ab92665148616a80dc0745c499d2746a7) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Change-Id: I263322417e4008d5c46735d5cda58cb38787cd03 Reviewed-on: https://chromium-review.googlesource.com/359889 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359889" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/89/359889/1" remote="cros" total_fail_count="4"/><pending_commit branch="chromeos-3.14" change_id="I6bb4933d07e889d0dc39e33b4e71320c34a2c90f" commit="8a4f44842f3c3f2d74e622b95f316590b168adaf" commit_message="ANDROID: cgroup: refactor allow_attach function into common code move cpu_cgroup_allow_attach to a common subsys_cgroup_allow_attach. This allows any process with CAP_SYS_NICE to move tasks across cgroups if they use this function as their allow_attach handler. Bug: 18260435 Change-Id: I6bb4933d07e889d0dc39e33b4e71320c34a2c90f Signed-off-by: Rom Lemarchand <romlem@android.com> (cherry picked from commit 16474253cb671233c662ad89a88fee802dc36e15 in chromeos-3.18 tree, adjusted to compile) Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/359890 Reviewed-by: Dylan Reid <dgreid@chromium.org> " fail_count="4" gerrit_number="359890" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/90/359890/1" remote="cros" total_fail_count="4"/><pending_commit branch="master" change_id="I7142fb87a6ce0a20c571cde608fbbe60e35898ea" commit="d997487077546a9dd779e02f543693167d0f7e2a" commit_message="cts: Added GPIO test suite Contains code for all the gpio tests so far. Code in cts_task for th and dut is for testing purposes and test result reporting will be updated in the next patch. BRANCH=None BUG=None TEST=Manual - Connect handshake and gpio test lines between th and dut - Build tests - run 'cat /dev/ttyACM0' in one terminal - run 'cat /def/ttyACM1' in another - Flash boards - All test results should print either passed or unknown Change-Id: I7142fb87a6ce0a20c571cde608fbbe60e35898ea Reviewed-on: https://chromium-review.googlesource.com/359935 Commit-Ready: Daisuke Nojiri <dnojiri@chromium.org> Tested-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org> " fail_count="0" gerrit_number="359935" owner_email="twothreecc@google.com" pass_count="0" patch_number="7" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/35/359935/7" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I0c811405134fad04f5c6914b1ac38835e212cbd2" commit="b5dbc6247d17b84990db3eeced542bef2f694fd7" commit_message="cts: Use pointers for test functions Test functions are listed in cts.testlist and shared by th.c and dut.c. This way, we can gurantee the two files are in sync. Also, cts.testlist is used to count the number of tests automatically. This allows us to use a for loop to execute each test. BUG=none BRANCH=none TEST=build buildall Change-Id: I0c811405134fad04f5c6914b1ac38835e212cbd2 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/359619 " fail_count="0" gerrit_number="359619" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="8" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/19/359619/8" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8008fcf8ea5a429ec6c3bd2cc59fe86f43d87ada" commit="c600816b14507b2ed3ee39ab07f5c6ef92bc7f3c" commit_message="cts: Disambiguate enum cts_error_code BUG=none BRANCH=none TEST=make -j buildall Change-Id: I8008fcf8ea5a429ec6c3bd2cc59fe86f43d87ada Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/360180 Reviewed-by: Chris Chen <twothreecc@google.com> " fail_count="0" gerrit_number="360180" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="8" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/80/360180/8" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I21aded619098500382b0371d467806bc52c9f1db" commit="8a489f06d2944bba787d1d2e0e0c247c4315c36c" commit_message="ichspi: hwseq: Deny access to non-descriptor flash regions If a flash region is not covered by a descriptor region then it should not be available for access. Return SPI_ACCESS_DENIED in such cases. BUG=chrome-os-partner:53313 BRANCH=None TEST="flashrom -p host -r /tmp/test.bin" works on reef Change-Id: I21aded619098500382b0371d467806bc52c9f1db Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/360192 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="1" gerrit_number="360192" owner_email="furquan@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/flashrom" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/flashrom" ref="refs/changes/92/360192/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Id1ce7e37b6bba9cf065dade599c04577ee2d1702" commit="584edff11d5b4a8489fb80ff07e71f30de515b14" commit_message="flashrom: Add Apollolake platform support Currently, on Apollolake platform, the SPI PCI device is hidden in the OS. Thus, flashrom is not able to find the SPI device while walking the PCI tree. Thus, instead use the PCI ID of APL host bridge. In the callback for enabling APL flash, use mmio-based access to mmap SPI PCI device and work with it. BUG=chrome-os-partner:53313 BRANCH=None TEST="taskset 0x1 sudo flashrom -p host -r /tmp/test.bin" works fine. taskset 0x1 is currently required on A0 stepping of APL. On future platforms, this won't be required. Change-Id: Id1ce7e37b6bba9cf065dade599c04577ee2d1702 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://chromium-review.googlesource.com/359981 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> " fail_count="1" gerrit_number="359981" owner_email="furquan@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/flashrom" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/flashrom" ref="refs/changes/81/359981/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I9bd9292c5d760160e6ff23ae1c0d833fbac035d0" commit="714b930ff5d3a60d460ec0b3394a7266b91911d7" commit_message="media-libs/arc-mesa: Fixes for 12.1-devel A new pkgconfig package called PTHREADSTUBS is needed in upstream Mesa, so we need to add environment variables for them to workaround for the lack of pkgconfig. Also for -9999 ebuild we need to manually generate the git_sha1.h header. Since we cannot reliably determine the real revision and it is actually completely irrelevant for the build, let's just put some random value there. Moreover we are moving from swrast software backend to kms_swrast, so the ebuild has to be updated to install proper binary. By the way remove some extraneous variables confusing CROS_WORKON_INPLACE from working correctly. This makes it possible to build arc-mesa incrementally using cros_workon_make. BUG=b:29036398 TEST=emerge-cyan-cheets arc-mesa Change-Id: I9bd9292c5d760160e6ff23ae1c0d833fbac035d0 Reviewed-on: https://chromium-review.googlesource.com/348276 Commit-Ready: Puneet Kumar <puneetster@chromium.org> Tested-by: Tomasz Figa <tfiga@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> " fail_count="2" gerrit_number="348276" owner_email="tfiga@chromium.org" pass_count="0" patch_number="4" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/76/348276/4" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I6c21b61699cfab8d9fba93552e632873768c242c" commit="d00f7fff6b4ec4307fe08cb9ac23cddbc6f44f46" commit_message="archive_stages: Mark DebugStages as "Forgiven" on upload failure. In CIDB, we have been marking DebugSymbols as passing, even when the upload failed. This has made it hard to get any stats about how often the upload passes or fails. So.... now we treat the stage as failed, but Forgiven on upload failure. Any other error is still a failure. BUG=chromium:212437 TEST=./run_tests Change-Id: I6c21b61699cfab8d9fba93552e632873768c242c Reviewed-on: https://chromium-review.googlesource.com/359613 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> " fail_count="2" gerrit_number="359613" owner_email="dgarrett@chromium.org" pass_count="0" patch_number="1" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/13/359613/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Ib1a05d15e00356d72a1c687095fc309778ebffe7" commit="69b7ad853093900588ef70c5732c5c492c76d36b" commit_message="upload_symbols: Get rid of Counter class. Get rid of the Counter class, and instead use a SymbolFile status of ERROR. Also, converted PerformSymbolFileUpload to PerformSymbolFilesUpload which processes s series of SymbolFiles instead of just one. BUG=None TEST=Unitests. Change-Id: Ib1a05d15e00356d72a1c687095fc309778ebffe7 Reviewed-on: https://chromium-review.googlesource.com/358640 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Ningning Xia <nxia@chromium.org> " fail_count="0" gerrit_number="358640" owner_email="dgarrett@chromium.org" pass_count="0" patch_number="2" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/40/358640/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I7c7e600ce35c5ad6ea4ca9100c532392295773be" commit="19d2d671a21dd33c9d53c94aa22dccad6e90aa9b" commit_message="Export fingerprint list metadata in build image stage BUG=b:28964183 TEST=Trybot Change-Id: I7c7e600ce35c5ad6ea4ca9100c532392295773be Reviewed-on: https://chromium-review.googlesource.com/357530 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="357530" owner_email="bhthompson@chromium.org" pass_count="0" patch_number="2" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/30/357530/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I064641a2e43c0d1ba70265bca61abf736b7396de" commit="145d8293bc03d23e4ba513f778f3222423006427" commit_message="Include API keys in chrome gn build The chrome ebuild only set the API keys for the gyp build of chrome. Add them for the gn build as well. BUG=chromium:628432 TEST=emerge and deploy chromeos-chrome on samus and see that it doesn't show an 'API keys are missing' dialog anymore Change-Id: I064641a2e43c0d1ba70265bca61abf736b7396de Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/361001 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> " fail_count="0" gerrit_number="361001" owner_email="chirantan@chromium.org" pass_count="0" patch_number="2" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/01/361001/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie948d284cebad60d97aab1512bb9e3af8838004e" commit="3ed67c8b6c0df7e5aaf1220d7561aa6c059184e5" commit_message="cts: Add interrupt test It's imported from test/interrupt.c and adjusted to CTS. BUG=chromium:624520 BRANCH=none TEST=make buildall. Test passed on stm32l476-geval and nucleo-f072rb. Change-Id: Ie948d284cebad60d97aab1512bb9e3af8838004e Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/360660 Reviewed-by: Chris Chen <twothreecc@google.com> " fail_count="0" gerrit_number="360660" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/60/360660/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I70673f2c0f8316a2b1fd9472eeb7db350fdc2d84" commit="9cb79a9c57ffee93887add80898d433275b5a53a" commit_message="cts: Add hook test It's imported from test/hooks.c and adjusted to CTS. BUG=chromium:624520 BRANCH=none TEST=make buildall. Test passed on stm32l476-geval and nucleo-f072rb. Change-Id: I70673f2c0f8316a2b1fd9472eeb7db350fdc2d84 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/360631 Reviewed-by: Chris Chen <twothreecc@google.com> " fail_count="0" gerrit_number="360631" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/31/360631/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="If026b67586d18fea478801daf6df13f624a610b0" commit="5e6166dc6a814fcb008a04c32bd565a698c64aa1" commit_message="[autotest] Add retry to adb command passed but return value failed to be parsed. For some reason, an adb command can pass but the return value is not in the desired format of "ADB_CMD_OUTPUT:<value>" BUG=b:29759939 TEST=local run command through adb_host Change-Id: If026b67586d18fea478801daf6df13f624a610b0 Reviewed-on: https://chromium-review.googlesource.com/361021 Commit-Ready: Dan Shi <dshi@google.com> Tested-by: Dan Shi <dshi@google.com> Reviewed-by: Bindu Mahadev <bmahadev@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org> " fail_count="0" gerrit_number="361021" owner_email="dshi@google.com" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/21/361021/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ib7e2c3836dc958ec65b695b1dc5eb3ed542b3667" commit="6ef4b73a80334c2295b9d160fe46b1096f42685c" commit_message="Fix chromiumos-sdk bot breakage The version of ncurses in the stage3 tarball is too old and causes slot conflicts when we try to setup the toolchains during a bootstrap. Manually update ncurses to the latest version, which can gracefully handle the slot changes. BUG=chromium:627974 TEST='cbuildbot --remote chromiumos-sdk' is green Change-Id: Ib7e2c3836dc958ec65b695b1dc5eb3ed542b3667 Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/360324 Reviewed-by: David James <davidjames@chromium.org> " fail_count="1" gerrit_number="360324" owner_email="chirantan@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/crosutils" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosutils" ref="refs/changes/24/360324/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I5efa645615190463da068cf047908d94db2f18aa" commit="6230aa4c6d5859f25fa4f306b6af964291b8d57c" commit_message="[Interop_chaos]Fix scanning on the packet capturer. If the packet capturere is a whirwind use the aux radio interface 'wlan2' which is dual band, for scanning purposes. BUG=chromium:623641 TEST=Tested locally Change-Id: I5efa645615190463da068cf047908d94db2f18aa Reviewed-on: https://chromium-review.googlesource.com/360640 Commit-Ready: Bindu Mahadev <bmahadev@chromium.org> Tested-by: Bindu Mahadev <bmahadev@chromium.org> Reviewed-by: Kris Rambish <krisr@chromium.org> " fail_count="1" gerrit_number="360640" owner_email="bmahadev@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/40/360640/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I41223cd2e4f1ea5d0185528925311f91d366b244" commit="079e071c35016f32e96ac409966aee8c52ad87ca" commit_message="Adding chrome w/ arc tests to bvt-cq. We will remove these tests from arc-bvt-cq once we find that these tests aren't causing any problem in bvt-cq. BUG=b:28889821, b:30089172 TEST=None Change-Id: I41223cd2e4f1ea5d0185528925311f91d366b244 Reviewed-on: https://chromium-review.googlesource.com/360344 Commit-Ready: Rohit Makasana <rohitbm@chromium.org> Tested-by: Rohit Makasana <rohitbm@chromium.org> Reviewed-by: Rohit Makasana <rohitbm@chromium.org> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="360344" owner_email="rohitbm@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/44/360344/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I8cab0541ecbb1daa26b4d728fbd3e45e903ee512" commit="4a6e1c99b55f994a553a6348b2de84aec290d30a" commit_message="cts: Add mutext test It's imported from test/mutex.c and adjusted to CTS. BUG=chromium:624520 BRANCH=none TEST=Test passed on stm32l476-geval and nucleo-f072rb. make -j buildall Change-Id: I8cab0541ecbb1daa26b4d728fbd3e45e903ee512 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/360600 Reviewed-by: Chris Chen <twothreecc@google.com> " fail_count="0" gerrit_number="360600" owner_email="dnojiri@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/00/360600/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I61ff857edf28b973d8241a275456219782f2ff03" commit="26b8ec29948b29f99ca30da5ef045bf9132eafe5" commit_message="[autotest] Added per-host ssh parameters. Parameters are stored as host attributes ssh_user, ssh_port, ssh_verbosity_flag and ssh_options. Password is intentionally not stored. The verbosity flag and options are only used by CrosHost. No modifications necessary to ssh host objects because they already receive and utilize the parameters. Only modified factory to pull arguments from attributes before using existing defaults. Testbed and ADBHost were modified to pass the arguments through. Also fixed typo in factory and added tests. Modified atest host create to pass simulated afe_host so that detection of parameters by host attributes works even before the attributes are in afe. BUG=chromium:620196 TEST=Unit tests of changes to factory, confirmed manually locally and on moblab. Change-Id: I61ff857edf28b973d8241a275456219782f2ff03 Reviewed-on: https://chromium-review.googlesource.com/353040 Commit-Ready: Justin Giorgi <jgiorgi@google.com> Tested-by: Justin Giorgi <jgiorgi@google.com> Reviewed-by: Justin Giorgi <jgiorgi@google.com> " fail_count="1" gerrit_number="353040" owner_email="jgiorgi@google.com" pass_count="0" patch_number="8" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/40/353040/8" remote="cros" total_fail_count="3"/><lkgm version="8592.0.0-rc3"/></manifest> |
