From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] several fixes
Date: Sun, 7 Sep 2014 18:35:57 +0100 [thread overview]
Message-ID: <20140907173557.GU7996@ZenIV.linux.org.uk> (raw)
Several bugfixes (all of them -stable fodder). Alexey's one deals with
double mutex_lock() in UFS (apparently, nobody has tried to test "ufs: sb mutex
merge + mutex_destroy" on something like file creation/removal on ufs -
it's a 100%-guaranteed deadlock). Mine deal with two kinds of umount bugs,
in umount propagation and in handling of automounted submounts, both
resulting in bogus transient EBUSY from umount. Please, pull from the
usual place:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (2):
get rid of propagate_umount() mistakenly treating slaves as busy.
fix EBUSY on umount() from MNT_SHRINKABLE
Alexey Khoroshilov (1):
ufs: fix deadlocks introduced by sb mutex merge
Diffstat:
fs/namespace.c | 10 +++++++++-
fs/pnode.c | 1 +
fs/ufs/inode.c | 7 ++-----
fs/ufs/namei.c | 14 ++++++--------
4 files changed, 18 insertions(+), 14 deletions(-)
next reply other threads:[~2014-09-07 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 17:35 Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-09 23:12 [git pull] several fixes Al Viro
2019-04-10 2:30 ` pr-tracker-bot
2011-03-16 14:42 Al Viro
2011-03-16 17:17 ` Miklos Szeredi
2011-03-16 17:42 ` Linus Torvalds
2011-03-16 18:17 ` Miklos Szeredi
2011-03-16 18:49 ` Linus Torvalds
2011-03-16 20:21 ` Al Viro
2011-03-16 20:29 ` Linus Torvalds
2011-03-16 19:51 ` Al Viro
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=20140907173557.GU7996@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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