From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2] GFS2: make sure S_NOSEC flag isn't overwritten
Date: Tue, 5 May 2015 14:42:32 -0400 (EDT) [thread overview]
Message-ID: <239477019.12334759.1430851352084.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1429124216-20451-1-git-send-email-bmarzins@redhat.com>
----- Original Message -----
> At the end of gfs2_set_inode_flags inode->i_flags is set to flags, so
> we should be mondifying flags instead of inode->i_flags, so it isn't
> overwritten.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
Hi,
The v2 version of the patch is now in the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=01e64ee40ad741037352d1d6202eaa432f833eb4
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2015-05-05 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 18:56 [Cluster-devel] [PATCH] GFS2: make sure S_NOSEC flag isn't overwritten Benjamin Marzinski
2015-04-15 19:16 ` Bob Peterson
2015-05-05 18:42 ` Bob Peterson [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-15 21:15 [Cluster-devel] [PATCH v2] " Benjamin Marzinski
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=239477019.12334759.1430851352084.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
/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.