Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp645329ybh; Wed, 15 Jul 2020 11:20:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJya0p+cmU5qrX2BkXEZc2fsAVY0SeR2i4wQNUzKTajHN/v8PKOXXuEg7EPKUsyG9IQrvEBr X-Received: by 2002:aa7:d1c8:: with SMTP id g8mr862598edp.337.1594837239586; Wed, 15 Jul 2020 11:20:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594837239; cv=none; d=google.com; s=arc-20160816; b=uGPWIUw+SU+DVgchrZ4sOozxu80K3bezutcs7qw1TQj+Z3VAHOx8Beh/kl2TKHXqBr RJh6J9q29VR5iWCbTCOgz8YVkTcosPlDgvvL1+G37ptiTZR6e8MP/qfeob9lXIspkoJo pleMs1mcCv53wunshA7dCDgnaeWkvQVJoe15GA/JtSz3gqnL7QW1seSQdj8dm6L/1sTq jr68ANZqAmi3VNc1ebzeEGNw7mmbG8xCHYt8foX6Bxi/o40Ft80dNwhoYzKz/W5EQ6zh 6RYgdGbEWGuUwkn3zrqA/5Ma4NSkkGC4SPpZQiKf+0YG/EG8DXvMsRp7cn9r7LM9YkJO HSNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=6R29tk8StEz7i4/DEBl236hOTubleGx7aou7XrLwBA0=; b=ZeJgjsYN95prfH1oDj3EfKsQqA+eFlJnby8Q210dVfYSFQYU4X01DGszif2vHjcoOu An5rvLxGpImIba66jK4k9hT3KjQeEVWuevcOpdE9DrJWSD+skIHdt9DDu/xp6Ryp7qvf z3EUm9lZgBmXJLEivXoyTEYDw8/8LnYF28HSf8zJnwdOr01mre8dUUbl4X9ruJSPa1kB 7zXSxnAHjzOasyDD6w/gfFysnKqaXRFrJTg9Vm38kZlQGiqT1kbW/2Yh7+oMyN66pZoe SPfKWZSiRP25zYpEOXhiD9tJTDsz5UqAYzXcg4KrY/9H0XoIdQYl63VIX/GE6V+ju5ny 5R4g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id si13si1747149ejb.188.2020.07.15.11.20.16; Wed, 15 Jul 2020 11:20:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726803AbgGOSTy (ORCPT + 99 others); Wed, 15 Jul 2020 14:19:54 -0400 Received: from verein.lst.de ([213.95.11.211]:60094 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725861AbgGOSTx (ORCPT ); Wed, 15 Jul 2020 14:19:53 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 254CC68AFE; Wed, 15 Jul 2020 20:19:50 +0200 (CEST) Date: Wed, 15 Jul 2020 20:19:49 +0200 From: Christoph Hellwig To: Dominique Martinet Cc: Christoph Hellwig , Doug Nazar , ericvh@gmail.com, lucho@ionkov.net, v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, syzbot+e6f77e16ff68b2434a2c@syzkaller.appspotmail.com Subject: Re: [PATCH] net/9p: validate fds in p9_fd_open Message-ID: <20200715181949.GA31172@lst.de> References: <20200710085722.435850-1-hch@lst.de> <5bee3e33-2400-2d85-080e-d10cd82b0d85@nazar.ca> <20200711104923.GA6584@nautica> <20200715073715.GA22899@lst.de> <20200715134756.GB22828@nautica> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200715134756.GB22828@nautica> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 15, 2020 at 03:47:56PM +0200, Dominique Martinet wrote: > Christoph Hellwig wrote on Wed, Jul 15, 2020: > > FYI, this is now generating daily syzbot reports, so I'd love to see > > the fix going into Linus' tree ASAP.. > > Yes, I'm getting some syzbot warnings as well now. > > I had however only planned to get this in linux-next, since that is what > the syzbot mails were complaining about, but I see this got into -rc5... > > > It's honestly just a warn on something that would fail anyway so I'd > rather let it live in -next first, I don't get why syzbot is so verbose > about this - it sent a mail when it found a c repro and one more once it > bisected the commit yesterday but it should not be sending more? Yes, I agree that this is just a warning on existing behavior. But then again these constant syzbot reports are pretty annoying.. > (likewise it should pick up the fix tag even if it only gets in -next, > or would it keep being noisy unless this gets merged to mainline?) > > > FWIW this is along with the 5 other patches I have queued for 5.9 > waiting for my tests as my infra is still down, I've stopped trying to > make promises, but I could push at least just this one to -next if that > really helps. > Sorry for that, things should be smoother once I've taken the time to > put things back in place. No need to be sorry, just through it might be worth to ping you. Thanks for all your help!