From: WeiXiong Liao <liaoweixiong@allwinnertech.com>
To: Kees Cook <keescook@chromium.org>
Cc: Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-doc@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/12] pstore: mtd: support crash log to block and mtd device
Date: Sat, 9 May 2020 18:32:28 +0800 [thread overview]
Message-ID: <c1583001-bf03-d198-ad57-3d2a0baf93ca@allwinnertech.com> (raw)
In-Reply-To: <202005080020.41C33738@keescook>
hi Kees Cook,
On 2020/5/8 PM 3:27, Kees Cook wrote:
> On Thu, May 07, 2020 at 11:39:52PM -0700, Kees Cook wrote:
>> So far, I've identified the following stuff left to do:
>> [...]
>> - implement ramoops-like probe feature for pstore/blk
>
> With the following hack, I'm able to start testing the series:
>
> diff --git a/fs/pstore/blk.c b/fs/pstore/blk.c
> index a736555e1ed3..7145da079267 100644
> --- a/fs/pstore/blk.c
> +++ b/fs/pstore/blk.c
> @@ -373,12 +373,14 @@ int psblk_register_blkdev(unsigned int major, unsigned int flags,
> if (IS_ERR(binfo))
> return PTR_ERR(binfo);
>
> +#if 0
> /* only allow driver matching the @blkdev */
> if (!binfo->devt || MAJOR(binfo->devt) != major) {
> pr_debug("invalid major %u (expect %u)\n",
> major, MAJOR(binfo->devt));
> return -ENODEV;
> }
> +#endif
>
> /* hold bdev exclusively */
> bdev = psblk_get_bdev(holder);
> @@ -423,7 +425,7 @@ void psblk_unregister_blkdev(unsigned int major)
> struct psblk_device dev = {.read = psblk_generic_blk_read};
> void *holder = blkdev;
>
> - if (psblk_bdev && MAJOR(psblk_bdev->bd_dev) == major) {
> + if (psblk_bdev/* && MAJOR(psblk_bdev->bd_dev) == major*/) {
> psblk_unregister_device(&dev);
> psblk_put_bdev(psblk_bdev, holder);
> blkdev_panic_write = NULL;
> @@ -476,6 +478,24 @@ int pstore_blk_usr_info(struct pstore_blk_info *info)
> }
> EXPORT_SYMBOL_GPL(pstore_blk_usr_info);
>
> +static int __init pstore_blk_init(void)
> +{
> + int ret = 0;
> +
> + if (blkdev[0])
> + ret = psblk_register_blkdev(0, 0, NULL);
> +
> + return ret;
> +}
> +postcore_initcall(pstore_blk_init);
> +
> +static void __exit pstore_blk_exit(void)
> +{
> + psblk_unregister_blkdev(0);
> +}
> +module_exit(pstore_blk_exit);
> +
> +
> MODULE_LICENSE("GPL");
> MODULE_AUTHOR("WeiXiong Liao <liaoweixiong@allwinnertech.com>");
> MODULE_DESCRIPTION("pstore backend for block devices");
>
>
> Then I can get things up and running with:
>
> # insmod pstore.ko compress=off
> # insmod pstore_zone.ko
> # truncate pstore-blk.raw --size 100M
> # losetup -f --show pstore-blk.raw
> /dev/loop0
> # insmod pstore_blk.ko blkdev=/dev/loop0 kmsg_size=16 console_size=64
>
> So far, I've hit a few bugs. The most obvious is that "rmmod" causes a
> fault, so I think locking and other things need to be fixed up further.
> After that, it looked like all the compressed files were failing to
> decompress, which implies some kind of buffer offset problem. When I
> loaded with pstore.compress=off I got readable logs, but there is a span
> of garbage between the header and the body in
> /sys/fs/pstore/dmesg-pstore-zone-1 etc.
>
Both of the above two bugs have been fix on series v6.
The following diff is to fix "rmmod" bug.
@@ -1273,8 +1273,8 @@ static void psz_free_zones(struct pstore_zone
***pszones, unsigned int *cnt)
return;
while (*cnt > 0) {
- psz_free_zone(&zones[*cnt]);
(*cnt)--;
+ psz_free_zone(&zones[*cnt]);
}
kfree(zones);
*pszones = NULL;
> Cool so far! It just needs a bit more testing a polish. :)
>
--
WeiXiong Liao
next prev parent reply other threads:[~2020-05-09 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 6:39 Kees Cook
2020-05-08 6:39 ` [PATCH v4 01/12] printk: Introduce kmsg_dump_reason_str() Kees Cook
2020-05-08 6:39 ` [PATCH v4 02/12] pstore/zone: Introduce common layer to manage storage zones Kees Cook
2020-05-09 3:09 ` WeiXiong Liao
2020-05-08 6:39 ` [PATCH v4 03/12] pstore/blk: Introduce backend for block devices Kees Cook
2020-05-09 3:48 ` WeiXiong Liao
2020-05-08 6:39 ` [PATCH v4 04/12] pstore/blk: Provide way to choose pstore frontend support Kees Cook
2020-05-08 6:39 ` [PATCH v4 05/12] pstore/blk: Add support for pmsg frontend Kees Cook
2020-05-09 4:38 ` WeiXiong Liao
2020-05-08 6:39 ` [PATCH v4 06/12] pstore/blk: Add console frontend support Kees Cook
2020-05-09 4:53 ` WeiXiong Liao
2020-05-08 6:39 ` [PATCH v4 07/12] pstore/blk: Add ftrace " Kees Cook
2020-05-08 6:40 ` [PATCH v4 08/12] Documentation: Add details for pstore/blk Kees Cook
2020-05-08 6:40 ` [PATCH v4 09/12] pstore/zone: Provide way to skip "broken" zone for MTD devices Kees Cook
2020-05-08 6:40 ` [PATCH v4 10/12] pstore/blk: Provide way to query pstore configuration Kees Cook
2020-05-08 6:40 ` [PATCH v4 11/12] pstore/blk: Support non-block storage devices Kees Cook
2020-05-08 6:40 ` [PATCH v4 12/12] mtd: Support kmsg dumper based on pstore/blk Kees Cook
2020-05-09 5:14 ` WeiXiong Liao
2020-05-08 7:27 ` [PATCH v4 00/12] pstore: mtd: support crash log to block and mtd device Kees Cook
2020-05-09 10:32 ` WeiXiong Liao [this message]
2020-05-09 19:10 ` Kees Cook
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=c1583001-bf03-d198-ad57-3d2a0baf93ca@allwinnertech.com \
--to=liaoweixiong@allwinnertech.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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®