linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the vfs tree
Date: Mon, 12 Apr 2021 15:07:56 +0200	[thread overview]
Message-ID: <CAOssrKdAmeVK_uwLCDo_ZT52vOzxSU9X=orgzU6RB088L6OdKA@mail.gmail.com> (raw)
In-Reply-To: <20210412214730.2dbbcdff@canb.auug.org.au>

Hi Al,

Fixed fileattr branch pushed to:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git fileattr_v6

Thanks,
Miklos

On Mon, Apr 12, 2021 at 1:47 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the vfs tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/filesystems/locking.rst:113: WARNING: Malformed table.
> Text in column margin in table line 24.
>
> ============    =============================================
> ops             i_rwsem(inode)
> ============    =============================================
> lookup:         shared
> create:         exclusive
> link:           exclusive (both)
> mknod:          exclusive
> symlink:        exclusive
> mkdir:          exclusive
> unlink:         exclusive (both)
> rmdir:          exclusive (both)(see below)
> rename:         exclusive (all) (see below)
> readlink:       no
> get_link:       no
> setattr:        exclusive
> permission:     no (may not block if called in rcu-walk mode)
> get_acl:        no
> getattr:        no
> listxattr:      no
> fiemap:         no
> update_time:    no
> atomic_open:    shared (exclusive if O_CREAT is set in open flags)
> tmpfile:        no
> fileattr_get:   no or exclusive
> fileattr_set:   exclusive
> ============    =============================================
>
> Introduced by commit
>
>   10a489bbff3e ("vfs: add fileattr ops")
>
> --
> Cheers,
> Stephen Rothwell


  reply	other threads:[~2021-04-12 13:08 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 11:47 linux-next: build warning after merge of the vfs tree Stephen Rothwell
2021-04-12 13:07 ` Miklos Szeredi [this message]
2021-04-15 21:19   ` Al Viro
  -- strict thread matches above, loose matches on Subject: below --
2021-01-06 23:15 Stephen Rothwell
2021-01-07  0:37 ` Gao Xiang
2021-01-07  0:40 ` Al Viro
2020-09-24  1:40 Stephen Rothwell
2020-09-24  2:00 ` Al Viro
2020-06-16  0:21 Stephen Rothwell
2020-03-09 22:59 Stephen Rothwell
2020-03-09 23:17 ` Pali Rohár
2020-03-09 23:36   ` Namjae Jeon
2020-03-10 10:32     ` 'Greg Kroah-Hartman'
2019-02-03 22:33 Stephen Rothwell
2019-03-18  0:00 ` Stephen Rothwell
2019-03-25 23:05   ` Stephen Rothwell
2018-09-06  0:02 Stephen Rothwell
2018-09-07  8:57 ` David Howells
2018-06-19  1:53 Stephen Rothwell
2018-06-19  1:29 Stephen Rothwell
2018-05-17  0:39 Stephen Rothwell
2018-05-17  6:41 ` Christoph Hellwig
2018-05-14  0:56 Stephen Rothwell
2017-09-07 23:25 Stephen Rothwell
2017-09-08  5:53 ` Dmitry V. Levin
2017-09-14  1:51 ` Stephen Rothwell
2017-07-03  0:53 Stephen Rothwell
2017-07-09 23:34 ` Stephen Rothwell
2015-04-13  4:00 Stephen Rothwell
2012-10-12  5:06 Stephen Rothwell
2012-09-25  1:52 Stephen Rothwell
2012-01-05  6:35 Stephen Rothwell
2012-01-05  8:06 ` Al Viro
2012-01-05  8:14   ` Al Viro
2012-01-05 11:34     ` Jan Kara
2012-01-05  8:14   ` Stephen Rothwell
2012-01-05  8:19     ` Al Viro
2011-07-18  5:04 Stephen Rothwell
2011-07-18  5:17 ` Al Viro
2011-07-18  5:20   ` Al Viro
2010-07-05  0:01 Stephen Rothwell
2010-07-05  8:10 ` Al Viro
2010-07-05 10:44   ` Stephen Rothwell
2010-07-05 12:15   ` Jeff Layton

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='CAOssrKdAmeVK_uwLCDo_ZT52vOzxSU9X=orgzU6RB088L6OdKA@mail.gmail.com' \
    --to=mszeredi@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).