cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: fix flock panic issue
Date: Tue, 22 Dec 2015 09:14:06 -0500 (EST)	[thread overview]
Message-ID: <1725877697.1870138.1450793646509.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1450772206-11805-1-git-send-email-junxiao.bi@oracle.com>

----- Original Message -----
> Commit 4f6563677ae8 ("Move locks API users to locks_lock_inode_wait()")
> move flock/posix lock indentify code to locks_lock_inode_wait(), but
> missed to set fl_flags to FL_FLOCK which will cause kernel panic in
> locks_lock_inode_wait().
> 
> Fixes: 4f6563677ae8 ("Move locks API users to locks_lock_inode_wait()")
> Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
> ---
>  fs/gfs2/file.c |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
> index 860408053c95..62b85802af2c 100644
> --- a/fs/gfs2/file.c
> +++ b/fs/gfs2/file.c
> @@ -1027,7 +1027,10 @@ static int do_flock(struct file *file, int cmd, struct
> file_lock *fl)
>  		if (fl_gh->gh_state == state)
>  			goto out;
>  		locks_lock_file_wait(file,
> -				     &(struct file_lock){.fl_type = F_UNLCK});
> +					&(struct file_lock) {
> +						.fl_type = F_UNLCK,
> +						.fl_flags = FL_FLOCK
> +					});
>  		gfs2_glock_dq(fl_gh);
>  		gfs2_holder_reinit(state, flags, fl_gh);
>  	} else {
> --
> 1.7.9.5
> 
> 

Hi,

Thanks. This is now applied to 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=a93a99838248bdab49db2eaac00236847670bc7f

Regards,

Bob Peterson
Red Hat File Systems



      reply	other threads:[~2015-12-22 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  8:16 [Cluster-devel] [PATCH] gfs2: fix flock panic issue Junxiao Bi
2015-12-22 14:14 ` Bob Peterson [this message]

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=1725877697.1870138.1450793646509.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 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).