From: Theodore Ts'o <tytso@mit.edu>
To: Volodymyr Mieshkov <volodymyr.mieshkov@ti.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: The patch at 'patchwork.ozlabs.org/patch/192079'
Date: Mon, 22 Oct 2012 00:42:52 -0400 [thread overview]
Message-ID: <20121022044252.GE4768@thunk.org> (raw)
In-Reply-To: <507FE1C9.3070301@ti.com>
On Thu, Oct 18, 2012 at 02:02:33PM +0300, Volodymyr Mieshkov wrote:
> Hi,
>
> My name is Volodymyr. Sorry, I don't know your name, but I'd like to
> ask you about some issue.
> Recently I got an Linux kernel panic on my system and submitted the
> patch to prevent it here: http://patchwork.ozlabs.org/patch/192079/.
> Before that I found at one of the forum a thread that described a
> similar problem,
> and you suggested the patch to fix it:
> http://www.gossamer-threads.com/lists/linux/kernel/1326686.
> I used your idea, and I would like to re-submit the path with your
> authorship.
> Sorry, I must ask you before I've submitted the patch. I don't want
> to break your authorship.
Hi Volodymyr,
The patch which I suggested in the thread which you referenced was
intended to debug the bug to find the real root cause of the issue.
If in fact the WARN() is triggering on your 3.0 system, then there's a
bug that we should be trying to fix.
Instead of using this patch to paper over the problem, I'd much rather
see if we can figure out why jinode was NULL in the first place. Can
you reliably reproduce this failure?
Regards,
- Ted
parent reply other threads:[~2012-10-22 4:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <507FE1C9.3070301@ti.com>]
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=20121022044252.GE4768@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=volodymyr.mieshkov@ti.com \
/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).