linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samson Yeung <samson.yeung@oracle.com>
To: linux-modules@vger.kernel.org
Subject: modinfo crc32 broken after fd44a98ae2eb
Date: Wed, 27 Jan 2016 11:32:58 -0800	[thread overview]
Message-ID: <56A91B6A.2060205@oracle.com> (raw)

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?

This happens on the official RedHat EL7 kernels, and also Ubuntu Wily's 
kernel.


Regards,
-Samson


             reply	other threads:[~2016-01-27 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 19:32 Samson Yeung [this message]
2016-01-28 19:21 ` modinfo crc32 broken after fd44a98ae2eb Lucas De Marchi
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=56A91B6A.2060205@oracle.com \
    --to=samson.yeung@oracle.com \
    --cc=linux-modules@vger.kernel.org \
    /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).