From: Theodore Tso <tytso@mit.edu>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, David Smith <dsmith@redhat.com>,
Roland McGrath <roland@redhat.com>,
Sam Ravnborg <sam@ravnborg.org>,
Wenji Huang <wenji.huang@oracle.com>,
Takashi Nishiie <t-nishiie@np.css.fujitsu.com>
Subject: Re: [PATCH] Marker depmod fix core kernel list
Date: Sat, 4 Oct 2008 11:24:56 -0400 [thread overview]
Message-ID: <20081004152456.GB23398@mit.edu> (raw)
In-Reply-To: <20081003195436.GA13506@Krystal>
On Fri, Oct 03, 2008 at 03:54:36PM -0400, Mathieu Desnoyers wrote:
> Here is a fix that should take care if this problem. Given I am not the
> modpost expert, let's see if I can get an ACK from Sam.
Tested-by: "Theodore Ts'o" <tytso@mit.edu>
It works, thanks!! Can we get this pushed to Linus before 2.6.28
opens? This is technically a regression since it was broken around
2.6.27-rc1.
Also, something we need to consider is getting distributions to ship
Modules.markers, and where it should be installed. I would argue that
it belongs in /lib/modules/`uname -r`, so maybe "make modules_install"
should put it there? This attention to deployability is going to be
important if markers are to be successfully used by applications such
as Systemtap.
- Ted
next prev parent reply other threads:[~2008-10-04 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 19:16 Markers in (non-module) kernel code? Theodore Ts'o
2008-10-03 19:54 ` [PATCH] Marker depmod fix core kernel list Mathieu Desnoyers
2008-10-04 15:24 ` Theodore Tso [this message]
2008-10-06 4:08 ` Greg KH
2008-10-10 9:39 ` Ingo Molnar
2008-10-10 9:39 ` Ingo Molnar
2008-10-10 15:48 ` Greg KH
2008-10-10 9:46 ` [PATCH RESEND] early_ioremap has a fencepost error Alan Cox
2008-10-10 10:21 ` Ingo Molnar
2008-10-06 20:23 ` [PATCH] Marker depmod fix core kernel list Roland McGrath
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=20081004152456.GB23398@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=dsmith@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=sam@ravnborg.org \
--cc=t-nishiie@np.css.fujitsu.com \
--cc=wenji.huang@oracle.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).