From: Bart Van Assche <bart.vanassche@wdc.com>
To: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bart.vanassche@wdc.com>
Subject: [PATCH v3 0/3] Rework handling of scsi_device.vpd_pg8[03]
Date: Mon, 28 Aug 2017 13:41:46 -0700 [thread overview]
Message-ID: <20170828204149.28693-5-bart.vanassche@wdc.com> (raw)
In-Reply-To: <20170828204149.28693-1-bart.vanassche@wdc.com>
Hello Martin,
The conclusion of a recent discussion about the handling of SCSI device VPD
data is that the code should be reworked such that that data is freed through
kfree_rcu() instead of kfree(). The three patches in this series realize this
and also simplify the VPD code. Please consider these patches for kernel
v4.14.
Thanks,
Bart.
Changes between v2 and v3:
- Added a third patch that introduces rcu_swap_protected().
- Introduced scsi_update_vpd_page().
- Skip VPD buffer updating if querying VPD data fails.
- Fix a race condition in the VPD sysfs show method.
Changes between v1 and v2:
- Split the VPD rework into two patches.
- Introduced struct scsi_vpd and scsi_get_vpd_buf().
Bart Van Assche (3):
Rework the code for caching Vital Product Data (VPD)
Rework handling of scsi_device.vpd_pg8[03]
scsi_transport_sas: Fix error handling in sas_smp_request()
drivers/scsi/scsi.c | 140 ++++++++++++++++----------------------
drivers/scsi/scsi_lib.c | 16 ++---
drivers/scsi/scsi_sysfs.c | 29 +++++---
drivers/scsi/scsi_transport_sas.c | 6 +-
include/scsi/scsi_device.h | 18 +++--
5 files changed, 106 insertions(+), 103 deletions(-)
--
2.14.1
next prev parent reply other threads:[~2017-08-28 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 20:41 [PATCH v3 0/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
2017-08-28 20:41 ` [PATCH v3 1/3] Rework the code for caching Vital Product Data (VPD) Bart Van Assche
2017-08-29 6:25 ` Hannes Reinecke
2017-08-28 20:41 ` [PATCH v3 2/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
2017-08-29 6:33 ` Hannes Reinecke
2017-08-28 20:41 ` [PATCH v3 3/3] scsi_transport_sas: Fix error handling in sas_smp_request() Bart Van Assche
2017-08-28 20:41 ` Bart Van Assche [this message]
2017-08-28 20:41 ` [PATCH v3 1/3] Rework the code for caching Vital Product Data (VPD) Bart Van Assche
2017-08-28 20:41 ` [PATCH v3 2/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
2017-08-28 20:41 ` [PATCH v3 3/3] scsi_transport_sas: Fix error handling in sas_smp_request() Bart Van Assche
2017-08-29 13:08 ` Christoph Hellwig
2017-08-28 20:43 ` [PATCH v3 0/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 20:44 Bart Van Assche
2017-08-28 20:44 ` Bart Van Assche
2017-08-28 20:46 ` Bart Van Assche
2017-08-28 20:45 Bart Van Assche
2017-08-28 20:45 ` Bart Van Assche
2017-08-28 20:47 ` Bart Van Assche
2017-08-28 20:46 Bart Van Assche
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=20170828204149.28693-5-bart.vanassche@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox