From: "Thomas Bächler" <thomas@archlinux.org>
To: stable@kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Greg KH <greg@kroah.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
richard@netwichtig.de
Subject: Apply 'ext4: fix NULL pointer dereference in print_daily_error_info()' to 2.6.36.y?
Date: Mon, 22 Nov 2010 21:45:00 +0100 [thread overview]
Message-ID: <4CEAD64C.5090600@archlinux.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hello,
we discovered this kernel panic [1] in 2.6.36. Apparently, commit
a1c6c5698d53db4c47a25c3a8d11731a4d7b8370 was supposed to fix it, but
never made it to 2.6.36(.1). Can this please be queued up for the next
stable kernel? This is a pretty serious issue and can reproducibly crash
the kernel.
This was mentioned at [2], but nothing more happened. Added some ext4
guys to CC.
Regards
Thomas
[1] http://richard.qasl.de/panic.JPG
[2] http://lkml.org/lkml/2010/11/20/64
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
reply other threads:[~2010-11-22 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CEAD64C.5090600@archlinux.org \
--to=thomas@archlinux.org \
--cc=greg@kroah.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@netwichtig.de \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable@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 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.