On Sat, Apr 06, 2013 at 12:04:52PM +0200, Marco Stornelli wrote: > In every place where sb_start_write was called now we must manage > the error code and return -EINTR. Now go and look for callers of mnt_want_write() ;-/ The really painful one is in do_last(), but kern_path_create() is not much better; mq_open() would be bad too, had it not been about something you are not going to freeze anyway... |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write is called, Marco Stornelli |
|---|---|
| Next by Date: | Hello., M . S |
| Previous by Thread: | Re: [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write is called, Marco Stornelli |
| Next by Thread: | Hello., M . S |
| Indexes: | [Date] [Thread] [Top] [All Lists] |