{"push_id":1288585896,"size":1,"distinct_size":1,"ref":"refs/heads/b_neo_stable_2.0","head":"25d2f0e22078d0ebcc6b3628ec038dd41f960c0b","before":"c2fce7ab2d0f65fadac7ae33a89aaee33e1272c0","commits":[{"sha":"25d2f0e22078d0ebcc6b3628ec038dd41f960c0b","author":{"name":"Andrew Perepechko","email":"e2878cd29bdffa86c5d49c1d4413e344197b0c0d@seagate.com"},"message":"MRP-3844 ldiskfs: always pre-allocate max depth for path\n\nThis patch is a port of LU-7980.\n\nUpon very specific meta-data and I/O pattern a situation can be\nencountered where ext_depth() will concurrently (due to i_data_sem\nrelease) grow outside of currently used ext4_ext_path[] array\nboundary.\nThis can lead to potential Slab overrun if current ext_depth()\nis used to index previously sized+allocated ext4_ext_path[] array.\nThis patch fixes this by already pre-allocating _ext_path[]\narray of the max possible depth.\n\nThis is an alternate way to avoid racy cases, that can lead to\nslab overrun, with current and unsafe implementation that causes\next4_ext_path[] array re-[sizing,allocation] based on current depth.\n\nNow unnecessay free an realloc upon depth change detection prior to\nreuse already allocated path space have also been removed.\n\nIntel-bug-id: LU-7980\nSigned-off-by: Bruno Faccini <bruno.faccini@intel.com>\nChange-Id: I0ae955c5eccf032cb02ef55c6381964a5eaf82c2\nReviewed-on: http://review.whamcloud.com/19349\nTested-by: Jenkins\nReviewed-by: Andreas Dilger <andreas.dilger@intel.com>\nTested-by: Maloo <hpdd-maloo@intel.com>\nReviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>\nReviewed-on: http://es-gerrit.xyus.xyratex.com:8080/12112\nTested-by: Alexander Lezhoev <alexander.lezhoev@seagate.com>\nReviewed-by: Alexander Zarochentsev <alexander.zarochentsev@seagate.com>\nReviewed-by: Vitaly Fertman <vitaly.fertman@seagate.com>","distinct":true,"url":"https://api.github.com/repos/Xyratex/lustre-stable/commits/25d2f0e22078d0ebcc6b3628ec038dd41f960c0b"}]}
{"actor":{"display_login":"MorpheusTeam"}}