From: liaoweixiong <liaoweixiong@allwinnertech.com>
To: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
liaoweixiong <liaoweixiong@allwinnertech.com>
Subject: [RFC v5 0/4] pstore/block: new support logger for block devices
Date: Mon, 7 Jan 2019 20:00:58 +0800 [thread overview]
Message-ID: <1546862462-19640-1-git-send-email-liaoweixiong@allwinnertech.com> (raw)
Why should we need pstore_block?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a sample for block device logger in driver
MTD (drivers/mtd/mtdoops.c).
2. Do not any equipment have battery, which means that it lost all data
on general ram if power failure. Pstore has little to do for these
equipments.
[PATCH v5]
On patch 1:
1. rename pstore/rom to pstore/blk
2. Do not allocate any memory in the write path of panic. So, use local
array instead in function romz_recover_dmesg_meta.
3. Add C header file "linux/fs.h" to fix implicit declaration of function
'filp_open','kernel_read'...
On patch 3:
1. If panic, do not recover pmsg but flush if it is dirty.
2. Fix erase pmsg failed.
On patch 4:
1. Create a document for pstore/blk
[PATCH v4]
On patch 1:
1. Fix always true condition '(--i >= 0) => (0-u32max >= 0)' in function
romz_init_zones by defining variable i to 'int' rahter than
'unsigned int'.
2. To make codes more easily to read, we use macro READ_NEXT_ZONE for
return value of romz_dmesg_read if it need to read next zone.
Moveover, we assign READ_NEXT_ZONE -1024 rather than 0.
3. Add 'FLUSH_META' to 'enum romz_flush_mode' and rename 'NOT_FLUSH' to
'FLUSH_NONE'
4. Function romz_zone_write work badly with FLUSH_PART mode as badly
address and offset to write.
On patch 3:
NEW SUPPORT psmg for pstore_rom.
[PATCH v3]
On patch 1:
Fix build as module error for undefined 'vfs_read' and 'vfs_write'
Both of 'vfs_read' and 'vfs_write' haven't be exproted yet, so we use
'kernel_read' and 'kernel_write' instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rather than block device.
liaoweixiong (4):
pstore/blk: new support logger for block devices
pstore/blk: add sample for pstore_blk
pstore/blk: support pmsg for pstore block
Documentation: pstore/blk: create document for pstore_blk
Documentation/admin-guide/pstore-block.rst | 226 ++++++
MAINTAINERS | 1 +
fs/pstore/Kconfig | 20 +
fs/pstore/Makefile | 5 +
fs/pstore/blkbuf.c | 46 ++
fs/pstore/blkzone.c | 1168 ++++++++++++++++++++++++++++
include/linux/pstore_blk.h | 62 ++
7 files changed, 1528 insertions(+)
create mode 100644 Documentation/admin-guide/pstore-block.rst
create mode 100644 fs/pstore/blkbuf.c
create mode 100644 fs/pstore/blkzone.c
create mode 100644 include/linux/pstore_blk.h
--
1.9.1
next reply other threads:[~2019-01-07 12:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 12:00 liaoweixiong [this message]
2019-01-07 12:00 ` [RFC v5 1/4] pstore/blk: " liaoweixiong
2019-01-18 0:12 ` Kees Cook
2019-01-19 8:53 ` liaoweixiong
2019-01-23 18:19 ` Aaro Koskinen
2019-01-24 13:27 ` liaoweixiong
2019-01-07 12:01 ` [RFC v5 2/4] pstore/blk: add sample for pstore_blk liaoweixiong
2019-01-18 0:15 ` Kees Cook
2019-01-18 0:21 ` Kees Cook
2019-01-19 9:26 ` 廖威雄
2019-01-19 9:28 ` liaoweixiong
2019-01-19 9:20 ` liaoweixiong
2019-01-07 12:01 ` [RFC v5 3/4] pstore/blk: support pmsg for pstore block liaoweixiong
2019-01-18 0:17 ` Kees Cook
2019-01-23 11:11 ` 廖威雄
2019-01-23 11:11 ` liaoweixiong
2019-01-07 12:01 ` [RFC v5 4/4] Documentation: pstore/blk: create document for pstore_blk liaoweixiong
2019-01-18 0:18 ` Kees Cook
2019-01-07 21:47 ` [RFC v5 0/4] pstore/block: new support logger for block devices Kees Cook
2019-01-08 2:19 ` 廖威雄
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=1546862462-19640-1-git-send-email-liaoweixiong@allwinnertech.com \
--to=liaoweixiong@allwinnertech.com \
--cc=akpm@linux-foundation.org \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®