LKML: Dexuan Cui: Any known soft lockup issue with vfs_write()->fsnotify()?
Any known soft lockup issue with vfs_write()->fsnotify()? Hi, Recently people are getting a soft lock issue with vfs_write()->fsnotify(). The detailed calltrace is available at: https://github.com/coreos/bugs/issues/2356 https://github.com/coreos/bugs/issues/2364 The kernel versions showing up the issue are: 4.14.11-coreos 4.14.19-coreos 4.13.0-1009 -- this is the kernel with which I'm personally
kernel/git/jack/linux-fs.git - Ext2/3, UDF, quota tree
fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it appears that no precautions are taken in fsnotify_put_mark() to ensure that fsnotify() drops its reference to this fsnotify_mark_connector before assigning a value to its 'destroy_next' field. This can result in fsnotify_put_mark() assigning a value to a connector'
LKML: Greg Kroah-Hartman: [PATCH 4.16 64/81] fsnotify: Fix fsnotify_mark_connector race
[PATCH 4.16 64/81] fsnotify: Fix fsnotify_mark_connector race 4.16-stable review patch. If anyone has any objections, please let me know. ------------------ From: Robert Kolchmeyer <rkolchmeyer@google.com> commit d90a10e2444ba5a351fa695917258ff4c5709fa5 upstream. fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it a
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Bug #1765564 “fsnotify: Fix fsnotify_mark_connector race” : Bugs : linux-azure package : Ubuntu
