diff options
author | Hans Verkuil <hverkuil-cisco@xs4all.nl> | 2023-08-17 13:41:32 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-10-06 14:16:16 +0300 |
commit | 1e1f2aeb733751d8c45be4cb7ea122bd7351f059 (patch) | |
tree | 3151f209715d5662bab1bfa0822aa3c962a39b4c /fs/nfs/nfs4proc.c | |
parent | 767176f849bfbeb1a7379a076d08441050a245a2 (diff) | |
download | linux-1e1f2aeb733751d8c45be4cb7ea122bd7351f059.tar.xz |
media: vb2: frame_vector.c: replace WARN_ONCE with a comment
[ Upstream commit 735de5caf79e06cc9fb96b1b4f4974674ae3e917 ]
The WARN_ONCE was issued also in cases that had nothing to do with VM_IO
(e.g. if the start address was just a random value and uaccess fails with
-EFAULT).
There are no reports of WARN_ONCE being issued for actual VM_IO cases, so
just drop it and instead add a note to the comment before the function.
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reported-by: Yikebaer Aizezi <yikebaer61@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/nfs/nfs4proc.c')
0 files changed, 0 insertions, 0 deletions