服务端系统kernel panic

[WooDragon]

提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。
Please answer the following questions before submitting your issue. Thank you.

1. 你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）

2. What version of V2Ray are you using?
   2.11
   客户端kernel 4.9.0-rc3
   服务端kernel 3.18.27

3. 你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。

4. What your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
   客户端通过iptables将tcp请求通过v2ray安全转发至服务端，再递交给服务端的业务程序。

5. 你看到的不正常的现象是什么？

6. What did you see?
   在实际业务下运行时，服务端系统内核直接崩溃，panic截图看来和xfrm有关（AES加密崩了？）
   当前不能确定一定是v2ray的问题，因为无法稳定复现，用iperf跑压测似乎也没有问题。
   但是因为同时间段其他变更不太可能导致内核崩溃那么严重，所以贴出来希望你能帮助看一下是否有关……
   kernel panic 拍照如下
   

7. 你期待看到的正确表现是怎样的？

8. What do you expected to see instead?
   不崩溃

9. 请附上你的配置文件。

10. Please attach your configuration file.
    服务端

{
    "log": {
        "access": "/disk/ssd2/v2ray/access.log",
        "error": "/disk/ssd2/v2ray/error.log",
        "loglevel": "warning"
    },
    "inbound": {
        "port": 4066,
        "protocol": "vmess",
        "settings": {
            "clients": [
                {   
                    "id": "xxx",
                    "level": 1
                }
            ]
        }
    },
    "outbound": {
        "protocol": "freedom",
        "settings": {}
    }
}

客户端

{
    "log": {
        "access": "/disk/ssd1/v2ray/access.log",
        "error": "/disk/ssd1/v2ray/error.log",
        "loglevel": "warning"
    },
    "inbound": {
        "protocol": "dokodemo-door",
        "port": 5066,
        "settings": {
            "network": "tcp",
            "timeout": 0,
            "address": "",
            "followRedirect": true
        }
    },
    "outbound": {
        "protocol": "vmess",
        "settings": {
            "vnext": [
                {
                    "address": "192.168.229.69",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.70",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.71",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.72",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.73",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.74",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.75",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                },
                {
                    "address": "192.168.229.76",
                    "port": 4066,
                    "users": [
                        {
                            "id": "xxx",
                            "security": "aes-128-gcm"
                        }
                    ]
                }
            ]
        }
    }
}

[WooDragon]

补充一个，10台中有3台先后挂掉，都是这个错误

[v2ray]

能不能看到panic信息的第一行？八成是golang的问题或者系统问题，或者不兼容。 V

…

On Tue, Dec 27, 2016 at 6:25 AM WooDragon ***@***.***> wrote: 补充一个，10台中有3台先后挂掉，都是这个错误 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#342 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANdNvpwB2twrbYWEkXvf0roCGpRJ9Y0aks5rMKFHgaJpZM4LWBK_> .

[WooDragon]

panic的节点系统没有转储能力……所以看不到第一行……现在不敢再放上去跑了，我后边再找个风险低的地方试试看吧

[v2ray]

xfrm_selector_match 是一个网络相关的函数，和 AES 没关系。看了一下那个文件的历史也没发现明确的线索，只找到一个修复某个 crash 的 commit。

看文件的上下文貌似是 Linux 的 bug 而不是 Golang 的，不过不确定。

[WooDragon]

@v2ray 这个我想办法看看能否可以复现并且转储出来吧，

[v2ray]

先关了，有线索了再重开吧