From: Randy Dunlap <rdunlap@xenotime.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Jon Masters <jcm@redhat.com>,
linux-kernel@vger.kernel.org,
Lucas De Marchi <lucas.demarchi@profusion.mobi>
Subject: Re: [PATCH] modules: sysfs - export: taint, address, size
Date: Mon, 09 Jan 2012 10:40:10 -0800 [thread overview]
Message-ID: <4F0B348A.3070708@xenotime.net> (raw)
In-Reply-To: <CAPXgP12rUUYfRy6QB5Z4Rwdday3hNHubCsSRY4gMDYuQGs3oJg@mail.gmail.com>
On 01/09/2012 04:44 AM, Kay Sievers wrote:
> On Mon, Jan 9, 2012 at 08:27, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> On Sat, 07 Jan 2012 16:44:36 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
>>> Recent tools do not use /proc to retrieve module information. A few values
>>> are currently missing from sysfs.
>>
>> Well, strace says lsmod still does. Is libkmod doing something
>> different?
>
> Yes, kmod used /sys only.
>
> There is current code to read the size, to provide the 'lsmod' output,
> but that will be removed.
>
>> Should we be deprecating /proc/modules?
>
> In the longer run, yes.
Deprecate it for udev? OK.
what about other users of it?
> We still aim for leaving everything that isn't process- or
> namespace-related (which, with some stretch is always process-related)
> alone, and use /sys for it.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-01-09 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 15:44 [PATCH] modules: sysfs - export: taint, address, size Kay Sievers
2012-01-09 7:27 ` Rusty Russell
2012-01-09 12:44 ` Kay Sievers
2012-01-09 18:40 ` Randy Dunlap [this message]
2012-01-09 22:44 ` Rusty Russell
2012-01-10 16:47 ` Kay Sievers
2012-01-10 23:54 ` Rusty Russell
2012-01-11 1:56 ` Lucas De Marchi
2012-01-09 15:52 ` Nick Bowler
2012-01-09 23:07 ` Greg KH
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=4F0B348A.3070708@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jcm@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.