From: Jan Kara <jack@suse.cz>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: [PATCH 0/2] Fix oops / warning when allocation of symlink fails
Date: Mon, 13 Jul 2009 21:29:25 +0200 [thread overview]
Message-ID: <1247513367-5609-1-git-send-email-jack@suse.cz> (raw)
Hi,
the two patches in this series fix a problem for ext3/ext4 when we fail
to allocate blocks for a symlink. In ext3 this could lead to a memory
corruption (since freed inode could remain on in-memory orphan list), in
ext4 just to some warnings on the next mount (Sigh. Ted was maybe right
we should always do ext?_orphan_del() regardless of calling truncate ;)).
Ted, would you please merge the patch (or both if you like)? Thanks.
Honza
next reply other threads:[~2009-07-13 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 19:29 Jan Kara [this message]
2009-07-13 19:29 ` [PATCH 1/2] ext3: Fix truncation of symlinks after failed write Jan Kara
2009-07-13 19:29 ` [PATCH 2/2] ext4: " Jan Kara
2009-07-15 6:18 ` Aneesh Kumar K.V
2009-07-15 10:28 ` Jan Kara
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=1247513367-5609-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@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).