From: Dan Carpenter <dan.carpenter@oracle.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: adilger.kernel@dilger.ca,
Ding Xiang <dingxiang@cmss.chinamobile.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: [PATCH] ext4: change variable "count" to signed integer
Date: Sat, 18 Jun 2022 12:33:01 +0300 [thread overview]
Message-ID: <Yq2bzesQ5H+DrA47@kili> (raw)
In-Reply-To: <165552108974.634564.2634497659089601268.b4-ty@mit.edu>
On Fri, Jun 17, 2022 at 10:59:01PM -0400, Theodore Ts'o wrote:
> On Mon, 30 May 2022 18:00:47 +0800, Ding Xiang wrote:
> > Since dx_make_map() may return -EFSCORRUPTED now,
> > so change "count" to signed integer.
> >
> >
>
> Applied, thanks!
>
> [1/1] ext4: change variable "count" to signed integer
> commit: fefb759df063599ad483422eb07ef8e14c612cc2
>
There was some kind of process error here...
1) That commit somehow never made it to linux-next.
2) No Fixes tag. Presumably Greg searches for Fixes tags before he back
ports patches. The original commit 46c116b920eb ("ext4: verify dir
block before splitting it") has been back ported to stable already.
3) I don't know why I didn't send a patch for this bug. I looked at it
on May 23 but never sent a patch. Sorry?
4) There are a dozen other static checkers which are supposed to have
warned about this. I search lore.kernel.org for 46c116b920eb
and 46c116b920ebec58031f0a78c5ea9599b0d2a371 but I couldn't find any
static checker warnings.
regards,
dan carpenter
next prev parent reply other threads:[~2022-06-18 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 10:00 [PATCH] ext4: change variable "count" to signed integer Ding Xiang
2022-06-18 2:59 ` Theodore Ts'o
2022-06-18 9:33 ` Dan Carpenter [this message]
2022-06-18 22:22 ` Theodore Ts'o
2022-06-20 5:45 ` Dan Carpenter
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=Yq2bzesQ5H+DrA47@kili \
--to=dan.carpenter@oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=dingxiang@cmss.chinamobile.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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