lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 16 Sep 2013 10:33:31 +0000
From:	"Morales, Alejandra" <alejandra.morales@....de>
To:	Oliver Neukum <oliver@...kum.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Doubts on IO requests in USB subsystem

2013/9/9 Oliver Neukum <oliver@...kum.org>
>
> Your prime suspect is the detection of medium change which was
> moved into the kernel in 3.2 or so. It can be disabled by sysfs.
> Generally the notion that a certain task originates a read or write
> on a block device is iffy. Read-ahead and shared data structures
> make it impossible to accurately tell.
>
> USB storage devices are notorious for setting the removable bit
> even if they have no removable medium.
>

Thanks for the answer Oliver. Unfortunately it doesn't seem to be the
medium change detection what is causing these requests, since the
removable bit is disabled and the polling period is set to -1:

morales@...zerodesk:~$ udevadm info --query all --path /sys/block/sdc/ --attribute-walk

looking at device '/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.0/host11/target11:0:0/11:0:0:0/block/sdc':
    KERNEL=="sdc"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{range}=="16"
    ATTR{ext_range}=="256"
    ATTR{removable}=="0"
    ATTR{ro}=="0"
    ATTR{size}=="1953525168"
    ATTR{alignment_offset}=="0"
    ATTR{discard_alignment}=="0"
    ATTR{capability}=="50"
    ATTR{stat}=="   12805     1970   102691    23528   747334     2557  5999128  3340096        0  1963084  3362880"
    ATTR{inflight}=="       0        0"
    ATTR{events}==""
    ATTR{events_async}==""
    ATTR{events_poll_msecs}=="-1"


Regards
- Alejandra--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ