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=-8.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 ABA7FC43381 for ; Thu, 14 Mar 2019 07:20:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6DE9A2063F for ; Thu, 14 Mar 2019 07:20:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="F914C4mP" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726812AbfCNHUR (ORCPT ); Thu, 14 Mar 2019 03:20:17 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:39949 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726464AbfCNHUR (ORCPT ); Thu, 14 Mar 2019 03:20:17 -0400 Received: by mail-qt1-f193.google.com with SMTP id f11so4934027qti.7 for ; Thu, 14 Mar 2019 00:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=9xCEOyneHddDTwozUVUQC1rUdiKwtYd3got1cZ42YRQ=; b=F914C4mP2xyf7loBdLq+DnGg3M9vs0GGtAShtYyiWJaGMajIh9S4ob2NJ1JJIcQuCW kFyUDJ3YZF6DLa8udzlPpKcIK4MPJmEOP4IKwm+JSL27e5fmR+1UfYM758nNYZSANsV3 K/ZHp4wDocqoKa3LJBZkCOAsT3eDO1Q1DsbdxhhD70M0DS8p7uUN6DUAmKaPBFwW4j+W Ph3JOj/q3s+G8g+nQUsvqZbfp3at0mbF2inwP2AKj5UlMar3Zi2psspGk6LbyVyt09mC 150EEbFyVCXP9B23jcD5pLcUQtAHspc0YywXS8a0yHdllyv+Zd4VzRwOzsRmEDV7YNty zUDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9xCEOyneHddDTwozUVUQC1rUdiKwtYd3got1cZ42YRQ=; b=DDex7HKX6VWHLIXGawEf7//a8clLQ1Gb3QS2+yL0Mww81WVpuTgUk9UsSAeU+nV5d5 UjTnvyLxTNb2Q0Vyk9EEtF3F17QoT97jmqONKI+Odxa+VHoKu11iVg7pg6Ous2dZQjuX 4gGi3EENRCO+Jb9rmkaZw7tAZTdY+0Su4rbB5zcdALPkTz13AIRPdkfS2XgG2vwMe0Nd AYESZfoPkzu0uhVaPxm/6mrM9I2YVkitJgOCCTGO14wz0desjCqWw7PBAoFKBeMYx47k sK/Yj5cUY7yNMQFcnbPvOasSicA1YemkjgRhsO9pvyoaoJQ6IcMlrhoBPhX8zCbQd/Cn ohkg== X-Gm-Message-State: APjAAAXFgtgl5wruaHeTZeWRXgWVcCDC25tCPqQUyga+hyTFMgH4mlw0 aHqZnCOjd1kAbrU+6aPqmUodeq3K23BJIEtcc0m/EI/V4DQ= X-Google-Smtp-Source: APXvYqzmDzh83Tn+umcxxex3JqAoMea9Nrb5DBScMhlS69u8/kZT3sCxXysNQwpDca5ij9efKSKNcgsvdrlBU3scLlU= X-Received: by 2002:ac8:1005:: with SMTP id z5mr3037080qti.205.1552548016389; Thu, 14 Mar 2019 00:20:16 -0700 (PDT) MIME-Version: 1.0 From: Murphy Zhou Date: Thu, 14 Mar 2019 15:20:05 +0800 Message-ID: Subject: mount(2) with NULL fstype returns ENOENT instead of EINVAL after introducing fs_context methods To: Linux-Fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Hi, Since this commit f3a09c92018a91ad0981146a4ac59414f814d801 Author: Al Viro Date: Sun Dec 23 18:55:56 2018 -0500 introduce fs_context methods Signed-off-by: Al Viro LTP[1] mount02 tests #5 starts to fail. This testcase is calling mount(2) with a NULL fs type. It's expecting EINVAL to PASS but now we are getting ENOENT. Should I fix the testcase or there is some work in the kernel ? I'm wring this email to confirm with you guys. Thanks, M [1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/mount/mount02.c