From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D90F7C43331 for ; Mon, 11 Nov 2019 10:39:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A700E20856 for ; Mon, 11 Nov 2019 10:39:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Q1Mxp3od" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726808AbfKKKjA (ORCPT ); Mon, 11 Nov 2019 05:39:00 -0500 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:26540 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726770AbfKKKjA (ORCPT ); Mon, 11 Nov 2019 05:39:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573468738; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DtJ5pv77U2r0G6ksqsSYckeZ6pvSP6wLt/Y5uCN51BI=; b=Q1Mxp3odtknFRKQ8QF88BEdp5eOZTaYPO2JsCyZBnLrD88EODg5q1SjqgMbzJriUfMjJlg qW0tOr+C6hDf3OUhGUbSbDt63360LnwAT7vx7rTZ0Cz3Fqh+Fq30Xc9IhOLR7vrG+P61Jx UBhoMhSrF2yMpsRmjrfCR8/G0d5/jsM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-268-S1iNAS8jNHuFSYbreh69fQ-1; Mon, 11 Nov 2019 05:38:56 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0D4F5107ACC4; Mon, 11 Nov 2019 10:38:55 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E5C755D6A3; Mon, 11 Nov 2019 10:38:54 +0000 (UTC) Received: from zmail17.collab.prod.int.phx2.redhat.com (zmail17.collab.prod.int.phx2.redhat.com [10.5.83.19]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id C14C94BB5C; Mon, 11 Nov 2019 10:38:54 +0000 (UTC) Date: Mon, 11 Nov 2019 05:38:54 -0500 (EST) From: Jan Stancek To: Christoph Hellwig Cc: "Darrick J. Wong" , Naresh Kamboju , LTP List , Linux-Next Mailing List , linux-fsdevel@vger.kernel.org, chrubis , open list , Al Viro , Mark Brown , Arnd Bergmann , lkft-triage@lists.linaro.org, linux-ext4 , Theodore Ts'o Message-ID: <1757087132.11450258.1573468734360.JavaMail.zimbra@redhat.com> In-Reply-To: <20191111083815.GA29540@infradead.org> References: <852514139.11036267.1573172443439.JavaMail.zimbra@redhat.com> <20191111012614.GC6235@magnolia> <1751469294.11431533.1573460380206.JavaMail.zimbra@redhat.com> <20191111083815.GA29540@infradead.org> Subject: Re: LTP: diotest4.c:476: read to read-only space. returns 0: Success MIME-Version: 1.0 X-Originating-IP: [10.43.17.163, 10.4.195.18] Thread-Topic: diotest4.c:476: read to read-only space. returns 0: Success Thread-Index: 910IB+66jrM2sMmDpKAiK7gJA7sQsg== X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: S1iNAS8jNHuFSYbreh69fQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org ----- Original Message ----- > Is this a new test? No, it's not new. > If not why was this never reported? Sounds like > we should add this test case to xfstests. I'm guessing not that many users still run 32bit kernels. Naresh' setup is using ext4, so I assume he noticed only after recent changes in linux-next wrt. directio and ext4. Regards, Jan