LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, kay.sievers@vrfy.org
Subject: Re: partition sysfs OOPS in current GIT
Date: Wed, 6 Feb 2008 15:59:02 -0800	[thread overview]
Message-ID: <20080206235902.GA15719@suse.de> (raw)
In-Reply-To: <20080206.153714.133821225.davem@davemloft.net>

On Wed, Feb 06, 2008 at 03:37:14PM -0800, David Miller wrote:
> From: Greg KH <gregkh@suse.de>
> Date: Wed, 6 Feb 2008 15:31:17 -0800
> 
> > On Wed, Feb 06, 2008 at 03:26:39PM -0800, David Miller wrote:
> > > I'm pretty sure the following changeset is to blame:
> > > 
> > > commit edfaa7c36574f1bf09c65ad602412db9da5f96bf
> > > Author: Kay Sievers <kay.sievers@vrfy.org>
> > > Date:   Mon May 21 22:08:01 2007 +0200
> > > 
> > >     Driver core: convert block from raw kobjects to core devices
> > >     
> > >     This moves the block devices to /sys/class/block. It will create a
> > >     flat list of all block devices, with the disks and partitions in one
> > >     directory. For compatibility /sys/block is created and contains symlinks
> > >     to the disks.
> > 
> > So I'm guessing if you revert this it works?
> 
> Unfortunately that's not so simple to test because afterwards there
> are changesets where all the files under block/ got renamed and as
> such I can't just revert that single patch from the tip.

Understood :(

but since you've bisected it down to this, that's a pretty big
suggestion that this is the problem.

What block drivers are you using for sparc?  Scsi?  Or something else?
What could make sparc64 different from x86 in regards to block device
structure, odd...

thanks,

greg k-h

  parent reply	other threads:[~2008-02-07  0:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 23:26 David Miller
2008-02-06 23:31 ` Greg KH
2008-02-06 23:37   ` David Miller
2008-02-06 23:48     ` David Miller
2008-02-06 23:59     ` Greg KH [this message]
2008-02-07  0:02       ` David Miller
2008-02-07  0:09         ` Greg KH
2008-02-07  0:29           ` David Miller
2008-02-07  4:06           ` David Miller
2008-02-07  5:47             ` Greg KH
2008-02-07  6:05               ` David Miller
2008-02-07  6:38                 ` Greg KH
2008-02-07  6:38                   ` David Miller
2008-02-07  6:42                 ` Greg KH
2008-02-07  6:39                   ` David Miller
2008-02-07  6:58                     ` Greg KH
2008-02-07  7:00                     ` Greg KH
2008-02-07  7:11                       ` David Miller
2008-02-07  7:18                         ` Greg KH
2008-02-07  7:33                           ` David Miller
2008-02-07  7:43                             ` Greg KH
2008-02-07  7:20                         ` Greg KH
2008-02-07  7:24                           ` David Miller
2008-02-07  7:42                             ` Greg KH
2008-02-07  6:44                 ` Greg KH
2008-02-07  6:42                   ` David Miller
2008-02-06 23:57   ` Andrew Morton
2008-02-07  0:07     ` Greg KH
2008-02-06 23:42 ` Oops figures Jan Engelhardt
2008-02-06 23:47   ` David Miller

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=20080206235902.GA15719@suse.de \
    --to=gregkh@suse.de \
    --cc=davem@davemloft.net \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: partition sysfs OOPS in current GIT' \
    /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

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).