From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 patches for review
Date: Mon, 9 Jun 2014 13:03:52 -0700 [thread overview]
Message-ID: <20140609130352.fc94f7d6ceaff24750eabccb@linux-foundation.org> (raw)
I'm stuck with the usual handful of patches. My notes:
ocfs2-should-add-inode-into-orphan-dir-after-updating-entry-in-ocfs2_rename.patch: needs acks
deadlock-when-two-nodes-are-converting-same-lock-from-pr-to-ex-and-idletimeout-closes-conn.patch: needs acks
ocfs2-revert-the-patch-fix-null-pointer-dereference-when-dismount-and-ocfs2rec-simultaneously.patch: needs acks
ocfs2-dlm-do-not-purge-lockres-that-is-queued-for-assert-master.patch: needs acks
refcount-take-inode_lock-until-write-io-issued.patch: needs acks
ocfs2-fix-a-tiny-race-when-running-dirop_fileop_racer.patch: needs acks. Mark confused, worried about log flooding
ocfs2-do-not-return-dlm_migrate_response_mastery_ref-to-avoid-endlessloop-during-umount.patch: needs acks
ocfs2-manually-do-the-iput-once-ocfs2_add_entry-failed-in-ocfs2_symlink-and-ocfs2_mknod.patch: needs acks, Mark dislikes it.
I'll send them out for re-review now.
next reply other threads:[~2014-06-09 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 20:03 Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-07 21:54 [Ocfs2-devel] ocfs2 patches for review Andrew Morton
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=20140609130352.fc94f7d6ceaff24750eabccb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.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