From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Boaz Harrosh <ooo@electrozaur.com>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [GIT PULL] Orangefs (text only resend)
Date: Fri, 11 Sep 2015 23:24:36 +0100 [thread overview]
Message-ID: <20150911222436.GO22011@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOg9mSTuo8Y2XTJWx=8443Ps=mxmSP-qxdRRt80FfWXECPdWZA@mail.gmail.com>
On Fri, Sep 11, 2015 at 05:12:08PM -0400, Mike Marshall wrote:
> I'm about to leave for the day...
>
> I haven't found any problems with the GFP_KERNEL allocations that
> Al warned me about... that doesn't mean there aren't any...
*IF* you have nothing that would require locks in any of the pathways
related to memory pressure (and can guarantee that no such thing will
appear), GFP_KERNEL should be OK. Still, doing that under the system-wide
mutex taken whenever you need to send a request looks like a Bad Idea(tm) -
too easy to introduce such deadlocks on subsequent changes.
> I'm using copy_page_to_iter in my new branch as Al suggested. I've
> changed the code quite a bit from any samples I've posted, there were
> regressions with it. I finally stole some code from
> cifs/file.c/cifs_readdata_to_iov
> and everything works... but I'm not happy with it yet... Linus once posted
> a message to the effect that "you don't fix bugs by thrashing around until
> stuff seems to work, you fix them by doing the right thing on purpose..."
> and I'm working towards that end...
Could you tell where does the current code live? What's in -next appears
to be unchanged...
BTW, as for passing all your tests... Do those include fuzzing it by
misbehaving server? And getdents() from a directory that has a bunch of
long names *and* a short one in the very end looks like it would misbehave
even on correctly working server...
next prev parent reply other threads:[~2015-09-11 22:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:42 [GIT PULL] Orangefs (text only resend) Mike Marshall
2015-09-02 23:34 ` Linus Torvalds
2015-09-03 1:13 ` Mike Marshall
2015-09-03 1:28 ` Linus Torvalds
2015-09-03 20:22 ` Linus Torvalds
2015-09-03 22:18 ` Mike Marshall
2015-09-03 22:44 ` Greg Kroah-Hartman
2015-09-06 6:35 ` Christoph Hellwig
2015-09-06 9:08 ` Al Viro
2015-09-06 14:52 ` Mike Marshall
2015-09-06 15:00 ` Mike Marshall
2015-09-06 20:20 ` Al Viro
2015-09-07 6:37 ` Al Viro
2015-09-07 21:10 ` Mike Marshall
2015-09-07 23:22 ` Al Viro
2015-09-08 0:47 ` Theodore Ts'o
2015-09-08 2:49 ` Dave Chinner
2015-09-08 14:48 ` Christoph Hellwig
2015-09-08 18:21 ` Mike Marshall
2015-09-09 15:05 ` Mike Marshall
2015-09-11 21:12 ` Mike Marshall
2015-09-11 22:24 ` Al Viro [this message]
2015-09-13 11:56 ` Mike Marshall
2015-09-11 23:20 ` Linus Torvalds
2015-09-13 11:59 ` Mike Marshall
2015-09-06 14:35 ` Mike Marshall
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=20150911222436.GO22011@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).