Re: possible deadlock in ovl_llseek 27c1936af506

From: Hillf Danton
Date: Tue Mar 12 2024 - 06:55:31 EST

Next message: Andi Shyti: "Re: linux-next: Signed-off-by missing for commit in the i2c-host tree"
Previous message: Krzysztof Kozlowski: "Re: [PATCH v3 1/2] dt-bindings: pinctrl: qcom: update compatible name for match with driver"
In reply to: Weiß, Simone: "possible deadlock in ovl_llseek 27c1936af506"
Next in thread: Amir Goldstein: "Re: possible deadlock in ovl_llseek 27c1936af506"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 12 Mar 2024 07:10:27 +0000 Weiß, Simone <Simone.Weiss@xxxxxxxxxxxxxx>
>
> For some experimentation, I have been running fuzzing campaigns and I
> noticed a possible deadlock in ovl_llseek .

Feel free to take a look at another case of deadlock [1]

[1] https://lore.kernel.org/lkml/ZPOtwcMHN_fpdrpt@boqun-archlinux/

Next message: Andi Shyti: "Re: linux-next: Signed-off-by missing for commit in the i2c-host tree"
Previous message: Krzysztof Kozlowski: "Re: [PATCH v3 1/2] dt-bindings: pinctrl: qcom: update compatible name for match with driver"
In reply to: Weiß, Simone: "possible deadlock in ovl_llseek 27c1936af506"
Next in thread: Amir Goldstein: "Re: possible deadlock in ovl_llseek 27c1936af506"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]