The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Mike Black <mblack@csihq.com>, linux-kernel@vger.kernel.org
Subject: Re: Something broken in sys_swapon
Date: Sun, 4 Nov 2001 12:33:00 -0800	[thread overview]
Message-ID: <20011104123300.A665@netnation.com> (raw)
In-Reply-To: <00a901c16526$48c64300$1a502341@cfl.rr.com> <Pine.GSO.4.21.0111040702440.20848-100000@weyl.math.psu.edu> <20011104122248.A13561@netnation.com>
In-Reply-To: <20011104122248.A13561@netnation.com>

Aha!  I then tried this patch:

--- linux/fs/block_dev.c.orig	Sun Nov  4 11:35:05 2001
+++ linux/fs/block_dev.c	Sun Nov  4 12:21:51 2001
@@ -84,6 +84,15 @@
 	}
 
 	oldsize = blksize_size[MAJOR(dev)][MINOR(dev)];
+
+	printk("Changing device %02x:%02x block size from %u to %u\n",
+		MAJOR(dev),MINOR(dev),
+		oldsize,size);
+	if (MAJOR(dev) == 0x03 && MINOR(dev) == 0x42){
+		printk("...Refused.\n");
+		return 0;
+	}
+
 	if (oldsize == size)
 		return 0;
 
...And now my system boots fine with /dev/hdb2 swap in the fstab.

In fact, I tried /dev/hdb1 after and then I couldn't read any more from
/boot (which is /dev/hda1).  So, some sort of wraparound is happening
here.  Why would blksize_size[3][2] be affected by blksize_size[3][0x42]?

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]

      reply	other threads:[~2001-11-04 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-03 20:23 Something broken in sys_swapon Simon Kirby
2001-11-03 20:31 ` Alexander Viro
2001-11-03 21:13   ` Simon Kirby
2001-11-04 11:46     ` Mike Black
2001-11-04 12:05       ` Alexander Viro
2001-11-04 20:22         ` Simon Kirby
2001-11-04 20:33           ` Simon Kirby [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=20011104123300.A665@netnation.com \
    --to=sim@netnation.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mblack@csihq.com \
    --cc=viro@math.psu.edu \
    /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