From: Yehuda Sadeh <yehuda@hq.newdream.net>
To: Jason Baron <jbaron@redhat.com>
Cc: Thomas Renninger <trenn@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
yehuda@hq.newdream.net
Subject: Re: Dynamic Debug broken on 2.6.35-rc3?
Date: Mon, 12 Jul 2010 14:21:46 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1007121359010.17416@yehudasa-desktop> (raw)
In-Reply-To: <20100712162140.GA2925@redhat.com>
On Mon, 12 Jul 2010, Jason Baron wrote:
...
> I will re-post the above as a separate thread. Also, I should probably
> post a patch to add myself to the MAINTAINERS file, since I didn't see
> Yehuda's patch until now...
Yeah, I wasn't sure who was responsible for this module. Wasn't clear
from the log.
>
>> If Yehuda's patch is fixing this already, we still need it backported for
>> 2.6.34 stable kernel and further?
>>
>
> Yes, patch might need to be adjusted a bit but is still relevant for
> 2.6.34 stable. The situation was exacerbated by:
>
> commit 3bafeb6247042dcbb72b0141ec7c7107de9f0b99
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Sat Jun 5 11:17:36 2010 -0600
>
> module: move find_module check to end
>
> during the 2.6.35 time frame.
>
Right. Looking at the code, pre .35-rc2 loads the dynamic debug code after
verifying that the module is loadable. So it's a bit harder to hit
it, although it can still fail at the following module_finalize() or at
the parse_args(), so the problem is there.
Yehuda
next prev parent reply other threads:[~2010-07-12 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 15:44 Thomas Renninger
2010-07-01 16:26 ` Jason Baron
2010-07-02 16:55 ` Thomas Renninger
2010-07-08 21:39 ` Jason Baron
2010-07-08 21:53 ` Andrew Morton
2010-07-09 11:03 ` Thomas Renninger
2010-07-09 13:30 ` Jason Baron
2010-07-12 14:24 ` Thomas Renninger
2010-07-12 16:21 ` Jason Baron
2010-07-12 21:21 ` Yehuda Sadeh [this message]
2010-07-12 21:47 ` Andi Kleen
2010-07-13 20:38 ` Yehuda Sadeh
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=alpine.DEB.2.00.1007121359010.17416@yehudasa-desktop \
--to=yehuda@hq.newdream.net \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hare@suse.de \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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
all inboxes | Powered by JetHome®