906e4af9 - docs: ABI: sysfs-uevent: make it compatible with ReST output

Fri, 30 Oct 2020 07:40:40 +0000

docs: ABI: sysfs-uevent: make it compatible with ReST output- Replace " by ``, in order to use monospaced fonts;- mark literal blocks as such.Acked-by: Jonathan Corbet Signed-off-by: Mauro Carvalho Chehab Link: https://lore.kernel.org/r/63904cc9b6a8581c5fc2ea1dca5d925874c67372.1604042072.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/Documentation/ABI/testing/sysfs-uevent

e622ec57 - doc: update kernel version in sysfs-uevent ABI doc

Sat, 27 May 2017 09:07:35 +0000

doc: update kernel version in sysfs-uevent ABI docWe expect the changes described in ABI/testing/sysfs-uevent doc to appear in 4.13.Signed-off-by: Peter Rajnoha Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/Documentation/ABI/testing/sysfs-uevent

f36776fa - kobject: support passing in variables for synthetic uevents

Tue, 09 May 2017 13:22:30 +0000

kobject: support passing in variables for synthetic ueventsThis patch makes it possible to pass additional arguments in additionto uevent action name when writing /sys/.../uevent attribute. Theseadditional arguments are then inserted into generated synthetic ueventas additional environment variables.Before, we were not able to pass any additional uevent environmentvariables for synthetic uevents. This made it hard to identify such ueventsproperly in userspace to make proper distinction between genuine ueventsoriginating from kernel and synthetic uevents triggered from userspace.Also, it was not possible to pass any additional information which wouldmake it possible to optimize and change the way the synthetic uevents areprocessed back in userspace based on the originating environment of thetriggering action in userspace. With the extra additional variables, we areable to pass through this extra information needed and also it makes itpossible to synchronize with such synthetic uevents as they can be clearlyidentified back in userspace.The format for writing the uevent attribute is following: ACTION [UUID [KEY=VALUE ...]There's no change in how "ACTION" is recognized - it stays the same("add", "change", "remove"). The "ACTION" is the only argument requiredto generate synthetic uevent, the rest of arguments, that this patchadds support for, are optional.The "UUID" is considered as transaction identifier so it's possible touse the same UUID value for one or more synthetic uevents in which casewe logically group these uevents together for any userspace listeners.The "UUID" is expected to be in "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"format where "x" is a hex digit. The value appears in uevent as"SYNTH_UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" environment variable.The "KEY=VALUE" pairs can contain alphanumeric characters only. It'spossible to define zero or more more pairs - each pair is then delimitedby a space character " ". Each pair appears in synthetic uevents as"SYNTH_ARG_KEY=VALUE" environment variable. That means the KEY name gains"SYNTH_ARG_" prefix to avoid possible collisions with existing variables.To pass the "KEY=VALUE" pairs, it's also required to pass in the "UUID"part for the synthetic uevent first.If "UUID" is not passed in, the generated synthetic uevent gains"SYNTH_UUID=0" environment variable automatically so it's possible toidentify this situation in userspace when reading generated uevent and sowe can still make a difference between genuine and synthetic uevents.Signed-off-by: Peter Rajnoha Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/Documentation/ABI/testing/sysfs-uevent

Changes in sysfs-uevent

906e4af9 - docs: ABI: sysfs-uevent: make it compatible with ReST output

e622ec57 - doc: update kernel version in sysfs-uevent ABI doc

f36776fa - kobject: support passing in variables for synthetic uevents