From: Al Viro <viro@ZenIV.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@linux-foundation.org, autofs@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [PATCH] Make stat/lstat/fstatat pass AT_NO_AUTOMOUNT to vfs_statx()
Date: Fri, 5 May 2017 00:53:27 +0100 [thread overview]
Message-ID: <20170504235326.GL29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <149393701678.21194.2478177197944898836.stgit@warthog.procyon.org.uk>
On Thu, May 04, 2017 at 11:30:16PM +0100, David Howells wrote:
> stat/lstat/fstatat need to pass AT_NO_AUTOMOUNT to vfs_statx() as the
> pre-statx code didn't set LOOKUP_AUTOMOUNT, even though fstatat() accepted
> the AT_NO_AUTOMOUNT flag.
Applied.
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@linux-foundation.org, autofs@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [PATCH] Make stat/lstat/fstatat pass AT_NO_AUTOMOUNT to vfs_statx()
Date: Fri, 5 May 2017 00:53:27 +0100 [thread overview]
Message-ID: <20170504235326.GL29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <149393701678.21194.2478177197944898836.stgit@warthog.procyon.org.uk>
On Thu, May 04, 2017 at 11:30:16PM +0100, David Howells wrote:
> stat/lstat/fstatat need to pass AT_NO_AUTOMOUNT to vfs_statx() as the
> pre-statx code didn't set LOOKUP_AUTOMOUNT, even though fstatat() accepted
> the AT_NO_AUTOMOUNT flag.
Applied.
next prev parent reply other threads:[~2017-05-04 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 22:30 [PATCH] Make stat/lstat/fstatat pass AT_NO_AUTOMOUNT to vfs_statx() David Howells
2017-05-04 22:30 ` David Howells
2017-05-04 23:53 ` Al Viro [this message]
2017-05-04 23:53 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170504235326.GL29622@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=autofs@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.