linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: hujianyang <hujianyang@huawei.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH resend] UBIFS: Add log overlap assertions
Date: Thu, 31 Jul 2014 15:54:41 +0300	[thread overview]
Message-ID: <1406811281.20616.6.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <53D85A81.3010106@huawei.com>

On Wed, 2014-07-30 at 10:37 +0800, hujianyang wrote:
> We use a circle area to record the log nodes in ubifs. This log area
> should not be overlapped. But after researching the code, I found
> some conditions may lead log head wraps log ltail. Although we've
> fixed the problems discovered, there may be some other issues still
> left.
> 
> This patch adds assertions where lhead changes to next leb to make
> sure ltail is not wrapped.

Pushed to linux-ubifs.

-- 
Best Regards,
Artem Bityutskiy

      reply	other threads:[~2014-07-31 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  2:37 [PATCH resend] UBIFS: Add log overlap assertions hujianyang
2014-07-31 12:54 ` Artem Bityutskiy [this message]

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=1406811281.20616.6.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=hujianyang@huawei.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;
as well as URLs for NNTP newsgroup(s).