linux-kernel - Re: [PATCH v2] docs: gpio: prefer pread(2) for interrupt reading

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Mon, 10 Jun 2024 09:38:36 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: brgl@...ev.pl,
	Huichun Feng <foxhoundsk.tw@...il.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	corbet@....net,
	linus.walleij@...aro.org,
	linux-doc@...r.kernel.org,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	warthog618@...il.com
Subject: Re: [PATCH v2] docs: gpio: prefer pread(2) for interrupt reading

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Mon, 10 Jun 2024 01:37:28 +0800, Huichun Feng wrote:
> In legacy sysfs GPIO, when using poll(2) on the sysfs GPIO value for
> state change awaiting, a subsequent read(2) is required for consuming
> the event, which the doc recommends the use of lseek(2) or
> close-and-reopen to reset the file offset afterwards.
> 
> The recommendations however, require at least 2 syscalls to consume
> the event. Gladly, use of pread(2) require only 1 syscall for the
> consumption. Let's advertise this usage by prioritizing its placement.
> 
> [...]

Applied, thanks!

[1/1] docs: gpio: prefer pread(2) for interrupt reading
      commit: 7f1e45f4ae7671550e15354ef87194bccd99ecec

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>