Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4265939imm; Wed, 30 May 2018 02:14:31 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIpmVzcU44+FeQU/0etN4szTjH5rHAwOMut5EjTjiKfnJJXnInAH7eF2AqIPYvEEJwMMsqc X-Received: by 2002:a62:4a0c:: with SMTP id x12-v6mr2025414pfa.142.1527671671268; Wed, 30 May 2018 02:14:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527671671; cv=none; d=google.com; s=arc-20160816; b=05nQtN6DHx//91GOSZntir5ZBQ07SEfzeYjBy3T1/ttN5qs30b6reNQQkZnJZXjuNn nZ+Dmwpt4rNXx9qE/JpWKkJR/hD/CuZDNJB4wHB6AFOykfDcoHvcdCa0aSvD0JEt5H5C MM6wcbkm3sZmtn8DrJXzM2jMn6xRXMq9aTvmYCQz/n9kP2Yu+5log8injtiUz9O1D3f2 FmCBib74JyqpVEW9ctNnBk/FnSGWVw8rWG19EJgIHZC889H1tf3lf0LTP0JzI5chyTJa KelBRjncw7ZGNBZEgCVqY2yftpl755Y+N17cmiTU6oMSnZs8/OuRK0MbLhLZaV7XdYvy wyRQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:message-id :mime-version:references:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=ZSCwqN+ytny8WFNi40n/55nUMiuo/XzuSsl0p/8hAJc=; b=ajt2pbYZpVH2YlVC57Jv/9KIbRYIUPPB56ymSreGfy4FCGtnMZ4EB8wu3SYyGlTt34 f2Zo/xCFvZGNoBRXBDaZRf7dRmZmfG/2lQZztSOWD9byCwDUyRxVKxKEhmR2huoFSu1W aEH6826Hxr6eiz/565dC9nOMXp/nkz/lYxL105bUj+m40ebPtNUEoaom8h+4Mf+0SvUE LvqJZnq2/XEs45CP9YZ0zIuEYPUFExre2NRoAKvtQIeGcSipngZ3dECJmPuAsEuLt6eR Oby4n709plyVs2QtW9FSAwksQrB7SI0VbUmnbp+1CblP5crV8Yj53lh0B9nwLpXi2TAA JynA== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 73-v6si6267554ple.157.2018.05.30.02.14.17; Wed, 30 May 2018 02:14:31 -0700 (PDT) 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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965282AbeE3JLw (ORCPT + 99 others); Wed, 30 May 2018 05:11:52 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:57672 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S968792AbeE3JLr (ORCPT ); Wed, 30 May 2018 05:11:47 -0400 Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4U96rIs067381 for ; Wed, 30 May 2018 05:11:46 -0400 Received: from e06smtp10.uk.ibm.com (e06smtp10.uk.ibm.com [195.75.94.106]) by mx0b-001b2d01.pphosted.com with ESMTP id 2j9s1k873r-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 30 May 2018 05:11:46 -0400 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 30 May 2018 10:11:44 +0100 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp10.uk.ibm.com (192.168.101.140) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 30 May 2018 10:11:42 +0100 Received: from d06av25.portsmouth.uk.ibm.com (d06av25.portsmouth.uk.ibm.com [9.149.105.61]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w4U9Bf7N25428158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 30 May 2018 09:11:41 GMT Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8696711C050; Wed, 30 May 2018 10:02:37 +0100 (BST) Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5E72311C04A; Wed, 30 May 2018 10:02:37 +0100 (BST) Received: from mschwideX1 (unknown [9.152.212.220]) by d06av25.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 30 May 2018 10:02:37 +0100 (BST) Date: Wed, 30 May 2018 11:11:40 +0200 From: Martin Schwidefsky To: Christoph Hellwig Cc: Linus Torvalds , linux-kernel , linux-s390 , Heiko Carstens Subject: Re: [GIT PULL] two more s390 bug fixes for 4.17 In-Reply-To: <20180530074130.GA6927@infradead.org> References: <20180530075920.1f73275a@mschwideX1> <20180530074130.GA6927@infradead.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-TM-AS-GCONF: 00 x-cbid: 18053009-0040-0000-0000-0000043F3B60 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18053009-0041-0000-0000-000026448E96 Message-Id: <20180530111140.40c791bd@mschwideX1> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-05-30_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=832 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805300107 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 30 May 2018 00:41:30 -0700 Christoph Hellwig wrote: > > - req->completion_data = cqr; > > + *((struct dasd_ccw_req **) blk_mq_rq_to_pdu(req)) = cqr; > > + > > Please don't play such tricks. In general your driver structure > should have struct request embedded. If for some reason > struct dasd_ccw_req has a different life time please create a new > structure instead of these hacks. Why do you consider this to be a 'trick'? The blk_mq_rq_to_pdu is meant to be used to access a block of data that is is associated with a request, no? With the change we store a single value, the pointer to a struct dasd_ccw_req. The struct request comes first, later do_dasd_request creates the struct dasd_ccw_req with the CCW chain for the request. And for the blk timeout handler we need a way to find the dasd_ccw_req again. > In either way this really doesn't look like a post-rc7 change. You think so? It fixes a crash for s390 with a minimal number of changed lines: drivers/s390/block/dasd.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.