{"push_id":2411839504,"size":1,"distinct_size":1,"ref":"refs/heads/upstream","head":"97c1e0515cb4ea0a924d0593ef8bc0ba47ad9746","before":"8fa69a05244df1bf8a4ecfea83530f0e86fe28cc","commits":[{"sha":"97c1e0515cb4ea0a924d0593ef8bc0ba47ad9746","author":{"name":"Hugh Dickins","email":"11bd16bbccd141ee47d9426ad06afbc74b915cf0@google.com"},"message":"shmem: fix faulting into a hole while it's punched\n\ncommit f00cdc6df7d7cfcabb5b740911e6788cb0802bdb upstream.\n\nTrinity finds that mmap access to a hole while it's punched from shmem\ncan prevent the madvise(MADV_REMOVE) or fallocate(FALLOC_FL_PUNCH_HOLE)\nfrom completing, until the reader chooses to stop; with the puncher's\nhold on i_mutex locking out all other writers until it can complete.\n\nIt appears that the tmpfs fault path is too light in comparison with its\nhole-punching path, lacking an i_data_sem to obstruct it; but we don't\nwant to slow down the common case.\n\nExtend shmem_fallocate()'s existing range notification mechanism, so\nshmem_fault() can refrain from faulting pages into the hole while it's\npunched, waiting instead on i_mutex (when safe to sleep; or repeatedly\nfaulting when not).\n\n[akpm@linux-foundation.org: coding-style fixes]\nSigned-off-by: Hugh Dickins <hughd@google.com>\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nTested-by: Sasha Levin <sasha.levin@oracle.com>\nCc: Dave Jones <davej@redhat.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/ZERONATE/android_kernel_samsung_j5xnlte/commits/97c1e0515cb4ea0a924d0593ef8bc0ba47ad9746"}]}
{"actor":{"display_login":"DY3413"}}