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 CB280C433EF for ; Tue, 23 Nov 2021 06:16:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233626AbhKWGTI (ORCPT ); Tue, 23 Nov 2021 01:19:08 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:40192 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233564AbhKWGTH (ORCPT ); Tue, 23 Nov 2021 01:19:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1637648159; 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: in-reply-to:in-reply-to:references:references; bh=4zwLXwj6k9S2mIEl8JoRh6JXMNKqR5tGWTY9Pd3RcY4=; b=ErEx38P69NJZcrFE5I7LwTBtdzTSnJzdHj2sXvGFXLGVqkG5vdL7NvslugWgfGAqEbZ9dH 6eFclFeUjKBQEvjqiaQJLRsdESAQY15zYiX+wFdZN/yoa7akve9Rse76Ef72vw3Znwk9xJ sBCZforC23H3b+LC3C0aETqtQXaUfj4= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-390--8VdEw87Nmqoy7eGvq-jHw-1; Tue, 23 Nov 2021 01:15:57 -0500 X-MC-Unique: -8VdEw87Nmqoy7eGvq-jHw-1 Received: by mail-wm1-f70.google.com with SMTP id 205-20020a1c00d6000000b003335d1384f1so689794wma.3 for ; Mon, 22 Nov 2021 22:15:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=4zwLXwj6k9S2mIEl8JoRh6JXMNKqR5tGWTY9Pd3RcY4=; b=sz3UwzUF8nsJPplMCxe/Ymw7aqIuPr3fxfMhBiqod/f92Tx15p+CmEheTrfQvbUixI 1ZeFl+fwRFQOb9k2Zt0GocWaVE0bNXjazv2XpbUmHwbqDMGlm1Gp0ysELwFg2uAT1JNB JCSsdN2SzYBUVfOjY4UYBQnYo3tzJiEymlbfRcWZVWBAsIhg6bx6R033h+ek+iT3nLdL Uh5JrFPD0NKbJYrBYodRhQAxVsPLmZQ9/NLb+f+s+mVBrGCvlDWLLElNbb5BPCdLIKhk qHvcXrok4xkT3Wlllj+oOgxCnP9SVMwKwsZS693wXEWDCbu+cAHzKHNqlamP2Xibm1YI pilA== X-Gm-Message-State: AOAM531RvdUmM7kxknFdno5n5rqsWMUeX/oBKAuSn6fMTw6B8ISc+hRH ODr1jCUDIsy+FkkruKHnVd9kfbcMr4i1AGKj98euPpRUXV47dBbnH2T7VcTGpn6+5LzqzBUzpUb lGakbF9TKNfnBeEp0wAHPvvRZ X-Received: by 2002:adf:ef4f:: with SMTP id c15mr4390039wrp.226.1637648156131; Mon, 22 Nov 2021 22:15:56 -0800 (PST) X-Google-Smtp-Source: ABdhPJwCd6t13EbSY0ZWFB7yE27RLkDqYVVYmKx7kd9hky7A7ody0jIp7kwGr4IDGX9vk1Uty1OSnQ== X-Received: by 2002:adf:ef4f:: with SMTP id c15mr4390015wrp.226.1637648155984; Mon, 22 Nov 2021 22:15:55 -0800 (PST) Received: from redhat.com ([45.15.19.36]) by smtp.gmail.com with ESMTPSA id a10sm24151127wmq.27.2021.11.22.22.15.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Nov 2021 22:15:55 -0800 (PST) Date: Tue, 23 Nov 2021 01:15:51 -0500 From: "Michael S. Tsirkin" To: Arnaud Pouliquen Cc: Bjorn Andersson , Ohad Ben-Cohen , Mathieu Poirier , linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, Jason Wang Subject: Re: [PATCH] rpmsg: virtio: don't let virtio core to validate used length Message-ID: <20211123011340-mutt-send-email-mst@kernel.org> References: <20211122160812.25125-1-arnaud.pouliquen@foss.st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211122160812.25125-1-arnaud.pouliquen@foss.st.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 22, 2021 at 05:08:12PM +0100, Arnaud Pouliquen wrote: > For RX virtqueue, the used length is validated in all the three paths > (big, small and mergeable). For control vq, we never tries to use used > length. So this patch forbids the core to validate the used length. Jason commented on this. This is copy paste from virtio net where the change was merely an optimization. > Without patch the rpmsg client sample does not work. Hmm that's not enough of a description. Could you please provide more detail? Does rpmsg device set used length to a value > dma read buffer size? what kind of error message do you get? what are the plans to fix the device? > Fixes: 939779f5152d ("virtio_ring: validate used buffer length") > > Signed-off-by: Arnaud Pouliquen > Cc: Jason Wang > Cc: Michael S. Tsirkin > --- > base-commit: fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf > --- > drivers/rpmsg/virtio_rpmsg_bus.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c > index 9c112aa65040..5f73f19c2c38 100644 > --- a/drivers/rpmsg/virtio_rpmsg_bus.c > +++ b/drivers/rpmsg/virtio_rpmsg_bus.c > @@ -1054,6 +1054,7 @@ static struct virtio_driver virtio_ipc_driver = { > .feature_table_size = ARRAY_SIZE(features), > .driver.name = KBUILD_MODNAME, > .driver.owner = THIS_MODULE, > + .suppress_used_validation = true, > .id_table = id_table, > .probe = rpmsg_probe, > .remove = rpmsg_remove, > -- > 2.17.1