From: marcin@mejor.pl
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs tree] Can't load bcache module second time
Date: Sat, 06 Aug 2016 14:20:12 +0200 [thread overview]
Message-ID: <36b48a9e235db2188b5063ebe6d23e4a@mejor.pl> (raw)
In-Reply-To: <alpine.LRH.2.11.1608051243330.10662@mail.ewheeler.net>
Hi!
W dniu 2016-08-05 21:47, Eric Wheeler napisał(a):
> On Fri, 5 Aug 2016, Marcin Mirosław wrote:
>
>> Hi!
>> Kernel is on commit 1c99b8fdce303e0961ee982919c890bf156ed775.
>> Host is freshly rebooted.
>> # grep bcache /proc/modules
>> # modprobe bcache && rmmod bcache && modprobe bcache
>> modprobe: ERROR: could not insert 'bcache': Cannot allocate memory
>>
>> In dmesg I've got:
>> > Aug 5 15:39:14 localhost kernel: [ 249.911487] WARNING: CPU: 3 PID: 17892 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x5d/0x70
>> > Aug 5 15:39:14 localhost kernel: [ 249.911490] sysfs: cannot create duplicate filename '/devices/virtual/bcache'
>
> Hmm, it looks like something in sysfs might not get unregistered at
> module
> unload time, so reloading it causes the warning.
>
> Are you using bcache or bcachefs? I don't see bch_fs_init() in 4.7:
> http://lxr.free-electrons.com/ident?i=bch_fs_init
> < empty >
>
> If bcachefs, please update the subject when you reply.
$ grep -R bch_fs_init drivers/md/bcache/*.{c,h}
drivers/md/bcache/fs.c:int __init bch_fs_init(void)
drivers/md/bcache/super.c: bch_fs_init() ||
drivers/md/bcache/bcache.h:int bch_fs_init(void);
I'm little confused. Module name is "bcache" and I used it in subject
because I couldn't load such module. I think that this module supports
both bcache (cache device) and bcachefs. And yes, I'm using kernel tree
with bcachefs support:)
Marcin
prev parent reply other threads:[~2016-08-06 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 14:03 Can't load bcache module second time Marcin Mirosław
2016-08-05 19:47 ` Eric Wheeler
2016-08-06 12:20 ` marcin [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:
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=36b48a9e235db2188b5063ebe6d23e4a@mejor.pl \
--to=marcin@mejor.pl \
--cc=bcache@lists.ewheeler.net \
--cc=linux-bcache@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).