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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5525DC433F5 for ; Thu, 29 Sep 2022 16:17:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236074AbiI2QQ4 (ORCPT ); Thu, 29 Sep 2022 12:16:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234737AbiI2QQh (ORCPT ); Thu, 29 Sep 2022 12:16:37 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D116BFAC9 for ; Thu, 29 Sep 2022 09:16:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664468195; 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=SK8jnl25GfBurW867juBk8Hvi+Y8sy3LVuiGjVel2EA=; b=JfY+UIzSZrkUD4yb993CbyErlacwwcF/pLjE6aHASlVRvQh4ctq0ce6DBRUoIsEI8DnUuH xFPC/m1ebwHcDalpsJpsf+zZAAi4ouVA3fSK5xI9dgka8GRcq4ikDOB5Q1aSZfv3ODTL77 izB83lwj5U/zNJFjc/QgAy7gdMom6G0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-590-tWxvPbKKOv-UAw5fd6zNXg-1; Thu, 29 Sep 2022 12:16:32 -0400 X-MC-Unique: tWxvPbKKOv-UAw5fd6zNXg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D5441868A2E; Thu, 29 Sep 2022 16:16:31 +0000 (UTC) Received: from starship (unknown [10.40.193.233]) by smtp.corp.redhat.com (Postfix) with ESMTP id 33A50140EBF4; Thu, 29 Sep 2022 16:16:30 +0000 (UTC) Message-ID: Subject: Re: Commit 'iomap: add support for dma aligned direct-io' causes qemu/KVM boot failures From: Maxim Levitsky To: Keith Busch Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Christoph Hellwig , qemu-devel@nongnu.org, kvm@vger.kernel.org Date: Thu, 29 Sep 2022 19:16:29 +0300 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2022-09-29 at 09:48 -0600, Keith Busch wrote: > I am aware, and I've submitted the fix to qemu here: > > https://lists.nongnu.org/archive/html/qemu-block/2022-09/msg00398.html > Thanks for quick response! Question is though, isn't this an kernel ABI breakage? (I myself don't care, I would be happy to patch my qemu), but I afraid that this will break *lots* of users that only updated the kernel and not the qemu. What do you think? Best regards, Maxim Levitsky