From: Douglas Gilbert <dgilbert@interlog.com>
To: linux-scsi@vger.kernel.org
Cc: martin.petersen@oracle.com, jejb@linux.vnet.ibm.com, hare@suse.de
Subject: [PATCH v11 38/44] sg: warn v3 write system call users
Date: Wed, 14 Oct 2020 22:06:37 -0400 [thread overview]
Message-ID: <20201015020643.432908-39-dgilbert@interlog.com> (raw)
In-Reply-To: <20201015020643.432908-1-dgilbert@interlog.com>
Should generate one log message per kernel run when the write()
system call is used with the sg interface version 3. Due to
security concerns suggest that they use ioctl(SG_SUBMIT_v3)
instead.
Sg interface version 1 or 2 based code may also be calling
write() in this context. There is no easy solution for them
(short of upgrading their interface to version 3 or 4), so
don't produce a warning suggesting the conversion will be
simple.
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
---
drivers/scsi/sg.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/scsi/sg.c b/drivers/scsi/sg.c
index da10e6d32f53..b95eb87a3c43 100644
--- a/drivers/scsi/sg.c
+++ b/drivers/scsi/sg.c
@@ -645,6 +645,9 @@ sg_write(struct file *filp, const char __user *p, size_t count, loff_t *ppos)
__func__);
return -EPERM;
}
+ pr_warn_once("Please use %s instead of write(),\n%s\n",
+ "ioctl(SG_SUBMIT_V3)",
+ " See: http://sg.danny.cz/sg/sg_v40.html");
res = sg_v3_submit(filp, sfp, h3p, false, NULL);
return res < 0 ? res : (int)count;
}
--
2.25.1
next prev parent reply other threads:[~2020-10-15 2:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 2:05 [PATCH v11 00/44] sg: add v4 interface Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 01/44] sg: move functions around Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 02/44] sg: remove typedefs, type+formatting cleanup Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 03/44] sg: sg_log and is_enabled Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 04/44] sg: rework sg_poll(), minor changes Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 05/44] sg: bitops in sg_device Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 06/44] sg: make open count an atomic Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 07/44] sg: move header to uapi section Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 08/44] sg: speed sg_poll and sg_get_num_waiting Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 09/44] sg: sg_allow_if_err_recovery and renames Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 10/44] sg: improve naming Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 11/44] sg: change rwlock to spinlock Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 12/44] sg: ioctl handling Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 13/44] sg: split sg_read Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 14/44] sg: sg_common_write add structure for arguments Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 15/44] sg: rework sg_vma_fault Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 16/44] sg: rework sg_mmap Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 17/44] sg: replace sg_allow_access Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 18/44] sg: rework scatter gather handling Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 19/44] sg: introduce request state machine Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 20/44] sg: sg_find_srp_by_id Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 21/44] sg: sg_fill_request_element Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 22/44] sg: printk change %p to %pK Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 23/44] sg: xarray for fds in device Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 24/44] sg: xarray for reqs in fd Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 25/44] sg: replace rq array with xarray Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 26/44] sg: sense buffer rework Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 27/44] sg: add sg v4 interface support Douglas Gilbert
2020-10-15 13:42 ` Hannes Reinecke
2020-10-15 2:06 ` [PATCH v11 28/44] sg: rework debug info Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 29/44] sg: add 8 byte SCSI LUN to sg_scsi_id Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 30/44] sg: expand sg_comm_wr_t Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 31/44] sg: add sg_iosubmit_v3 and sg_ioreceive_v3 ioctls Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 32/44] sg: add some __must_hold macros Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 33/44] sg: move procfs objects to avoid forward decls Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 34/44] sg: protect multiple receivers Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 35/44] sg: first debugfs support Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 36/44] sg: rework mmap support Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 37/44] sg: defang allow_dio Douglas Gilbert
2020-10-15 2:06 ` Douglas Gilbert [this message]
2020-10-15 2:06 ` [PATCH v11 39/44] sg: add mmap_sz tracking Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 40/44] sg: remove rcv_done request state Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 41/44] sg: track lowest inactive and await indexes Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 42/44] sg: remove unit attention check for device changed Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 43/44] sg: no_dxfer: move to/from kernel buffers Douglas Gilbert
2020-10-15 2:06 ` [PATCH v11 44/44] sg: bump version to 4.0.11 Douglas Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201015020643.432908-39-dgilbert@interlog.com \
--to=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.