NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/54322: strange kdump output

>Number:         54322
>Category:       kern
>Synopsis:       strange kdump output
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 24 09:15:00 +0000 2019
>Originator:     Martin Husemann
>Release:        NetBSD 8.99.47
The NetBSD Foundation, Inc.
System: NetBSD 8.99.47 NetBSD 8.99.47 (GENERIC) #0: Fri Jun 21 16:57:12 UTC 2019 amd64
Architecture: x86_64
Machine: amd64

While ktracing a threaded application I noticed strange output in kdump:

  6851      1 gxemul   CALL  read(4,0x7d05e3f9e000,0x1000)
  6851      1 gxemul   GIO   fd 4 read 4088 bytes
[... data content stripped ...]
  6851      1 gxemul   GIO   fd 4 read 8 bytes
  6851      1 gxemul   RET   read 4096/0x1000

I expected a request of 0x1000 to just trigger the transfer of upto
4096/0x1000 bytes. Why is GIO accounting for additional stuff?

Not sure, seems to be reproducable for me.


Home | Main Index | Thread Index | Old Index