linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Chris Webb <chris@arachsys.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] sysfs superblock read oops
Date: Thu, 26 Jun 2008 09:45:16 +1000	[thread overview]
Message-ID: <18530.55436.577183.364504@notabene.brown> (raw)
In-Reply-To: message from Chris Webb on Wednesday June 25

On Wednesday June 25, chris@arachsys.com wrote:
> Whilst correcting my rdev resize patch to deal with non-persistent metadata,
> I noticed that reading from /sys/block/mdX/md/rdY/super when there isn't a
> real superblock causes an oops rather than just returning zero length. The
> tiny attached patch fixes this.

You must be using a slightly old kernel.  The 'super' sysfs file was removed
on 19th March 2008 and is gone since 2.6.25-rc7.

commit 0e82989d95cc46cc58622381eafa54f7428ee679

Thanks,
NeilBrown


      reply	other threads:[~2008-06-25 23:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 23:35 [PATCH] sysfs superblock read oops Chris Webb
2008-06-25 23:45 ` Neil Brown [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=18530.55436.577183.364504@notabene.brown \
    --to=neilb@suse.de \
    --cc=chris@arachsys.com \
    --cc=linux-raid@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).