From: Christoph Hellwig <hch@lst.de>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 10/11] fs: remove __vfs_read
Date: Fri, 8 May 2020 17:46:58 +0200 [thread overview]
Message-ID: <20200508154658.GA4200@lst.de> (raw)
In-Reply-To: <20200508154552.GB1431382@iweiny-DESK2.sc.intel.com>
On Fri, May 08, 2020 at 08:45:53AM -0700, Ira Weiny wrote:
> On Fri, May 08, 2020 at 11:22:21AM +0200, Christoph Hellwig wrote:
> > Fold it into the two callers.
>
> In 5.7-rc4, it looks like __vfs_read() is called from
> security/integrity/iint.c
>
> Was that removed somewhere prior to this patch?
[PATCH 08/11] integrity/ima: switch to using __kernel_read
next prev parent reply other threads:[~2020-05-08 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 9:22 clean up kernel_{read,write} & friends Christoph Hellwig
2020-05-08 9:22 ` [PATCH 01/11] fs: call file_{start,end}_write from __kernel_write Christoph Hellwig
2020-05-08 9:22 ` [PATCH 02/11] fs: check FMODE_WRITE in __kernel_write Christoph Hellwig
2020-05-08 9:22 ` [PATCH 03/11] fs: remove the call_{read,write}_iter functions Christoph Hellwig
2020-05-08 9:22 ` [PATCH 04/11] fs: implement kernel_write using __kernel_write Christoph Hellwig
2020-05-08 9:22 ` [PATCH 05/11] fs: remove __vfs_write Christoph Hellwig
2020-05-08 9:22 ` [PATCH 06/11] fs: don't change the address limit for ->write_iter in __kernel_write Christoph Hellwig
2020-05-08 9:22 ` [PATCH 07/11] fs: add a __kernel_read helper Christoph Hellwig
2020-05-08 9:22 ` [PATCH 08/11] integrity/ima: switch to using __kernel_read Christoph Hellwig
2020-05-08 9:22 ` [PATCH 09/11] fs: implement kernel_read " Christoph Hellwig
2020-05-08 9:22 ` [PATCH 10/11] fs: remove __vfs_read Christoph Hellwig
2020-05-08 15:45 ` Ira Weiny
2020-05-08 15:46 ` Christoph Hellwig [this message]
2020-05-08 9:22 ` [PATCH 11/11] fs: don't change the address limit for ->read_iter in __kernel_read 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=20200508154658.GA4200@lst.de \
--to=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.