Greg, I'm pretty sure I know what's happening. For whatever reason we're invoking dev_attr_show() on attribute_group objects. The reason it probably only crashes on sparc64 is because perhaps at that dev_attr->show offset on x86 there are zero bytes there instead of a pointer, so the NULL check here in dev_attr_show() masks the bug. The problem with all of this "container_of() this", "container_of() that" is that we lose real type checking. So unless we add magic cookies to verify or other hacks, functions never really know if the container they are being passed really is a subset object of the type they expect. Can you read the code instead of asking more information from me to try and figure out why the attribute showing paths might be misconfigured for these block device objects after the changeset in question? I can do this, but you're more likely to find the problem quickly than I am. I redid the bisect to make sure it absolutely was that specific changeset, and it is. Thanks. --
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer | [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree |
| Alexander Sulfrian | [RFC/PATCH] RE: git calls SSH_ASKPASS even if DISPLAY is not set |
| Junio C Hamano | Re: Rss produced by git is not valid xml? |
| Linux Kernel Ma |
