Skip to content
Snippets Groups Projects
Select Git revision
  • 428edade4e6c70e5b51fcd4188d944fbb744d84c
  • openEuler-1.0-LTS default protected
  • openEuler-22.09
  • OLK-5.10
  • openEuler-22.03-LTS
  • openEuler-22.03-LTS-Ascend
  • master
  • openEuler-22.03-LTS-LoongArch-NW
  • openEuler-22.09-HCK
  • openEuler-20.03-LTS-SP3
  • openEuler-21.09
  • openEuler-21.03
  • openEuler-20.09
  • 4.19.90-2210.5.0
  • 5.10.0-123.0.0
  • 5.10.0-60.63.0
  • 5.10.0-60.62.0
  • 4.19.90-2210.4.0
  • 5.10.0-121.0.0
  • 5.10.0-60.61.0
  • 4.19.90-2210.3.0
  • 5.10.0-60.60.0
  • 5.10.0-120.0.0
  • 5.10.0-60.59.0
  • 5.10.0-119.0.0
  • 4.19.90-2210.2.0
  • 4.19.90-2210.1.0
  • 5.10.0-118.0.0
  • 5.10.0-106.19.0
  • 5.10.0-60.58.0
  • 4.19.90-2209.6.0
  • 5.10.0-106.18.0
  • 5.10.0-106.17.0
33 results

22b970497

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    David Howells authored
    The handling of CB.CallBack messages sent by the fileserver to the client
    is broken in that they are currently being processed after the reply has
    been transmitted.
    
    This is not what the fileserver expects, however.  It holds up change
    visibility until the reply comes so as to maintain cache coherency, and so
    expects the client to have to refetch the state on the affected files.
    
    Fix CB.CallBack handling to perform the callback break before sending the
    reply.
    
    The fileserver is free to hold up status fetches issued by other threads on
    the same client that occur in reponse to the callback until any pending
    changes have been committed.
    
    Fixes: d001648e ("rxrpc: Don't expose skbs to in-kernel users [ver #2]")
    Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
    428edade
    History
    Name Last commit Last update