Re: [PATCH v2 3/3] pstore: add pmsg

[Mark Salyzyn]

On 01/13/2015 09:58 AM, Kees Cook wrote:
> On Tue, Jan 6, 2015 at 9:49 AM, Mark Salyzyn <salyzyn@xxxxxxxxxxx> wrote:
> > A secured user-space accessible pstore object. Writes
> > to /dev/pmsg0 are appended to the buffer, on reboot
> > the persistent contents are available in
> > /sys/fs/pstore/pmsg-ramoops-[ID].
> >
> > One possible use is syslogd, or other daemon, can
> > write messages, then on reboot provides a means to
> > triage user-space activities leading up to a panic
> > as a companion to the pstore dmesg or console logs.
> >
> > Signed-off-by: Mark Salyzyn <salyzyn@xxxxxxxxxxx>
> > ---
> >   fs/pstore/Kconfig          |  10 +++++
> >   fs/pstore/Makefile         |   2 +
> >   fs/pstore/inode.c          |   3 ++
> >   fs/pstore/internal.h       |   6 +++
> >   fs/pstore/platform.c       |   1 +
> >   fs/pstore/pmsg.c           | 101 +++++++++++++++++++++++++++++++++++++++++++++
> >   fs/pstore/ram.c            |  46 ++++++++++++++++++---
> >   include/linux/pstore.h     |   1 +
> >   include/linux/pstore_ram.h |   1 +
> >   9 files changed, 166 insertions(+), 5 deletions(-)
> >   create mode 100644 fs/pstore/pmsg.c
. . .
> > diff --git a/fs/pstore/pmsg.c b/fs/pstore/pmsg.c
> > new file mode 100644
> > index 0000000..d50d818
> > --- /dev/null
> > +++ b/fs/pstore/pmsg.c
. . .
> > +static ssize_t write_pmsg(struct file *file, const char __user *buf,
> > +                         size_t count, loff_t *ppos)
> > +{
> > +       size_t i;
> > +
> > +       if (!count)
> > +               return 0;
> > +
> > +       if (!access_ok(VERIFY_READ, buf, count))
> > +               return -EFAULT;
> > +
> > +       for (i = 0; i < count; ) {
> > +               char buffer[512];
> This feels like a lot of stack space to use for a buffer. Would it
> maybe be better to either reduce the copy size or use a larger kmalloc
> or vmalloc buffer to act as the bounce buffer to pass to write_buf?
I am taking a page(sic) from kernel/printk/printk.c and countless 
drivers that have settled on 512 byte on-stack bounce buffers as an 
acceptable median. I will test vmalloc though since it would offer us 
the promise of a more atomic operation (see below).

. . .
> > +       if (IS_ERR(pmsg_device)) {
> > +               pr_err("pmsg: failed to create device\n");
> Instead of mentioning pmsg directly here and in the pr_err()s above,
> maybe set it via the pr_* defines:
>
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>
> And maybe use KBUILD_MODNAME instead of PMSG_NAME or vice versa?

Thanks :-)
> +static bool prz_ok(struct persistent_ram_zone *prz)
> +{
> +       return !!prz && !!(persistent_ram_old_size(prz) +
> +                          persistent_ram_ecc_string(prz, NULL, 0));
> +}
> The addition of prz_ok() seems like a separate change?
Will split out.

. . .
> Some nits above. Overall, this seems like a fine idea. Would it make
> sense to enforce a single opener for these writes to avoid
> interleaving?

I expect logging would favour lowest overhead. A reduced syscall 
approach would be for multiple writers to hold on to an open file 
descriptor. We can avoid the problem by switching to spinlock of the 
write handler to guarantee atomic. This makes a switch from stack bounce 
buffer to vmalloc advised.
> -Kees
Thanks. Expect a respin of the entire pstore pmsg patch-set story after 
testing.

Sincerely -- Mark Salyzyn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/