Explicitly say which file cannot be open when failing to open a backing file
ClosedPublic
Actions

Authored by bapt on May 26 2016, 11:37 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Sat, Oct 18, 11:36 AM

	Unknown Object (File)
	Sep 23 2025, 12:54 PM

	Unknown Object (File)
	Sep 22 2025, 6:03 PM

	Unknown Object (File)
	Sep 22 2025, 1:52 PM

	Unknown Object (File)
	Sep 22 2025, 9:01 AM

	Unknown Object (File)
	Sep 22 2025, 3:33 AM

	Unknown Object (File)
	Sep 21 2025, 9:36 AM

	Unknown Object (File)
	Sep 21 2025, 3:53 AM

View All 100 Files

Subscribers

imp

Details

Reviewers

grehan

Commits

rS300843: Improve error message when failing to open a backing file

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

bapt updated this revision to Diff 16902.May 26 2016, 11:37 AM

bapt retitled this revision from to Explicitly say which file cannot be open when failing to open a backing file.

bapt updated this object.

bapt edited the test plan for this revision. (Show Details)

bapt added a reviewer: grehan.

Herald added a subscriber: imp. · View Herald TranscriptMay 26 2016, 11:37 AM

Looks fine. This also closes PR 202321

The error message in pci_virtio_blk may not be needed since it's going to be printed in the blockif call.

This revision is now accepted and ready to land.May 26 2016, 1:52 PM

Closed by commit rS300843: Improve error message when failing to open a backing file (authored by bapt). · Explain WhyMay 27 2016, 11:47 AM

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

head/

usr.sbin/

bhyve/

block_if.c

5 lines

Diff 16989

View Options

head/usr.sbin/bhyve/block_if.c

Explicitly say which file cannot be open when failing to open a backing fileClosedPublicActions