Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1664291
| From | Khazhismel Kumykov <khazhy@google.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Hang/soft lockup in d_invalidate with simultaneous calls |
| Date | 2017-06-13 01:10 +0200 |
| Message-ID | <tRGD8-8H-5@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <tIf97-cH-7@gated-at.bofh.it> <tO5Tr-j9-3@gated-at.bofh.it> <tO9No-2S4-1@gated-at.bofh.it> <tOaJr-3sB-1@gated-at.bofh.it> <tOb2N-3zj-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Fri, Jun 2, 2017 at 11:47 PM, Khazhismel Kumykov <khazhy@google.com> wrote: > On Fri, Jun 2, 2017 at 11:20 PM, Al Viro <viro@zeniv.linux.org.uk> wrote: >> The thing is, unlike shrink_dcache_parent() we *can* bugger off as >> soon as we'd found no victims, nothing mounted and dentry itself >> is unhashed. We can't do anything in select_collect() (we would've >> broken shrink_dcache_parent() that way), but we can do unhashing >> in check_and_drop() in "really nothing to do" case and we can return >> from d_invalidate() after that. So how about this: > That does the trick. I'm not entirely familiar the process here, is the above change committed somewhere, should I propose a patch?
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Hang/soft lockup in d_invalidate with simultaneous calls Khazhismel Kumykov <khazhy@google.com> - 2017-06-13 01:10 +0200 Re: Hang/soft lockup in d_invalidate with simultaneous calls Al Viro <viro@ZenIV.linux.org.uk> - 2017-06-15 13:00 +0200
csiph-web