diff options
| author | Peter Xu <peterx@redhat.com> | 2020-04-07 21:40:10 -0400 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-04-07 19:34:31 -0700 |
| commit | c7b6a566b98524baea6a244186e665d22b633545 (patch) | |
| tree | 00b778f01a2928b56a1221a1e291b06089ff8833 /drivers/leds/Kconfig | |
| parent | ba841078cd0557b43b59c63f5c048b12168f0db2 (diff) | |
| download | linux-c7b6a566b98524baea6a244186e665d22b633545.tar.bz2 | |
mm/gup: Mark lock taken only after a successful retake
It's definitely incorrect to mark the lock as taken even if
down_read_killable() failed.
This wass overlooked when we switched from down_read() to
down_read_killable() because down_read() won't fail while
down_read_killable() could.
Fixes: 71335f37c5e8 ("mm/gup: allow to react to fatal signals")
Reported-by: syzbot+a8c70b7f3579fc0587dc@syzkaller.appspotmail.com
Signed-off-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/leds/Kconfig')
0 files changed, 0 insertions, 0 deletions