<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - LO on Linux crashes when accessing opend/locked File on SAMBA network share" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127648#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - LO on Linux crashes when accessing opend/locked File on SAMBA network share" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127648">bug 127648</a> from <a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> Stephan Bergmann</a> <pre>(In reply to Jan from <a href="show_bug.cgi?id=127648#c19">comment #19</a>) > All right, so you mean it is a client side kernel bug of cifs kernel module ? > Or Server side bug samba4 / btrfs? Hard to tell. I would start by reporting it to the relevant client-side kernel part. (In reply to Mike Kaganski from <a href="show_bug.cgi?id=127648#c20">comment #20</a>) > Does that value reach LO code? In which case, it could be worth a workaround > checking if the reported read size is greater than asked size? I would only want to do that as a very last resort, in case the the assumed bug outside of LO can't be fixed for whatever reason. Why not wait for an analysis of the assumed kernel bug first? (Jan, I assume you pass this on as appropriate? In which case, thank you, and would be great if you could add a link here or report back any findings.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>