linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Samson Yeung <samson.yeung@oracle.com>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: modinfo crc32 broken after fd44a98ae2eb
Date: Thu, 28 Jan 2016 17:21:34 -0200	[thread overview]
Message-ID: <CAKi4VA+MC=hXMQ2kHi4_Xv2w7qQcG443zj9+rKo_JKoSzgDvYQ@mail.gmail.com> (raw)
In-Reply-To: <56A91B6A.2060205@oracle.com>

Hi Samson,

On Wed, Jan 27, 2016 at 5:32 PM, Samson Yeung <samson.yeung@oracle.com> wrote:
> Hi all,
>
> Please reply directly as I am not on this list.
>
> Commit "fd44a98ae2eb Fix race while loading modules" also broke 'modinfo
> crc32', specifically, for me.
>
> Is this a bug, is it something strange going on with crc32, or is it
> intended behavior?

breaking is never intended ;-). What do you mean by "break"? Does it crash?

I can't see how this commit is related to modinfo. You will need to
give more details. Check if you can get the output by passing the
complete path to the module and make sure it's actually a module (and
not builtin) in your kernel configuration

Lucas De Marchi

  reply	other threads:[~2016-01-28 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 19:32 modinfo crc32 broken after fd44a98ae2eb Samson Yeung
2016-01-28 19:21 ` Lucas De Marchi [this message]
2016-01-28 22:40   ` Samson Yeung
2016-01-29  1:35     ` Lucas De Marchi
2016-01-29  5:54       ` Duplicated module names Rusty Russell
2016-01-29  7:04         ` Tomi Valkeinen
2016-01-29 10:20         ` Herbert Xu
2016-01-29 15:58         ` Sudeep Holla
2016-01-29 19:08         ` Lucas De Marchi

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='CAKi4VA+MC=hXMQ2kHi4_Xv2w7qQcG443zj9+rKo_JKoSzgDvYQ@mail.gmail.com' \
    --to=lucas.de.marchi@gmail.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=samson.yeung@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).