From: Alasdair G Kergon <agk@redhat.com>
To: John Mesmon <jmesmon@gmail.com>, maximlevitsky@gmail.com
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm fails when /proc/devices contains "-1 smblk"
Date: Sat, 17 Mar 2012 16:12:20 +0000 [thread overview]
Message-ID: <20120317161220.GA12111@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4F645D81.3010002@redhat.com>
> Dne 16.3.2012 07:28, John Mesmon napsal(a):
> > Block devices:
> > -1 smblk
That's outside the range of valid major numbers and surely shouldn't be getting
exposed to userspace in /proc/devices.
static struct mtd_blktrans_ops sm_ftl_ops = {
.name = "smblk",
.major = -1,
Why's -1 being used?
Alasdair
next prev parent reply other threads:[~2012-03-17 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 6:28 [linux-lvm] lvm fails when /proc/devices contains "-1 smblk" John Mesmon
2012-03-17 9:46 ` Zdenek Kabelac
2012-03-17 16:12 ` Alasdair G Kergon [this message]
2012-03-17 17:31 ` Maxim Levitsky
2012-03-17 20:51 ` Zdenek Kabelac
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=20120317161220.GA12111@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=jmesmon@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=maximlevitsky@gmail.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).