public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Mike Black <mblack@csihq.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Recommended change
Date: Fri, 17 Aug 2001 04:42:56 -0600	[thread overview]
Message-ID: <20010817044256.E32617@turbolinux.com> (raw)
In-Reply-To: <001f01c12702$f5fd98a0$e1de11cc@csihq.com>
In-Reply-To: <001f01c12702$f5fd98a0$e1de11cc@csihq.com>

On Aug 17, 2001  05:57 -0400, Mike Black wrote:
> I upgraded to e2fsprog-1.23 and LInux 2.4.8 yesterday and saw this:
> 
> Aug 16 08:58:20 yeti kernel: md: fsck.ext3(pid 207) used obsolete MD ioctl,
> upgrade your software to use new ictls.
> 
> Do you suppose we could change the printk line to actually output the ioctl
> that was requested?
> 
> i.e.:
> 
> /usr/src/linux/drivers/md/md.c
> 
>                 default:
>                         printk(KERN_WARNING "md: %s(pid %d) used obsolete MD
> ioctl(%d), upgrade your software to use new ictls.\n", current->comm,
> current->pid, cmd);

Some notes:
1) It should probably print the ioctl as 0x%X, because this makes it a lot
   easier to decode which ioctl it is.

2) The ioctl in question is actually BLKGETSIZE64, which is part of Jens'
   64-bit block device patch, but is not part of the stock kernel.  It
   was added to e2fsprogs in order to support devices > 2TB.

3) Drivers probably shouldn't complain about ioctls they don't understand,
   as it just causes a lot of grief (see this thread here).  If anything,
   they _could_ complain about specific obsolete ioctl numbers, or maybe
   ioctl numbers in their "allocated" namespace (0x09 for MD it appears).
   Even so, this "breaks" forward compatibility, if tools try to use a
   new ioctl on an older kernel before falling back to the old ioctl, you
   get a lot of spurious warnings.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


      reply	other threads:[~2001-08-17 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  9:57 Recommended change Mike Black
2001-08-17 10:42 ` Andreas Dilger [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=20010817044256.E32617@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mblack@csihq.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