mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Holger.Smolinski@de.ibm.com
To: Guest section DW <dwguest@win.tue.nl>,
	aeb@cwi.nl, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [PATCH] partitions/ibm.c
Date: Mon, 26 Feb 2001 11:15:56 +0100	[thread overview]
Message-ID: <C12569FF.003D0F79.00@d12mta07.de.ibm.com> (raw)



Andries, others,
Thanks for hacking through the code of fs/partitions/ibm.c.
Your patch does not work at all because you are relying on the
data in the part component of the hd structure, which does not
hold the geometry data of the disk but the data of the partitions
on that disk. Besides that, exactly these data are to be set up
by the code in fs/partitions/ibm.c.
The geometry data is stored in the device driver. As in oposition
to the partition schemes the device drivercan be a loadable
module, fs/partitions.c should not at all directly call or use symbols
from the device driver.
My preferred solution would be having partition schemes as
loadable modules, too. Maybe I'll find some time to post the
approriate patch on this list soon...

Regards,
     Holger Smolinski

IBM Germany
Linux/390 Kernel Development
Schönaicher Str.220, D-71032 Böblingen

>Reading patch-2.4.2 I met a strange amount of crap in
>partitions/ibm.c. It is as if the author does not know
>where the kernel keeps the starting offset of a partition,
>and simulates a HDIO_GETGEO ioctl from user space.
>I think the following patch does the same and removes a lot
>of cruft. (Warning: (i) untested, uncompiled; (ii) pasted
>from another window - tabs will have become spaces.)

>Andries



             reply	other threads:[~2001-02-26 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 10:15 Holger.Smolinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-27  0:51 Andries.Brouwer
2001-02-26 15:11 Holger.Smolinski
2001-02-26 13:05 Andries.Brouwer
2001-02-24  3:38 Guest section DW

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=C12569FF.003D0F79.00@d12mta07.de.ibm.com \
    --to=holger.smolinski@de.ibm.com \
    --cc=aeb@cwi.nl \
    --cc=dwguest@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®