linux-kernel - Re: [PATCH] Add hsize argument in write_buf call of pstore_ftrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1372755248.3616.5.camel@pasglop>
Date:	Tue, 02 Jul 2013 18:54:08 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Aruna Balakrishnaiah <aruna@...ux.vnet.ibm.com>
Cc:	linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org,
	fengguang.wu@...el.com, kbuild-all@...org, rostedt@...dmis.org
Subject: Re: [PATCH] Add hsize argument in write_buf call of
 pstore_ftrace_call

On Tue, 2013-07-02 at 11:06 +0530, Aruna Balakrishnaiah wrote:
> Incorporate the addition of hsize argument in write_buf callback
> of pstore.

Thanks. I've added that to powerpc-next. It should hit Stephen tomorrow.

Cheers,
Ben.

> Signed-off-by: Aruna Balakrishnaiah <aruna@...ux.vnet.ibm.com>
> ---
> 
>  fs/pstore/ftrace.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/pstore/ftrace.c b/fs/pstore/ftrace.c
> index 43b1280..76a4eeb 100644
> --- a/fs/pstore/ftrace.c
> +++ b/fs/pstore/ftrace.c
> @@ -44,7 +44,7 @@ static void notrace pstore_ftrace_call(unsigned long ip,
>  	rec.parent_ip = parent_ip;
>  	pstore_ftrace_encode_cpu(&rec, raw_smp_processor_id());
>  	psinfo->write_buf(PSTORE_TYPE_FTRACE, 0, NULL, 0, (void *)&rec,
> -			  sizeof(rec), psinfo);
> +			  0, sizeof(rec), psinfo);
>  
>  	local_irq_restore(flags);
>  }


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