From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Dave Young <dyoung@redhat.com>,
kexec@lists.infradead.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
linux-kernel@vger.kernel.org,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 0/3] Convert vmcore to use an iov_iter
Date: Mon, 13 Dec 2021 14:19:04 +0000 [thread overview]
Message-ID: <20211213141907.3064347-1-willy@infradead.org> (raw)
For some reason several people have been sending bad patches to fix
compiler warnings in vmcore recently. Here's how it should be done.
Compile-tested only on x86. As noted in the first patch, s390 should
take this conversion a bit further, but I'm not inclined to do that
work myself.
v2:
- Removed unnecessary kernel-doc
- Included uio.h to fix compilation problems
- Made read_from_oldmem_iter static to avoid compile warnings during the
conversion
- Use iov_iter_truncate() (Christoph)
Matthew Wilcox (Oracle) (3):
vmcore: Convert __read_vmcore to use an iov_iter
vmcore: Convert read_from_oldmem() to take an iov_iter
iov-kaddr
arch/x86/kernel/crash_dump_64.c | 7 +-
fs/9p/vfs_dir.c | 5 +-
fs/9p/xattr.c | 6 +-
fs/proc/vmcore.c | 119 ++++++++++++--------------------
include/linux/crash_dump.h | 10 ++-
include/linux/uio.h | 9 +++
lib/iov_iter.c | 32 +++++++++
7 files changed, 97 insertions(+), 91 deletions(-)
--
2.33.0
next reply other threads:[~2021-12-13 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 14:19 Matthew Wilcox (Oracle) [this message]
2021-12-13 14:19 ` [PATCH v2 1/3] vmcore: Convert __read_vmcore to use an iov_iter Matthew Wilcox (Oracle)
2021-12-13 14:19 ` [PATCH v2 2/3] vmcore: Convert read_from_oldmem() to take " Matthew Wilcox (Oracle)
2021-12-13 14:19 ` [PATCH v2 3/3] iov-kaddr Matthew Wilcox (Oracle)
2021-12-13 14:34 ` Matthew Wilcox
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=20211213141907.3064347-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=amit.kachhap@arm.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=hch@lst.de \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=yangtiezhu@loongson.cn \
/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).