From: "Theodore Tso" <tytso@mit.edu>
To: Junzhe Yu <junzheyu1@gmail.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info
Date: Thu, 6 Aug 2026 10:35:05 -0400 [thread overview]
Message-ID: <anSa1gy5xsHhtG-Y@mit.edu> (raw)
In-Reply-To: <65c955b0-716b-4599-b925-59c2782e38b4@gmail.com>
On Tue, Aug 04, 2026 at 12:55:33PM -0500, Junzhe Yu wrote:
> Resend: previous attempt was rejected by vger for containing HTML.
This attempt still had a patch with mangled whitespace. Trying to
send patches using gmail is... fraught. Please a take a look at [1]
for future submissions, thanks. This patch was simple enough that I
was able to apply it by hand.
[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html
- Ted
next prev parent reply other threads:[~2026-08-06 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 4:55 [PATCH] ext4: guard against NULL s_group_info in ext4_get_group_info Junzhe Yu
2026-08-06 14:35 ` Theodore Tso [this message]
2026-08-06 15:00 ` Theodore Ts'o
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=anSa1gy5xsHhtG-Y@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=junzheyu1@gmail.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