From: Artem Bityutskiy <dedekind1@gmail.com>
To: Adam Thomas <adamthomas1111@gmail.com>
Cc: linux-mtd@lists.infradead.org, adrian.hunter@intel.com
Subject: Re: [PATCH v2 1/2] UBIFS: fix use of freed ubifs_orphan objects
Date: Mon, 04 Feb 2013 12:31:42 +0200 [thread overview]
Message-ID: <1359973902.13791.35.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1359844351-5889-2-git-send-email-adamthomas1111@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Sat, 2013-02-02 at 22:32 +0000, Adam Thomas wrote:
> The last orphan in the cnext list has its cnext set to NULL. Because
> of that, ubifs_delete_orphan assumes that it is not on the cnext list
> and frees it immediately instead of adding it to the dnext list. The
> freed orphan is later modified by write_orph_node.
>
> This can cause various inconsistencies including directory entries
> that cannot be removed and this error:
>
> UBIFS error (pid 20685): layout_cnodes: LPT out of space at LEB 14:129009 needing 17, done_ltab 1, done_lsave 1
>
> This is a regression introduced by
> "7074e5eb UBIFS: remove invalid reference to list iterator variable".
>
> This change adds an explicit flag to ubifs_orphan indicating whether
> it is pending commit.
>
> Signed-off-by: Adam Thomas <adamthomas1111@gmail.com>
Pushed both to linux-ubifs.git, added 'Cc: stable@vger.kernel.org'.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-02-04 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 1:28 UBIFS: a pair of orphan bugs Adam Thomas
2013-01-28 1:28 ` [PATCH 1/2] UBIFS: fix use of freed ubifs_orphan objects Adam Thomas
2013-02-01 13:23 ` Adrian Hunter
2013-02-02 22:32 ` Adam Thomas
2013-02-02 22:32 ` [PATCH v2 " Adam Thomas
2013-02-04 10:31 ` Artem Bityutskiy [this message]
2013-01-28 1:28 ` [PATCH 2/2] UBIFS: fix double free of " Adam Thomas
2013-02-01 13:23 ` Adrian Hunter
2013-02-02 22:35 ` [PATCH v2 " Adam Thomas
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=1359973902.13791.35.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=adamthomas1111@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=linux-mtd@lists.infradead.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