> -----Original Message-----
> From: Bart Van Assche [mailto:[email protected]]
> Sent: Friday, August 18, 2017 4:47 PM
> To: [email protected]; Viswas G <[email protected]>; Gerry
> Morong <[email protected]>; Mahesh Rajashekhara
> <[email protected]>; [email protected]; Scott
> Benesh <[email protected]>; Don Brace
> <[email protected]>; Bader Ali - Saleh
> <[email protected]>; Kevin Barnett
> <[email protected]>; [email protected]; Scott Teel
> <[email protected]>; [email protected]; Justin Lindley
> <[email protected]>; John Hall <[email protected]>
> Cc: [email protected]
> Subject: Re: [PATCH] sd: preserve sysfs updates to max_sectors_kb
> 
> EXTERNAL EMAIL
> 
> 
> On Fri, 2017-08-18 at 21:29 +0000, Don Brace wrote:
> > As far as I can see, udev looks for file access in sysfs.
> > I am not exactly sure which rule changes this. It was added in more recent
> > distros. Can someone help me out?
> 
> Hello Don,
> 
> Can you check on your test system which udev rule changes
> max_sectors_kb? I
> have checked two recent Linux distro's but haven't been able to find such a
> udev rule:
> $ grep -rw max_sectors_kb /usr/lib/udev/rules.d /etc/udev/rules.d | wc -l
> 0
> 
> Thanks,
> 
> Bart.

On my system it is 60-block.rules, and it is the last rule in that rule file.
--
# do not edit this file, it will be overwritten on update

# enable in-kernel media-presence polling
ACTION=="add", SUBSYSTEM=="module", KERNEL=="block", 
ATTR{parameters/events_dfl_poll_msecs}=="0", \
  ATTR{parameters/events_dfl_poll_msecs}="2000"

# forward scsi device event to corresponding block device
ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", 
TEST=="block", ATTR{block/*/uevent}="change"

# watch metadata changes, caused by tools closing the device node which was 
opened for writing
ACTION!="remove", SUBSYSTEM=="block", KERNEL=="loop*|nvme*|sd*|vd*|xvd*|pmem*", 
OPTIONS+="watch"

Reply via email to