From: Ruslan Bilovol <ruslan.bilovol@ti.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Misc ext4 fixes
Date: Mon, 3 Jun 2013 13:00:14 +0300 [thread overview]
Message-ID: <1370253616-8173-1-git-send-email-ruslan.bilovol@ti.com> (raw)
Hello guys,
Here are few patches that add sanity checks
before dereferencing some pointers inside of
ext4/jbd2 functions and help to avoid some crashes
on systems under high load and limited resources.
I met them in next usecase: writing a high-bitrate
video to ext4 partition from HD webcam. The issues
appear very rare.
I do not know if these issues are already fixed in some
maintainers repo, but they are still applicable
to 3.10-rc4 tag on which they are based on.
I understand that just sanity checking may not be
enough and the root cause may be in some other
place, so I hope the patches will be reviewed
by ext4 guru as well.
Regards,
Ruslan
Ruslan Bilovol (2):
jbd2: check bh->b_data for NULL in jbd2_journal_get_descriptor_buffer
before memset()
ext4: add sanity checks in __ext4_check_dir_entry
fs/ext4/dir.c | 8 ++++++--
fs/jbd2/journal.c | 2 +-
2 files changed, 7 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-06-03 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 10:00 Ruslan Bilovol [this message]
2013-06-03 10:00 ` [PATCH 1/2] jbd2: check bh->b_data for NULL in jbd2_journal_get_descriptor_buffer before memset() Ruslan Bilovol
2013-06-03 15:33 ` Theodore Ts'o
2013-06-04 11:15 ` Ruslan Bilovol
2013-06-04 13:37 ` Theodore Ts'o
2013-06-06 8:02 ` Ruslan Bilovol
2013-06-03 10:00 ` [PATCH 2/2] ext4: add sanity checks in __ext4_check_dir_entry Ruslan Bilovol
2013-06-03 15:40 ` Theodore Ts'o
2013-06-04 11:17 ` Ruslan Bilovol
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=1370253616-8173-1-git-send-email-ruslan.bilovol@ti.com \
--to=ruslan.bilovol@ti.com \
--cc=adilger.kernel@dilger.ca \
--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;
as well as URLs for NNTP newsgroup(s).