From: Zheng Yejian <zhengyejian1@huawei.com>
To: <linux-kernel@vger.kernel.org>
Cc: <akpm@linux-foundation.org>, <rdunlap@infradead.org>,
<vbabka@suse.cz>, <guohanjun@huawei.com>,
<zhangjinhao2@huawei.com>
Subject: [PATCH 0/2] Fix encode_comp_t()
Date: Sat, 15 May 2021 22:06:29 +0800 [thread overview]
Message-ID: <20210515140631.369106-1-zhengyejian1@huawei.com> (raw)
Type conversion in encode_comp_t() may look a bit problematic.
Zheng Yejian (2):
acct: Fix accuracy loss for input value of encode_comp_t()
acct: Fix potential integer overflow in encode_comp_t()
kernel/acct.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2021-05-15 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 14:06 Zheng Yejian [this message]
2021-05-15 14:06 ` [PATCH 1/2] acct: Fix accuracy loss for input value of encode_comp_t() Zheng Yejian
2021-05-15 14:06 ` [PATCH 2/2] acct: Fix potential integer overflow in encode_comp_t() Zheng Yejian
2022-11-02 3:52 ` [PATCH 0/2] Fix encode_comp_t() Zheng Yejian
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=20210515140631.369106-1-zhengyejian1@huawei.com \
--to=zhengyejian1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
--cc=zhangjinhao2@huawei.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).