From: <gregkh@linuxfoundation.org>
To: fabf@skynet.be, gregkh@linuxfoundation.org, viro@zeniv.linux.org.uk
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "fs/ufs: restore s_lock mutex_init()" has been added to the 4.0-stable tree
Date: Wed, 08 Jul 2015 14:48:57 -0700 [thread overview]
Message-ID: <1436392137180194@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
fs/ufs: restore s_lock mutex_init()
to the 4.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
fs-ufs-restore-s_lock-mutex_init.patch
and it can be found in the queue-4.0 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From e4f95517f18271b1da36cfc5d700e46844396d6e Mon Sep 17 00:00:00 2001
From: Fabian Frederick <fabf@skynet.be>
Date: Wed, 17 Jun 2015 18:15:45 +0200
Subject: fs/ufs: restore s_lock mutex_init()
From: Fabian Frederick <fabf@skynet.be>
commit e4f95517f18271b1da36cfc5d700e46844396d6e upstream.
Add last missing line in commit "cdd9eefdf905"
("fs/ufs: restore s_lock mutex")
Signed-off-by: Fabian Frederick <fabf@skynet.be>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/ufs/super.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/ufs/super.c
+++ b/fs/ufs/super.c
@@ -801,6 +801,7 @@ static int ufs_fill_super(struct super_b
UFSD("flag %u\n", (int)(sb->s_flags & MS_RDONLY));
mutex_init(&sbi->mutex);
+ mutex_init(&sbi->s_lock);
spin_lock_init(&sbi->work_lock);
INIT_DELAYED_WORK(&sbi->sync_work, delayed_sync_fs);
/*
Patches currently in stable-queue which might be from fabf@skynet.be are
queue-4.0/ufs-fix-possible-deadlock-when-looking-up-directories.patch
queue-4.0/fs-ufs-restore-s_lock-mutex.patch
queue-4.0/fs-ufs-revert-ufs-fix-deadlocks-introduced-by-sb-mutex-merge.patch
queue-4.0/fs-ufs-restore-s_lock-mutex_init.patch
reply other threads:[~2015-07-08 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1436392137180194@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fabf@skynet.be \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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 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.