From: Benjamin LaHaise <ben@communityfibre.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christopher Lameter <cl@linux.com>,
Randy Dunlap <rdunlap@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>,
akpm@linux-foundation.org, Mel Gorman <mel@skynet.ie>,
andi@firstfloor.org, Rik van Riel <riel@redhat.com>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC 0/8] Xarray object migration V1
Date: Thu, 28 Dec 2017 14:17:48 -0500 [thread overview]
Message-ID: <20171228191748.GO24310@kvack.org> (raw)
In-Reply-To: <1514482820.3040.13.camel@HansenPartnership.com>
On Thu, Dec 28, 2017 at 09:40:20AM -0800, James Bottomley wrote:
> On Thu, 2017-12-28 at 12:33 -0500, Benjamin LaHaise wrote:
> > On Thu, Dec 28, 2017 at 09:18:53AM -0800, James Bottomley wrote:
> > ...
> > >
> > > Well you can ask for expert help. The mm list also ate one of my
> > > bug reports (although the followup made it). This is the lost
> > > email:
> > >
> > > From: James Bottomley <James.Bottomley@HansenPartnership.com
> > > >
> > > To: Linux Memory Management List <linux-mm@kvack.org>
> > > Subject: Hang with v4.15-rc trying to swap back in
> > > Date: Wed, 27 Dec 2017 10:12:20 -0800
> > > Message-Id: <1514398340.3986.10.camel@HansenPartnership.com>
> > ...
> > >
> > > I've cc'd Ben because I think the list is still on his systems.
> > ...
> >
> > Looks like Google's anti-spam service filtered it, so my system never
> > even saw it. Not much I can do when that happens other than try to
> > manually track it down.
>
> I honestly don't think it's safe to host a public email list on google:
> their "spam" filter is eccentric to say the least and is far too
> willing to generate false positives for reasons no-one seems to be able
> to fix. What about moving the list to reliable infrastructure, like
> vger?
The list is not hosted on Google - Google's anti-spam service is only used
for ingress filtering. Spamassassin is not a "Good Enough" option these
days given the volume and nature of spam that comes into kvack.org. If
you can point me at a better anti-spam solution that actually works (and
is not RBL based), I'd be happy to try it since the Google service is
absolutely awful with pretty much no way to get a human to fix obviously
broken things.
-ben
> James
>
>
--
"Thought is the essence of where you are now."
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-28 19:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 22:06 Christoph Lameter
2017-12-27 22:06 ` [RFC 2/8] slub: Add defrag_ratio field and sysfs support Christoph Lameter
2017-12-30 6:20 ` Matthew Wilcox
2018-01-02 14:53 ` Christopher Lameter
2017-12-27 22:06 ` [RFC 3/8] slub: Add isolate() and migrate() methods Christoph Lameter
2017-12-30 6:42 ` Matthew Wilcox
2018-01-01 21:20 ` Matthew Wilcox
2018-01-02 14:56 ` Christopher Lameter
2018-01-02 14:55 ` Christopher Lameter
2017-12-27 22:06 ` [RFC 4/8] slub: Sort slab cache list and establish maximum objects for defrag slabs Christoph Lameter
2017-12-27 22:06 ` [RFC 5/8] slub: Slab defrag core Christoph Lameter
2017-12-27 22:06 ` [RFC 6/8] slub: Extend slabinfo to support -D and -F options Christoph Lameter
2017-12-27 22:06 ` [RFC 7/8] xarray: Implement migration function for objects Christoph Lameter
2017-12-27 22:06 ` [RFC 8/8] Add debugging output Christoph Lameter
2017-12-28 5:19 ` [RFC 0/8] Xarray object migration V1 Randy Dunlap
2017-12-28 14:57 ` Christopher Lameter
2017-12-28 17:18 ` James Bottomley
2017-12-28 17:33 ` Benjamin LaHaise
2017-12-28 17:40 ` James Bottomley
2017-12-28 19:17 ` Benjamin LaHaise [this message]
2017-12-28 20:00 ` James Bottomley
2017-12-28 20:33 ` Benjamin LaHaise
2017-12-28 22:24 ` Dave Chinner
2017-12-29 0:19 ` Christopher Lameter
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=20171228191748.GO24310@kvack.org \
--to=ben@communityfibre.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@infradead.org \
--cc=riel@redhat.com \
--cc=willy@infradead.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