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=-3.8 required=3.0 tests=BAYES_00, 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 18743C433DB for ; Sat, 27 Feb 2021 17:33:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D400D64E29 for ; Sat, 27 Feb 2021 17:33:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230169AbhB0Rbq (ORCPT ); Sat, 27 Feb 2021 12:31:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230210AbhB0RTz (ORCPT ); Sat, 27 Feb 2021 12:19:55 -0500 Received: from zeniv-ca.linux.org.uk (zeniv-ca.linux.org.uk [IPv6:2607:5300:60:148a::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A85AC06174A; Sat, 27 Feb 2021 09:19:02 -0800 (PST) Received: from viro by zeniv-ca.linux.org.uk with local (Exim 4.94 #2 (Red Hat Linux)) id 1lG3Ex-001QwC-As; Sat, 27 Feb 2021 17:18:51 +0000 Date: Sat, 27 Feb 2021 17:18:51 +0000 From: Al Viro To: Linus Torvalds Cc: Linux Kernel Mailing List , linux-fsdevel Subject: Re: [git pull] vfs.git misc stuff Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Al Viro Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 27, 2021 at 08:21:55AM -0800, Linus Torvalds wrote: > On Fri, Feb 26, 2021 at 10:00 PM Al Viro wrote: > > > > Al Viro (3): > > 9p: fix misuse of sscanf() in v9fs_stat2inode() > > Hmm. Technically this changes some of the rules. It used to check that > i tall fit in 32 bytes. Now there could be arbitrary spaces in there > that pushes it over the limit. > > I don't think we care, but.. I doubt that something was sending "HARDLINKCOUNT 123" *and* relying upon the truncation to have that parsed as 1 rather than 123...