All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git
Date: Wed, 28 May 2014 07:38:48 +0100	[thread overview]
Message-ID: <20140528063847.GX18016@ZenIV.linux.org.uk> (raw)

	Oh, well...  Still nothing useful on that livelock (I had something
that looked kinda-sorta like a non-invasive solution, but it deadlocks), so
it's just Miklos' vmsplice fix for now.  Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus

Shortlog:
Miklos Szeredi (1):
      vfs: fix vmplice_to_user()

Diffstat:
 fs/splice.c |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

PS: livelock looks triggerable without check_submounts_and_drop() anywhere
in sight - vfs_rmdir() does shrink_dcache_parent() on prospective victim
right before calling ->rmdir().  So rmdir a vs rmdir a/b/c will get you
shrink_dcache_parent() on a and a/b/c at the same time - no locks in common
there.  So we'll probably need to shift those calls after successful calls
of ->rmdir() (and similar in overwriting ->rename()), in addition to whatever
we cook in check_submounts_and_drop()...

I still would like to see detailed traces on what gets triggered by udev -
hopefully the patch I've sent to Mika won't disrupt the livelock by printks
it's doing ;-/

             reply	other threads:[~2014-05-28  6:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28  6:38 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-17  5:55 [git pull] vfs.git Al Viro
2016-11-11  6:05 Al Viro
2016-11-11 17:25 ` Linus Torvalds
2016-11-11 18:06   ` Ilya Dryomov
2016-11-12  3:36   ` Yan, Zheng
2016-10-11  3:07 Al Viro
2016-05-16  3:32 Al Viro
2016-05-16 15:43 ` Linus Torvalds
2016-05-17  6:27   ` Al Viro
2016-05-17 18:27     ` Linus Torvalds
2016-05-17 20:11       ` Al Viro
2016-03-20  1:44 Al Viro
2016-03-20  1:55 ` Linus Torvalds
2016-03-20  1:59   ` Al Viro
2015-04-24 20:40 Al Viro
2014-12-10 19:13 [GIT PULL] vfs.git Al Viro
2014-12-11 16:18 ` Miklos Szeredi
2014-12-11 18:06   ` Al Viro
2014-12-11 18:34     ` Al Viro
2014-11-05 13:57 [git pull] vfs.git Al Viro
2014-11-02  5:58 Al Viro
2014-10-26  3:04 Al Viro
2014-04-12 12:40 Al Viro
2014-04-13 18:53 ` Geert Uytterhoeven
2013-11-11 16:30 Al Viro
2013-11-13 14:52 ` J. Bruce Fields
2013-06-15  3:34 Al Viro
2012-12-21  0:21 Al Viro
2012-06-01 16:56 Al Viro
2012-06-01 17:38 ` Linus Torvalds
2012-06-01 17:38   ` Linus Torvalds
2012-06-01 17:48   ` 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=20140528063847.GX18016@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@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 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.