From: Al Viro <viro@zeniv.linux.org.uk>
To: Colin King <colin.king@canonical.com>
Cc: linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] binfmt_elf: fix unsigned regset0_size compared to less than zero
Date: Mon, 27 Jul 2020 18:43:15 +0000 [thread overview]
Message-ID: <20200727184315.GK794331@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200727174054.154765-1-colin.king@canonical.com>
On Mon, Jul 27, 2020 at 06:40:54PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Variable regset0_size is an unsigned int and it is being checked
> for an error by checking if it is less than zero, and hence this
> check is always going to be false. Fix this by making the variable
> regset0_size signed.
Folded and pushed...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@zeniv.linux.org.uk>
To: Colin King <colin.king@canonical.com>
Cc: linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] binfmt_elf: fix unsigned regset0_size compared to less than zero
Date: Mon, 27 Jul 2020 19:43:15 +0100 [thread overview]
Message-ID: <20200727184315.GK794331@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200727174054.154765-1-colin.king@canonical.com>
On Mon, Jul 27, 2020 at 06:40:54PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Variable regset0_size is an unsigned int and it is being checked
> for an error by checking if it is less than zero, and hence this
> check is always going to be false. Fix this by making the variable
> regset0_size signed.
Folded and pushed...
next prev parent reply other threads:[~2020-07-27 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 17:40 [PATCH][next] binfmt_elf: fix unsigned regset0_size compared to less than zero Colin King
2020-07-27 17:40 ` Colin King
2020-07-27 18:43 ` Al Viro [this message]
2020-07-27 18:43 ` Al Viro
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=20200727184315.GK794331@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.