From: "Theodore Ts'o" <tytso@mit.edu>
To: Dan Carpenter <dan.carpenter@oracle.com>
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 18:22:00 -0400 [thread overview]
Message-ID: <Yq5QCJI7qC80AtxL@mit.edu> (raw)
In-Reply-To: <Yq2bzesQ5H+DrA47@kili>
On Sat, Jun 18, 2022 at 12:33:01PM +0300, Dan Carpenter wrote:
> 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.
That's I only pushed it out Friday night (US/Eastern), and Stephen
Rothwell creates new linux-next release based on snapshots taken
Monday through Friday in the Morning (AU/Canberra time).
Things have been crazy busy, so a last set of ext4 backports only
happened Friday starting around 10pm localtime. (Yes, I have no
life.)
> 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.
I did add a Fixes tag in what is in the ext4 tree. I don't always
mention when I've rewritten since that requries manual editing of the
"b4 ty" generated acknowledgement.
In the ideal world when I rewrite the one-line snapshot, at the *very*
least it should show up in the Applied/thanks. Maybe something like
this:
[1/1] ext4: change variable "count" to signed integer
commit: fefb759df063599ad483422eb07ef8e14c612cc2
rewritten summary: ext4: make variable "count" signed
... and if the commit description is rewritten, maybe the "b4 ty"
e-mail should mention it. (Very often I end up rewriting commit
descriptions, especially when the original poster's first language is
not English.)
For the record, this is what is in the ext4 tree that I plan to push
to Linus is:
commit fefb759df063599ad483422eb07ef8e14c612cc2
Author: Ding Xiang <dingxiang@cmss.chinamobile.com>
Date: Mon May 30 18:00:47 2022 +0800
ext4: make variable "count" signed
Since dx_make_map() may return -EFSCORRUPTED now, so change "count" to
be a signed integer so we can correct check for an error code returned
by dx_make_map().
Fixes: 46c116b920eb ("ext4: verify dir block before splitting it")
Signed-off-by: Ding Xiang <dingxiang@cmss.chinamobile.com>
Link: https://lore.kernel.org/r/20220530100047.537598-1-dingxiang@cmss.chinamobile.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cheers,
- Ted
next prev parent reply other threads:[~2022-06-18 22:22 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
2022-06-18 22:22 ` Theodore Ts'o [this message]
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=Yq5QCJI7qC80AtxL@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=dan.carpenter@oracle.com \
--cc=dingxiang@cmss.chinamobile.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox