On 2020-05-29 6:32 a.m., Christoph Hellwig wrote:
> On Thu, May 28, 2020 at 11:43:13AM -0700, Linus Torvalds wrote:
>> On Wed, May 27, 2020 at 10:41 PM Christoph Hellwig wrote:
>>>
>>> -ssize_t __kernel_write(struct file *file, const void *buf, size_t count,
>>> loff_t *pos)
>>> +ssize_t
On Fri, May 29, 2020 at 07:57:36AM +0200, Christoph Hellwig wrote:
> On Thu, May 28, 2020 at 08:00:52PM +0100, Al Viro wrote:
> > On Thu, May 28, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> > > If we write to a file that implements ->write_iter there is no need
> > > to change the address
On Thu, May 28, 2020 at 11:43:13AM -0700, Linus Torvalds wrote:
> On Wed, May 27, 2020 at 10:41 PM Christoph Hellwig wrote:
> >
> > -ssize_t __kernel_write(struct file *file, const void *buf, size_t count,
> > loff_t *pos)
> > +ssize_t __kernel_write(struct file *file, const void *buf, size_t
On Thu, May 28, 2020 at 08:00:52PM +0100, Al Viro wrote:
> On Thu, May 28, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> > If we write to a file that implements ->write_iter there is no need
> > to change the address limit if we send a kvec down. Implement that
> > case, and prefer it over
On Thu, May 28, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> If we write to a file that implements ->write_iter there is no need
> to change the address limit if we send a kvec down. Implement that
> case, and prefer it over using plain ->write with a changed address
> limit if available.
On Wed, May 27, 2020 at 10:41 PM Christoph Hellwig wrote:
>
> -ssize_t __kernel_write(struct file *file, const void *buf, size_t count,
> loff_t *pos)
> +ssize_t __kernel_write(struct file *file, const void *buf, size_t count,
> + loff_t *pos)
Please don't do these kinds of
On Sat, May 16, 2020 at 11:04:36AM +0800, Hillf Danton wrote:
> > + if (file->f_op->write_iter) {
> > + struct kvec iov = { .iov_base = (void *)buf, .iov_len = count };
> > + struct kiocb kiocb;
> > + struct iov_iter iter;
> > +
> > + init_sync_kiocb(,
7 matches
Mail list logo
