Using read-only NULLFS leads to panic. gdb output included, e asy to reproduce.

[Helge Oldach]

Hi,

Tim Robbins:
>On Wed, Mar 03, 2004 at 12:09:30PM +0100, Pawel Malachowski wrote:
>
>> On Wed, Mar 03, 2004 at 11:25:36AM +1100, Tim Robbins wrote:
>> 
>> > There are known bugs in nullfs in all 4.x releases to date, and in 5.0.
>> > If I have time, I may MFC the fixes some time before 4.10 is released.
>> 
>> Sounds interesting.
>> 
>> > Can you reproduce these problems on 5.1 or 5.2?
>> 
>> Procedure:
>> mount_null -o ro /usr/ports /mnt/1
>> find /usr/ports -type f -perm -u+s &
>> find /mnt/1 -type f -perm -u+s &
>> ...
>> <about 30-40 processess of find(1) was enough>
>> 
>> 
>> I was not able to reproduce panic on 5.1-RELEASE system.
>> 
>> However, I've reproduced second problem described in this PR,
>> which happened to me on 4.9-STABLE once.
>[...]
>
>I'm sorry - the commit that fixed the deadlock issue you're describing
>here ocurred between 5.1 and 5.2, not between 5.0 and 5.1 like I
>had previously thought. Try 5.2, or try this patch on 5.1. If it solves
>your problem, I'll backport it to 4.x for you later this week.

Did I miss this MFC, or haven't you back-ported it yet?

Thanks!

Helge