From: Dave Chinner <david@fromorbit.com>
To: Brent Bice <bbice@sgi.com>
Cc: Shyam Kaushik <shyam@zadarastorage.com>,
Alex Lyakas <alex@zadarastorage.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH 4/5] xfs: xfs_inode_free() isn't RCU safe
Date: Wed, 13 Apr 2016 07:11:48 +1000 [thread overview]
Message-ID: <20160412211148.GJ567@dastard> (raw)
In-Reply-To: <570CDC0B.3070802@sgi.com>
On Tue, Apr 12, 2016 at 05:29:15AM -0600, Brent Bice wrote:
> Could you resend it to be sure? I flagged it for redelivery the
> day I emailed you so if nobody else has seen it yet then something
> still didn't work. I was pretty sure I'd seen it get delivered ok
> to oss, but... (shrug)
No, it didn't, and it's not in the archives, either.
It seems that sgi.com is rejecting quite a bit of legitimate mail
lately. I've seen a couple of people in the past couple of weeks
send stuff that has reached my private in boxes but not the list.
Now this one, too.
If someone is having to micro-manage the list to prevent rejections
of valid email then that is bad...
-Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-12 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 8:56 [PATCH 4/5] xfs: xfs_inode_free() isn't RCU safe Alex Lyakas
2016-04-12 11:29 ` Brent Bice
2016-04-12 21:11 ` Dave Chinner [this message]
2016-04-12 21:55 ` Brent Bice
2016-04-12 23:29 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2016-04-12 8:55 Alex Lyakas
2016-04-06 9:22 [PATCH 0/5] xfs; xfs_iflush_cluster vs xfs_reclaim_inode Dave Chinner
2016-04-06 9:22 ` [PATCH 4/5] xfs: xfs_inode_free() isn't RCU safe Dave Chinner
2016-04-07 15:50 ` Christoph Hellwig
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=20160412211148.GJ567@dastard \
--to=david@fromorbit.com \
--cc=alex@zadarastorage.com \
--cc=bbice@sgi.com \
--cc=shyam@zadarastorage.com \
--cc=xfs@oss.sgi.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