Project

General

Profile

Actions
Copy link

Bug #8270

closed

dnlc_reverse_lookup() is unsafe at any speed

Added by Patrick Mooney about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Patrick Mooney
Category:
kernel
Start date:
2017-05-24
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

Doing a reverse "lookup" in the DNLC (in air quotes because it's a scan, not a lookup) is unsafe at any speed – there shouldn't be an interface to do it, and consumers of it should simply assume that dnlc_reverse_lookup() returns nothing. Doing this resolves acute performance issues that we've seen in production in getcwd(), reading LX pmaps and other domains.

(Upstreaming https://smartos.org/bugview/OS-3975)

Actions
Copy link

Also available in: Atom PDF