[roll] Roll fuchsia [starnix] Failing to create a devtmps device should return a warning

Right now, add_device in the DeviceRegistry returns an error if
devtmpfs_create_device fails. However, given that android maintains its
own tmpfs to manage its devices, we should not log errors if creating
the device fails. In the case of dm-verity, we expect create_device to
fail because apexd will not have the CAP_MKNOD capability when it
creates the device (ueventd has the CAP_MKNOD capability instead).

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1044217
Original-Revision: 6f99263d059182c6ce28f644dac0c11fd6336c20
GitOrigin-RevId: 19dfff22a7ed9a4ae8660c4974ea6b3b71f5d4dd
Change-Id: I52344054c1a4ca167a5f2b23b7e8fdaaadf6e753
1 file changed
tree: d7e86b875404620d49ab769e20eb7b8e1660884f
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.