From: Oleg Nesterov <oleg@redhat.com>
To: Jann Horn <jannh@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Eric W . Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v3 2/5] coredump: Let dump_emit() bail out on short writes
Date: Tue, 18 Aug 2020 15:40:28 +0200 [thread overview]
Message-ID: <20200818134027.GF29865@redhat.com> (raw)
In-Reply-To: <20200818061239.29091-3-jannh@google.com>
On 08/18, Jann Horn wrote:
>
> + if (dump_interrupted())
> + return 0;
> + n = __kernel_write(file, addr, nr, &pos);
> + if (n != nr)
> + return 0;
> + file->f_pos = pos;
Just curious, can't we simply do
__kernel_write(file, addr, nr, &file->f_pos);
and avoid "loff_t pos" ?
Oleg.
next prev parent reply other threads:[~2020-08-18 13:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 6:12 [PATCH v3 0/5] Fix ELF / FDPIC ELF core dumping, and use mmap_lock properly in there Jann Horn
2020-08-18 6:12 ` Jann Horn
2020-08-18 6:12 ` [PATCH v3 1/5] binfmt_elf_fdpic: Stop using dump_emit() on user pointers on !MMU Jann Horn
2020-08-18 6:12 ` Jann Horn
2020-08-18 6:12 ` [PATCH v3 2/5] coredump: Let dump_emit() bail out on short writes Jann Horn
2020-08-18 6:12 ` Jann Horn
2020-08-18 13:40 ` Oleg Nesterov [this message]
2020-08-18 15:08 ` Jann Horn
2020-08-18 15:08 ` Jann Horn
2020-08-18 15:17 ` Al Viro
2020-08-18 6:12 ` [PATCH v3 3/5] coredump: Refactor page range dumping into common helper Jann Horn
2020-08-18 6:12 ` Jann Horn
2020-08-18 6:12 ` [PATCH v3 4/5] binfmt_elf, binfmt_elf_fdpic: Use a VMA list snapshot Jann Horn
2020-08-18 6:12 ` Jann Horn
2020-08-18 8:18 ` Linus Torvalds
2020-08-18 8:18 ` Linus Torvalds
2020-08-18 8:31 ` Jann Horn
2020-08-18 8:31 ` Jann Horn
2020-08-18 6:12 ` [PATCH v3 5/5] mm/gup: Take mmap_lock in get_dump_page() Jann Horn
2020-08-18 6:12 ` Jann Horn
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=20200818134027.GF29865@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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.