LKML Archive on
help / color / mirror / Atom feed
From: Rusty Russell <>
To: Alexey Dobriyan <>
Subject: Re: [PATCH v3] Race between cat /proc/kallsyms and rmmod
Date: Tue, 20 Mar 2007 10:35:11 +1100	[thread overview]
Message-ID: <1174347311.11680.31.camel@localhost.localdomain> (raw)
In-Reply-To: <>

On Mon, 2007-03-19 at 17:33 +0300, Alexey Dobriyan wrote:
> Iterating code of /proc/kallsyms calls module_get_kallsym() which grabs
> and drops module_mutex internally and returns "struct module *",
> module is removed, aforementioned "struct module *" is used in non-trivial
> way.

Hi Alexey,

	I like the patch, but I wonder if passing the lengths for the symbol
and module name is overkill?  There are KSYM_NAME_LEN and
MODULE_NAME_LEN constants, after all, and we could just have the callers
use buffers of sufficient size.  Simplifies the code and reduces
confusion if someone passes a small buffer and it gets surprisingly


      parent reply	other threads:[~2007-03-19 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 11:42 [PATCH RESEND 1/2] Race between cat /proc/kallsyms and rmmod Alexey Dobriyan
2007-03-19 14:33 ` [PATCH v3] " Alexey Dobriyan
2007-03-19 15:20   ` Paulo Marques
2007-03-19 23:35   ` Rusty Russell [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1174347311.11680.31.camel@localhost.localdomain \ \ \ \ \ \ \

* 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).