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. If we must manage the error code, then these functions should be marked __must_check. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write is called, Marco Stornelli |
|---|---|
| Next by Date: | Re: [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write is called, Marco Stornelli |
| Previous by Thread: | [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write is called, Marco Stornelli |
| Next by Thread: | Re: [PATCH 2/4] fsfreeze: manage kill signal when sb_start_write is called, Marco Stornelli |
| Indexes: | [Date] [Thread] [Top] [All Lists] |