linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Kazimierz Krosman <k.krosman@samsung.com>
Cc: akpm@linux-foundation.org, peter@hurleysoftware.com,
	tj@kernel.org, vvs@virtuozzo.com, corbet@lwn.net, arnd@arndb.de,
	gregkh@linuxfoundation.org, daniel@zonque.org,
	kay.sievers@vrfy.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-api@vger.kernel.org,
	k.lewandowsk@samsung.com, m.niesluchow@samsung.com,
	richard.weinberger@gmail.com, b.zolnierkie@samsung.com,
	luto@amacapital.net, knhoon.baik@samsung.com
Subject: Re: [PATCH v6 3/8] kmsg: introduce additional kmsg devices support
Date: Fri, 26 Feb 2016 15:05:10 +0100	[thread overview]
Message-ID: <20160226140510.GE3305@pathway.suse.cz> (raw)
In-Reply-To: <1456314801-32738-4-git-send-email-k.krosman@samsung.com>

On Wed 2016-02-24 12:53:16, Kazimierz Krosman wrote:
> From: Marcin Niesluchowski <m.niesluchow@samsung.com>
> 
> kmsg device provides operations on cyclic logging buffer used mainly
> by kernel but also in userspace by privileged processes.
> 
> Additional kmsg devices keep the same log format but may be added
> dynamically with custom size.
> 
> Signed-off-by: Marcin Niesluchowski <m.niesluchow@samsung.com>
> Signed-off-by: Paul Osmialowski <p.osmialowsk@samsung.com>
> [Rebased kmsg patch v5 on Linux 4.5-rc5]
> Signed-off-by: Kazimierz Krosman <k.krosman@samsung.com>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 3653a8e..b99403b 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -584,9 +595,11 @@ ssize_t msg_print_ext_body(char *buf, size_t size,
>  void log_buf_kexec_setup(void)
>  {
>  	VMCOREINFO_SYMBOL(log_buf);
> -	VMCOREINFO_SYMBOL(log_buf_len);
> -	VMCOREINFO_SYMBOL(log_first_idx);
> -	VMCOREINFO_SYMBOL(log_next_idx);
> +	VMCOREINFO_STRUCT_SIZE(log_buffer);
> +	VMCOREINFO_OFFSET(log_buffer, buf);
> +	VMCOREINFO_OFFSET(log_buffer, len);
> +	VMCOREINFO_OFFSET(log_buffer, first_idx);
> +	VMCOREINFO_OFFSET(log_buffer, next_idx);

This breaks makedumpfile, crash and possibly other tools
that use this information to access the log buffer.

Best Regards,
Petr

  reply	other threads:[~2016-02-26 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 11:53 [PATCH v6 0/8] Additional kmsg devices Kazimierz Krosman
     [not found] ` <1456314801-32738-1-git-send-email-k.krosman-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-02-24 11:53   ` [PATCH v6 1/8] printk: extract kmsg-related routines from printk.c to kmsg.c Kazimierz Krosman
2016-02-25 21:47   ` [PATCH v6 0/8] Additional kmsg devices Tejun Heo
     [not found]     ` <20160225214714.GJ6092-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-02-26 13:22       ` Kazimierz Krosman
2016-02-26 14:47         ` Petr Mladek
2016-02-27 11:54           ` Tejun Heo
2016-02-24 11:53 ` [PATCH v6 2/8] printk: add one function for storing log in proper format Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 3/8] kmsg: introduce additional kmsg devices support Kazimierz Krosman
2016-02-26 14:05   ` Petr Mladek [this message]
2016-02-24 11:53 ` [PATCH v6 4/8] kmsg: add additional buffers support to memory class Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 5/8] kmsg: add function for adding and deleting additional buffers Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 6/8] kmsg: add ioctl for adding and deleting kmsg* devices Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 7/8] kmsg: add ioctl for kmsg* devices operating on buffers Kazimierz Krosman
2016-02-24 11:53 ` [PATCH v6 8/8] kmsg: selftests Kazimierz Krosman

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=20160226140510.GE3305@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=corbet@lwn.net \
    --cc=daniel@zonque.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=k.krosman@samsung.com \
    --cc=k.lewandowsk@samsung.com \
    --cc=kay.sievers@vrfy.org \
    --cc=knhoon.baik@samsung.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=m.niesluchow@samsung.com \
    --cc=peter@hurleysoftware.com \
    --cc=richard.weinberger@gmail.com \
    --cc=tj@kernel.org \
    --cc=vvs@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).