From: Erez Zadok <ezk@cs.sunysb.edu>
To: "Jörn Engel" <joern@logfs.org>
Cc: Erez Zadok <ezk@cs.sunysb.edu>,
dwmw2@infradead.org, linux-mtd@lists.infradead.org,
peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block2mtd lockdep_init_map warning
Date: Sun, 6 Jan 2008 14:11:47 -0500 [thread overview]
Message-ID: <200801061911.m06JBldW020012@agora.fsl.cs.sunysb.edu> (raw)
In-Reply-To: Your message of "Sun, 06 Jan 2008 14:13:43 +0100." <20080106131343.GA3120@lazybastard.org>
In message <20080106131343.GA3120@lazybastard.org>, =?utf-8?B?SsO2cm4=?= Engel writes:
> Maybe it is not obvious that I maintain this driver and would like to be
> kept on Cc:. Will send a patch to fix that shortly.
I was looking in MAINTAINERS, and you weren't listed on the main MTD section
as a maintainer. Perhaps an update?
If you get a patch, I'd love to test it.
> On Sun, 6 January 2008 02:17:32 -0500, Erez Zadok wrote:
[...]
> > In lieu of a better fix, is this patch acceptable?
>
> Not for me. I don't mind if you keep such a hack until a proper
> solution if found in your private tree. But it is a horrible solution
> to a problem introduced elsewhere.
Yup, that's what I figured. I'll keep this ugly hack but I won't push it to
my unionfs tree on kernel.org.
> Ingo, Peter, does either of you actually care about this problem? In
> the last round when I debugged this problem there was a notable lack of
> reaction from either of you.
The problem appears to be an interaction of two components--module loading
and lockdep--that's perhaps why it wasn't given enough attention.
I run a lot of regression tests w/ unionfs on top of many different file
systems, and monitoring for all sorts of problems, including lockdep
warnings. So it's frustrating that each time I get to test w/ jffs2, I get
this lockdep warning, and lockdep shuts down until a reboot. That kills my
automated testing and masks out possible other lockdep problems (that's why
I wanted to at least have some workaround). Other lockdep problems I
reported with other subsystems had been fixed within days; this one,
unfortunately, has lingered for a while. So if a fix can be made in a
reasonable time-frame, I'd really appreciate it.
Thanks,
Erez.
next prev parent reply other threads:[~2008-01-06 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 7:17 [PATCH] block2mtd lockdep_init_map warning Erez Zadok
2008-01-06 13:13 ` Jörn Engel
2008-01-06 13:39 ` Peter Zijlstra
2008-01-06 19:11 ` Erez Zadok [this message]
2008-01-06 21:25 ` Jörn Engel
2008-01-07 10:05 ` Peter Zijlstra
2008-01-07 10:20 ` Jörn Engel
2008-01-07 10:34 ` Peter Zijlstra
2008-01-08 0:47 ` Rusty Russell
2008-01-16 8:16 ` Peter Zijlstra
2008-01-16 21:20 ` Jörn Engel
2008-01-20 21:01 ` Erez Zadok
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=200801061911.m06JBldW020012@agora.fsl.cs.sunysb.edu \
--to=ezk@cs.sunysb.edu \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=peterz@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).