From: Andrew Morton <akpm@osdl.org>
To: Evgeniy Dushistov <dushistov@mail.ru>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] ufs: ufs_trunc_indirect: infinite cycle
Date: Sun, 14 May 2006 02:47:52 -0700 [thread overview]
Message-ID: <20060514024752.2d666443.akpm@osdl.org> (raw)
In-Reply-To: <20060514081807.GA9802@rain.homenetwork>
Evgeniy Dushistov <dushistov@mail.ru> wrote:
>
> The situation the same: in ufs_trunc_(not direct),
> we read block,
> check if count of links to it is equal to one,
> if so we finish cycle, if not continue.
> Because of "count of links" always >=2 this operation cause
> infinite cycle and hang up the kernel.
okay, but do we know what that code which you removed was actually intended
to do?
Do you know whether 2.4 kernels exhibit the same bug? If not, we might have
accidentally broken UFS at some stage.
next prev parent reply other threads:[~2006-05-14 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 8:18 [PATCH 1/3] ufs: ufs_trunc_indirect: infinite cycle Evgeniy Dushistov
2006-05-14 9:47 ` Andrew Morton [this message]
2006-05-14 11:47 ` Evgeniy Dushistov
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=20060514024752.2d666443.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dushistov@mail.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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