linux-kernel - Re: [PATCH v2] printk: Modify operators of printed_len and text

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: <20170711083047.GO23069@pathway.suse.cz>
Date:   Tue, 11 Jul 2017 10:30:47 +0200
From:   Petr Mladek <pmladek@...e.com>
To:     Pierre Kuo <vichy.kuo@...il.com>
Cc:     sergey.senozhatsky@...il.com, rostedt@...dmis.org,
        linux-kernel@...r.kernel.org, joe@...ches.com
Subject: Re: [PATCH v2] printk: Modify operators of printed_len and text_len

On Tue 2017-07-11 14:40:55, Pierre Kuo wrote:
> With commit <ddb9baa82226> ("printk: report lost messages in printk
> safe/nmi contexts") and commit <8b1742c9c207> ("printk: remove zap_locks()
> function"), it seems we can remove initialization, "=0", of text_len and
> directly assign result of log_output to printed_len.

Just one small thing. The <> brackets should not be there around
the sha1 commit id. Otherwise, the patch looks fine to me.

Acked-by: Petr Mladek <pmladek@...e.com>

You do not need to resend the patch. I'll remove the brackets
when applying the patch. I'll wait few more days just in case
anyone has more comments on this patch.

Best Regards,
Petr