From: Paolo Bonzini <pbonzini@redhat.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
James Bottomley <JBottomley@parallels.com>,
mmarek@suse.cz
Subject: Re: Ioctl warning for a partition
Date: Sat, 28 Jan 2012 11:22:11 +0100 [thread overview]
Message-ID: <4F23CC53.4040304@redhat.com> (raw)
In-Reply-To: <20120127192817.GB25348@khazad-dum.debian.net>
On 01/27/2012 08:28 PM, Henrique de Moraes Holschuh wrote:
> Does that fix still need to be backported to -stable?
>
> Linux v3.0.18 + Debian stable userspace (mdadm v3.1.4) causes this on
> boot (when mdadm runs in the initramfs):
>
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 1261 to a partition!
> mdadm: sending ioctl 800c0910 to a partition!
> mdadm: sending ioctl 800c0910 to a partition!
The warnings are intended; the kernel will behave as before they were
introduced. I'm monitoring reports and looking at them as they come in.
They are harmless as long as the ioctls have always failed, and so far
this has always been the case. As soon as we are reasonably certain,
the warnings will go away.
Paolo
next prev parent reply other threads:[~2012-01-28 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 22:30 Ioctl warning for a partition Jan Kara
2012-01-26 23:01 ` Linus Torvalds
2012-01-26 23:56 ` Michael Tokarev
2012-01-27 19:28 ` Henrique de Moraes Holschuh
2012-01-27 19:37 ` Henrique de Moraes Holschuh
2012-01-28 10:22 ` Paolo Bonzini [this message]
2012-01-28 14:41 ` Henrique de Moraes Holschuh
2012-01-27 8:35 ` Paolo Bonzini
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=4F23CC53.4040304@redhat.com \
--to=pbonzini@redhat.com \
--cc=JBottomley@parallels.com \
--cc=axboe@kernel.dk \
--cc=hmh@hmh.eng.br \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mmarek@suse.cz \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).