Received: by 10.223.185.116 with SMTP id b49csp4325829wrg; Tue, 6 Mar 2018 13:48:47 -0800 (PST) X-Google-Smtp-Source: AG47ELsdXnioZxC3n2cqDGM7858WBIoD8D8UZIlPJxK1X79LFj9DUdbXZjlIkK+bjZzAibOnBdYt X-Received: by 10.167.131.29 with SMTP id t29mr20506200pfm.116.1520372927530; Tue, 06 Mar 2018 13:48:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520372927; cv=none; d=google.com; s=arc-20160816; b=YJCVFlYxf04Yrb2S3ukonJ5OGfiRlxB3MdV8aFiyQy40ZkQ+UhLjX4SoIu3sVyAa+t QepW86vlXGWlcfTldNh8zTSz1GzQi34THa2ibfXjBR5Wpo3p4VknSmq714xupNpWUjv4 f7RQb82lUMVI2nJcT753U48nIQGwT4OgW0x4aeoTE4/HIyng7/cI93pM4zLz3/cqgCe1 leqg3bI92+abgXT8lkHHVUzLTwaHMflemuATTRLrNWKsuHrZkmyU/tW7zfigZrWvoWxL bpmO5NJU7Ch16iLpxzCvAWgioPUkfNV4vzpVK7JBpol8QeSootWEJAkZWbviKezFA4aN GHIw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:feedback-id:message-id:date:subject:cc:to :from:dkim-signature:dkim-signature:arc-authentication-results; bh=IyiNqQnHXWpsSyIvjVxIXgDhhCfvT/d40vSSmuCCMLI=; b=cv7E84VpH7t4+NsdMFJrKpIkdl5DSsQg4wjemp7cXe/Ec+jckVT/4S6X7pqza6/oiF a8aUmmJj4fsTfNuH9VuPusZ5b1ulNGFmjFsdWLexWHz3JySKEdq8A47oIgZZfQThtGoE VMXGCUn8YmlFXajiAWcDk9lczSLuUbVEZXH9dO2pScay0F+DWPl/3zeU8VFB37ugpcIW /qMPSq/GvT7y0CpKGXQqYSUdP15Yx4ug8DuEGi2hvISUHMOj9d0JgwzRh+tyxtCiRkKz 5tyoB4O5HJRWky2ck1fjEh3vrJ2OMRcTGQql8B4KzcG1mRUJ9m0Pb6ShcrLa0llIMUcY 9hPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@jcline.org header.s=rdybrs3533vx7mghocfwl3vdwgpl2v5u header.b=HyAGFc8B; dkim=pass header.i=@amazonses.com header.s=224i4yxa5dv7c2xz3womw6peuasteono header.b=W7dRuh3B; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w186si10323208pgd.745.2018.03.06.13.48.33; Tue, 06 Mar 2018 13:48:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@jcline.org header.s=rdybrs3533vx7mghocfwl3vdwgpl2v5u header.b=HyAGFc8B; dkim=pass header.i=@amazonses.com header.s=224i4yxa5dv7c2xz3womw6peuasteono header.b=W7dRuh3B; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754095AbeCFVre (ORCPT + 99 others); Tue, 6 Mar 2018 16:47:34 -0500 Received: from a8-61.smtp-out.amazonses.com ([54.240.8.61]:48334 "EHLO a8-61.smtp-out.amazonses.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753876AbeCFVrd (ORCPT ); Tue, 6 Mar 2018 16:47:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=rdybrs3533vx7mghocfwl3vdwgpl2v5u; d=jcline.org; t=1520372852; h=From:To:Cc:Subject:Date:Message-Id; bh=Qy7GrM0B/xuVdCYff6448JD/TqUAFESJbiys6XqTHDo=; b=HyAGFc8BinoI0+V3ORwhjTQQM3mH50jGSsctarShbjVThK3Xc/gPFdTWtMbfNPMv cDetX4cjCh/d29bB22lvsuQfJEb13krxojRT6DYJvhbN1DMmv2a7iaObwYLl19RB4h4 urFeNzpi6bxVHy1EGgpUnySS1hnE5AVUrfCqNST0= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1520372852; h=From:To:Cc:Subject:Date:Message-Id:Feedback-ID; bh=Qy7GrM0B/xuVdCYff6448JD/TqUAFESJbiys6XqTHDo=; b=W7dRuh3BKIQcfACuAfZu2IWXvmTu3Wbf/qFX+3uy+SgekPBzulnhR6tEdwEJHaGL aitxEHg3IC0swPlUyslDIFa0YUqXFLK+FC7x2uRJMxq5GYrCcz+nmlkoFpfepfHIFv/ S2JW9dnbxCHegoGpYf2N68ygpl0ySufWaVv1w28s= X-Virus-Scanned: amavisd-new at jcline.org From: Jeremy Cline To: "James E . J . Bottomley" , "Martin K . Petersen" Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, lining916740672@icloud.com, Jeremy Cline Subject: [PATCH v2] scsi: sd: Keep disk read-only when re-reading partition Date: Tue, 6 Mar 2018 21:47:32 +0000 Message-ID: <01000161fd48a4af-94cc485f-468a-404a-985e-7e8e50a358f0-000000@email.amazonses.com> X-Mailer: git-send-email 2.16.2 X-SES-Outgoing: 2018.03.06-54.240.8.61 Feedback-ID: 1.us-east-1.z18Isoc/FaoPOvCyJyi1mnTt8STwoRuibXVNoUcvG6g=:AmazonSES Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org If the read-only flag is true on a SCSI disk, re-reading the partition table sets the flag back to false. To observe this bug, you can run: 1. blockdev --setro /dev/sda 2. blockdev --rereadpt /dev/sda 3. blockdev --getro /dev/sda This commit reads the disk's old state and combines it with the device disk-reported state rather than unconditionally marking it as RW. Reported-by: Li Ning Signed-off-by: Jeremy Cline --- Sorry about this, but there's a bug in the first version of this patch. I'm not sure what the protocol is for sending revised patches when the earlier version got accepted, but I don't see the first version in 4.16/scsi-fixes yet. If I should make a patch on top of the v1 patch, just let me know. Changes in v2: - Don't save the value of "get_disk_ro" to "sdkp->write_prot" since, as Li Ning noticed, that causes a second bug: when you make the disk writable again with "blockdev --setrw /dev/sda" it isn't possible to write to the disk until the partition is re-read. drivers/scsi/sd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c index bff21e636ddd..3541caf3fceb 100644 --- a/drivers/scsi/sd.c +++ b/drivers/scsi/sd.c @@ -2595,6 +2595,7 @@ sd_read_write_protect_flag(struct scsi_disk *sdkp, unsigned char *buffer) int res; struct scsi_device *sdp = sdkp->device; struct scsi_mode_data data; + int disk_ro = get_disk_ro(sdkp->disk); int old_wp = sdkp->write_prot; set_disk_ro(sdkp->disk, 0); @@ -2635,7 +2636,7 @@ sd_read_write_protect_flag(struct scsi_disk *sdkp, unsigned char *buffer) "Test WP failed, assume Write Enabled\n"); } else { sdkp->write_prot = ((data.device_specific & 0x80) != 0); - set_disk_ro(sdkp->disk, sdkp->write_prot); + set_disk_ro(sdkp->disk, sdkp->write_prot || disk_ro); if (sdkp->first_scan || old_wp != sdkp->write_prot) { sd_printk(KERN_NOTICE, sdkp, "Write Protect is %s\n", sdkp->write_prot ? "on" : "off"); -- 2.16.2