Messages in this thread | | | Date | Wed, 30 Jan 2013 19:08:03 +0800 | Subject | Re: [PATCH 1/4] firmware: Refactoring for splitting user-mode helper code | From | Ming Lei <> |
| |
On Wed, Jan 30, 2013 at 6:53 PM, Takashi Iwai <tiwai@suse.de> wrote: > At Wed, 30 Jan 2013 18:50:05 +0800, > Ming Lei wrote: >> >> On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai <tiwai@suse.de> wrote: >> > >> > But it's supposed to be cached, no? >> >> Generally it will be cached, but some crazy devices might come as new >> device during resume, so we still need to handle the situation. > > In that case, shouldn't we simply return an error instead of > usermodehelper lock (at least for direct loading)?
The check depends on usermodehelper_read_trylock now, is there other simpler way to do the check?
Thanks, -- Ming Lei
| |