From b57c7cd1c17616ae9db5614525ba703f384afd05 Mon Sep 17 00:00:00 2001
From: Christoph Hellwig <hch@lst.de>
Date: Tue, 20 Jun 2023 13:32:30 +0200
Subject: [PATCH] io_uring: remove a confusing comment above io_file_get_flags
Git-commit: b57c7cd1c17616ae9db5614525ba703f384afd05
Patch-mainline: v6.5-rc1
References: bsc#1215211
The SCM inflight mechanism has nothing to do with the fact that a file
might be a regular file or not and if it supports non-blocking
operations.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20230620113235.920399-4-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Gabriel Krisman Bertazi <krisman@suse.de>
---
io_uring/io_uring.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index 2d13f636de93..79f3cabec5b9 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -1766,11 +1766,6 @@ static void io_iopoll_req_issued(struct io_kiocb *req, unsigned int issue_flags)
}
}
-/*
- * If we tracked the file through the SCM inflight mechanism, we could support
- * any file. For now, just ensure that anything potentially problematic is done
- * inline.
- */
unsigned int io_file_get_flags(struct file *file)
{
unsigned int res = 0;
--
2.42.0