From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Fabian Frederick <fabf@skynet.be>,
linux-kernel <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
jfs-discussion@lists.sourceforge.net
Subject: Re: [Jfs-discussion] [PATCH 1/1] fs/jfs/jfs_inode.c: atomically set inode->i_flags
Date: Wed, 02 Apr 2014 13:00:27 -0500 [thread overview]
Message-ID: <533C503B.7000007@oracle.com> (raw)
In-Reply-To: <20140402174707.GK6901@thunk.org>
On 04/02/2014 12:47 PM, Theodore Ts'o wrote:
> On Wed, Apr 02, 2014 at 07:29:50PM +0200, Fabian Frederick wrote:
>> + set_mask_bits(&inode->i_flags, S_IMMUTABLE | S_APPEND | S_NOATIME |
>> + S_DIRSYNC | S_SYNC, new_fl);
>
> Warning --- per discussion with Linus over the weekend, he decided he
> really didn't like the set_mask_bits() interface, because it was too
> prone to abuse. Unfortuantely, Linus had already included an earlier
> version of my patch that used set_mask_bits() in 3.14 without letting
> me know. This is what I have in my ext4 tree for the merge window,
> which is undergoing final testing at the moment. This will cause a
> patch conflict, and it's likely (given Linus's dislike of the
> set_mask_bits interface) that set_mask_bits() will end up getting
> removed from the tree, if not when he fixes up the merge conflict, but
> subsequent to -rc1.
Thanks Ted. I'll wait until the ext4 piece is resolved before merging
this one.
Fabian, feel free to resubmit the patch based on Ted's revision.
Otherwise, I'll fix it up myself.
Thanks,
Shaggy
next prev parent reply other threads:[~2014-04-02 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 17:29 [PATCH 1/1] fs/jfs/jfs_inode.c: atomically set inode->i_flags Fabian Frederick
2014-04-02 17:47 ` Theodore Ts'o
2014-04-02 18:00 ` Dave Kleikamp [this message]
2014-04-02 18:08 ` Fabian Frederick
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=533C503B.7000007@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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