public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre5-ac2:  kernel oops with "swapoff -a"
Date: Sat, 08 Mar 2003 18:51:27 +0000	[thread overview]
Message-ID: <3E6A3BAF.7020708@myrealbox.com> (raw)
In-Reply-To: <fa.fk1qpc0.s4022c@ifi.uio.no>

walt wrote:
> Alan Cox wrote:
> 
>> On Sat, 2003-03-08 at 11:07, walt wrote:
>>
>>> When I do "swapoff -a" I still see the kernel oops that began with 
>>> -pre4-ac7
>>> and has propagated to every 'ac' kernel since then.
> 
> 
>> Can you send me an strace swapoff -a ?


> swapoff("/dev/hda10")                   = -1 EINVAL (Invalid argument)
> read(3, "", 4096)                       = 0
> _exit(0)                                = ?


On further investigation I find that "swapoff <anyPartition>" will produce
the same oops and segfault in /sbin/swapoff, whereas if I supply a totally
bogus argument like 'swapoff xyz' I get an appropriate error message
instead of the oops:

swapoff("xyz")                          = -1 ENOENT (No such file or directory)
write(2, "swapoff: xyz: No such file or di"..., 40swapoff: xyz: No such file or 
directory
) = 40
_exit(-1)                               = ?



       reply	other threads:[~2003-03-09  2:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.hhhab3c.11n83hg@ifi.uio.no>
     [not found] ` <fa.fk1qpc0.s4022c@ifi.uio.no>
2003-03-08 18:51   ` walt [this message]
     [not found] <fa.ft2aqc1.154k31h@ifi.uio.no>
     [not found] ` <fa.ohdbn4e.1rgcs92@ifi.uio.no>
2003-03-08 16:52   ` 2.4.21-pre5-ac2: kernel oops with "swapoff -a" walt
2003-03-08 11:07 walt
2003-03-08 22:40 ` Alan Cox
2003-03-08 21:42   ` John Bradford

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=3E6A3BAF.7020708@myrealbox.com \
    --to=wa1ter@myrealbox.com \
    --cc=linux-kernel@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