From: Trond Myklebust <trondmy@primarydata.com>
To: "mhocko@kernel.org" <mhocko@kernel.org>,
"n.borisov.lkml@gmail.com" <n.borisov.lkml@gmail.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull NFS client fixes for 4.12
Date: Thu, 11 May 2017 12:16:37 +0000 [thread overview]
Message-ID: <1494504995.3207.1.camel@primarydata.com> (raw)
In-Reply-To: <20170511075910.GD26782@dhcp22.suse.cz>
T24gVGh1LCAyMDE3LTA1LTExIGF0IDA5OjU5ICswMjAwLCBNaWNoYWwgSG9ja28gd3JvdGU6DQo+
IE9uIFRodSAxMS0wNS0xNyAxMDo1MzoyNywgTmlrb2xheSBCb3Jpc292IHdyb3RlOg0KPiA+IA0K
PiA+IA0KPiA+IE9uIDEwLjA1LjIwMTcgMTk6NDcsIFRyb25kIE15a2xlYnVzdCB3cm90ZToNCj4g
DQo+IFsuLi5dDQo+ID4gPiAtIENsZWFudXAgYW5kIHJlbW92YWwgb2Ygc29tZSBtZW1vcnkgZmFp
bHVyZSBwYXRocyBub3cgdGhhdA0KPiA+ID4gwqAgR0ZQX05PRlMgaXMgZ3VhcmFudGVlZCB0byBu
ZXZlciBmYWlsLg0KPiA+IA0KPiA+IFdoYXQgZ3VhcmFudGVlcyB0aGF0PyBTaW5jZSBpZiB0aGlz
IGlzIHRoZSBjYXNlIHRoZW4gdGhpcyBjYW4NCj4gPiByZXN1bHQgaW4NCj4gPiBhIGxvdCBvZiBv
cHBvcnR1bml0aWVzIGZvciBjbGVhbnVwIGFjcm9zcyB0aGUgd2hvbGUga2VybmVsIHRyZWUuDQo+
ID4gQWZ0ZXINCj4gPiBkaXNjdXNzaW5nIHdpdGggbWhvY2tvIChjYydlZCkgaXQgc2VlbXMgdGhh
dCBpbiBwcmFjdGljZSBldmVyeXRoaW5nDQo+ID4gYmVsb3cgQ09TVExZX09SREVSIHdoaWNoIGFy
ZSBub3QgR0ZQX05PUkVUUlkgd2lsbCBuZXZlciBmYWlsLiBCdXQNCj4gPiB0aGlzDQo+ID4gc2Vt
YW50aWMgaXMgbm90IHRoZSBzYW1lIGFzIEdGUF9OT0ZBSUwuIEUuZy4gbm90aGluZyBndWFyYW50
ZWVzDQo+ID4gdGhhdA0KPiA+IHRoaXMgd2lsbCBzdGF5IGxpa2UgdGhhdCBpbiB0aGUgZnV0dXJl
Pw0KPiANCj4gSW4gcHJhY3RpY2UgaXQgaXMgaGFyZCB0byBjaGFuZ2UgdGhlIHNlbWFudGljIG9m
IHNtYWxsIGFsbG9jYXRpb25zDQo+IG5ldmVyDQo+IGZhaWwgX3ByYWN0aWNhbGx5Xy4gQnV0IHRo
aXMgaXMgYWJzb2x1dGVseSBub3QgZ3VhcmFudGVlZCEgVGhleSBjYW4NCj4gZmFpbA0KPiBlLmcu
IHdoZW4gdGhlIGFsbG9jYXRpb24gY29udGV4dCBpcyB0aGUgb29tIHZpY3RpbS4gUmVtb3Zpbmcg
ZXJyb3INCj4gcGF0aHMNCj4gZm9yIGFsbG9jYXRpb24gZmFpbHVyZXMgaXMganVzdCB3cm9uZy4N
Cg0KT0ssIHRoaXMgbWFrZXMgbm8gZnVja2luZyBzZW5zZSBhdCBhbGwuDQoNCkVpdGhlciBhbGxv
Y2F0aW9ucyBjYW4gZmFpbCBvciB0aGV5IGNhbid0Lg0KMSkgSWYgdGhleSBjYW4ndCBmYWlsLCB0
aGVuIHdlIGRvbid0IG5lZWQgdGhlIGNoZWNrcy4NCjIpIElmIHRoZXkgY2FuIGZhaWwsIHRoZW4g
d2UgZG8gbmVlZCB0aGVtLCBhbmQgdGhpcyBoYW5kIHdyaW5naW5nIGluDQp0aGUgTU0gY29tbXVu
aXR5IGFib3V0IEdGUF8qIHNlbWFudGljcyBhbmQgaG93IHdlIG5lZWQgdG8gcHJldmVudA0KZmFp
bHVyZSBpcyBmdWNraW5nIHBvaW50bGVzcy4NCg0KU28gd2hpY2ggaXMgaXQ/ICgxKSBvciAoMik/
DQoNCg0KDQoNCi0tIA0KVHJvbmQgTXlrbGVidXN0DQpMaW51eCBORlMgY2xpZW50IG1haW50YWlu
ZXIsIFByaW1hcnlEYXRhDQp0cm9uZC5teWtsZWJ1c3RAcHJpbWFyeWRhdGEuY29tDQo=
WARNING: multiple messages have this Message-ID (diff)
From: Trond Myklebust <trondmy@primarydata.com>
To: "mhocko@kernel.org" <mhocko@kernel.org>,
"n.borisov.lkml@gmail.com" <n.borisov.lkml@gmail.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull NFS client fixes for 4.12
Date: Thu, 11 May 2017 12:16:37 +0000 [thread overview]
Message-ID: <1494504995.3207.1.camel@primarydata.com> (raw)
In-Reply-To: <20170511075910.GD26782@dhcp22.suse.cz>
On Thu, 2017-05-11 at 09:59 +0200, Michal Hocko wrote:
> On Thu 11-05-17 10:53:27, Nikolay Borisov wrote:
> >
> >
> > On 10.05.2017 19:47, Trond Myklebust wrote:
>
> [...]
> > > - Cleanup and removal of some memory failure paths now that
> > > GFP_NOFS is guaranteed to never fail.
> >
> > What guarantees that? Since if this is the case then this can
> > result in
> > a lot of opportunities for cleanup across the whole kernel tree.
> > After
> > discussing with mhocko (cc'ed) it seems that in practice everything
> > below COSTLY_ORDER which are not GFP_NORETRY will never fail. But
> > this
> > semantic is not the same as GFP_NOFAIL. E.g. nothing guarantees
> > that
> > this will stay like that in the future?
>
> In practice it is hard to change the semantic of small allocations
> never
> fail _practically_. But this is absolutely not guaranteed! They can
> fail
> e.g. when the allocation context is the oom victim. Removing error
> paths
> for allocation failures is just wrong.
OK, this makes no fucking sense at all.
Either allocations can fail or they can't.
1) If they can't fail, then we don't need the checks.
2) If they can fail, then we do need them, and this hand wringing in
the MM community about GFP_* semantics and how we need to prevent
failure is fucking pointless.
So which is it? (1) or (2)?
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next prev parent reply other threads:[~2017-05-11 12:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 16:47 [GIT PULL] Please pull NFS client fixes for 4.12 Trond Myklebust
2017-05-10 16:47 ` Trond Myklebust
2017-05-10 20:06 ` Linus Torvalds
2017-05-11 7:53 ` Nikolay Borisov
2017-05-11 7:59 ` Michal Hocko
2017-05-11 12:16 ` Trond Myklebust [this message]
2017-05-11 12:16 ` Trond Myklebust
2017-05-11 12:26 ` Michal Hocko
2017-05-11 12:45 ` Trond Myklebust
2017-05-11 12:45 ` Trond Myklebust
2017-05-11 12:56 ` Michal Hocko
2017-05-11 13:10 ` Trond Myklebust
2017-05-11 13:10 ` Trond Myklebust
2017-05-11 13:27 ` Michal Hocko
2017-05-16 15:15 ` Jonathan Corbet
2017-05-11 13:41 ` Trond Myklebust
2017-05-11 13:41 ` Trond Myklebust
2017-05-11 13:54 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 14:19 Trond Myklebust
2017-06-28 14:19 ` Trond Myklebust
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=1494504995.3207.1.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=n.borisov.lkml@gmail.com \
--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.