aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/target/iscsi/cxgbit/cxgbit_cm.c
diff options
context:
space:
mode:
authorKenjiro Nakayama <nakayamakenjiro@gmail.com>2017-09-13 14:01:22 +0900
committerNicholas Bellinger <nab@linux-iscsi.org>2017-11-04 14:54:07 -0700
commitb849b4567549d5a54ab34ffacfd48fca05e8b34e (patch)
tree743c04ad802fa1c1b3a259f45fac0439174e2435 /drivers/target/iscsi/cxgbit/cxgbit_cm.c
parenttarget/tcmu: Use macro to call container_of in tcmu_cmd_time_out_show (diff)
downloadlinux-dev-b849b4567549d5a54ab34ffacfd48fca05e8b34e.tar.xz
linux-dev-b849b4567549d5a54ab34ffacfd48fca05e8b34e.zip
target: Add netlink command reply supported option for each device
Currently netlink command reply support option (TCMU_ATTR_SUPP_KERN_CMD_REPLY) can be enabled only on module scope. Because of that, once an application enables the netlink command reply support, all applications using target_core_user.ko would be expected to support the netlink reply. To make matters worse, users will not be able to add a device via configfs manually. To fix these issues, this patch adds an option to make netlink command reply disabled on each device through configfs. Original TCMU_ATTR_SUPP_KERN_CMD_REPLY is still enabled on module scope to keep backward-compatibility and used by default, however once users set nl_reply_supported=<NAGATIVE_VALUE> via configfs for a particular device, the device disables the netlink command reply support. Signed-off-by: Kenjiro Nakayama <nakayamakenjiro@gmail.com> Reviewed-by: Mike Christie <mchristi@redhat.com> Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'drivers/target/iscsi/cxgbit/cxgbit_cm.c')
0 files changed, 0 insertions, 0 deletions