From: Theodore Ts'o <tytso@mit.edu>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: nborisov <n.borisov.lkml@gmail.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: Open bugs found by fuzzing as of 2016-07-30
Date: Sun, 31 Jul 2016 00:37:27 -0400 [thread overview]
Message-ID: <20160731043727.GB12853@thunk.org> (raw)
In-Reply-To: <579CFF1B.40201@oracle.com>
On Sat, Jul 30, 2016 at 09:25:15PM +0200, Vegard Nossum wrote:
>
> It seems that most of them are indeed tagged for stable; for the patches
> I submitted or reported for, it looks like the only one without a stable
> tag is a warning about large memory allocations -- commit
> 7bc9491645118c9461bd21099c31755ff6783593.
... and that's an oversight. Commit 7bc949164511 ("ext4: verify
extent header depth") should have been marked for stable. I've added
stable@vger.kernel.org to the cc. Could you please it to the stable
kernels? Many thanks!!
- Ted
next prev parent reply other threads:[~2016-07-31 4:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 13:04 Open bugs found by fuzzing as of 2016-07-30 Vegard Nossum
2016-07-30 18:39 ` nborisov
2016-07-30 19:25 ` Vegard Nossum
2016-07-31 4:37 ` Theodore Ts'o [this message]
2016-08-03 5:43 ` Greg KH
2016-08-04 2:58 ` Theodore Ts'o
2016-08-01 4:55 ` Theodore Ts'o
2016-08-01 7:33 ` Vegard Nossum
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=20160731043727.GB12853@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=n.borisov.lkml@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vegard.nossum@oracle.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).