From: Christoph Hellwig <hch@infradead.org>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix filler_t callback type mismatch with readpage
Date: Wed, 1 May 2019 06:36:54 -0700 [thread overview]
Message-ID: <20190501133654.GA26768@infradead.org> (raw)
In-Reply-To: <20190430214724.66699-1-samitolvanen@google.com>
This still leaves bugs around in jffs2 and nfs. And it is a little
ugly. This is what I'd like to do instead, so far untested. I'll
post a series once it passes basic testing:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/filler-fixes
prev parent reply other threads:[~2019-05-01 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 21:47 [PATCH] mm: fix filler_t callback type mismatch with readpage Sami Tolvanen
2019-04-30 21:57 ` Kees Cook
2019-05-01 13:36 ` Christoph Hellwig [this message]
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=20190501133654.GA26768@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.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;
as well as URLs for NNTP newsgroup(s).