On 2012-06-15 16:23 +0200, Jan Kara wrote: > On Fri 15-06-12 09:58:25, Nick Bowler wrote: > > On 2012-06-15 12:51 +0200, Jens Axboe wrote: > > > On 06/15/2012 12:50 PM, Jan Kara wrote: > > > > Sometimes, warnings about ioctls to partition happen often enough that they > > > > form majority of the warnings in the kernel log and users complain. In some > > > > cases warnings are about ioctls such as SG_IO so it's not good to get rid of > > > > the warnings completely as they can ease debugging of userspace problems > > > > when ioctl is refused. > > > > > > > > Since I have seen warnings from lots of commands, including some proprietary > > > > userspace applications, I don't think disallowing the ioctls for processes > > > > with CAP_SYS_RAWIO will happen in the near future if ever. So lets just > > > > stop warning for processes with CAP_SYS_RAWIO for which ioctl is allowed. > > > > > > Agree, merged, finally. > > > > Hurray! > > > > This should be -stable material as well, as >=3.2.y kernel versions are > > affected (I think 3.0.y is OK?). > 3.0 also spits those warnings. But I'm not convinced this is really a > -stable material. I don't see anybody loosing sleep over this... These messages are quite annoying on my raid boxes (currently running 3.2.y) where mdadm spews a whole pile of these whenever you do anything. Even with the rate limiting, they make up a substantial proportion of the total log messages. Cheers, -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
