Incident report on memory leak caused by Cloudflare parser bug
Incident report on memory leak caused by Cloudflare parser bug2017-02-23 Last Friday, Tavis Ormandy from Google’s Project Zero contacted Cloudflare to report a security problem with our edge servers. He was seeing corrupted web pages being returned by some HTTP requests run through Cloudflare. It turned out that in some unusual circumstances, which I’ll detail below, our edge servers were running
ã„ã¾ã•ã‚‰èžã‘ãªã„Linuxã¨ãƒ¡ãƒ¢ãƒªã®åŸºç¤Žï¼†vmstatã®è©³ã—ã„使ã„æ–¹ - Qiita
ã•ãらインターãƒãƒƒãƒˆ Advent Calendar最終日ã¯ã€ç¡¬æ´¾ã«Linuxã®ãƒ¡ãƒ¢ãƒªã«é–¢ã™ã‚‹åŸºç¤ŽçŸ¥è˜ã«ã¤ã„ã¦ã¿ã¦ã¿ãŸã„ã¨æ€ã„ã¾ã™ã€‚ 最近ã¯ã‚µãƒ¼ãƒãƒ¼ã‚’æ„è˜ã›ãšãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°ã§ãるよã†ã«ãªã‚Šã€ãƒ¡ãƒ¢ãƒªã®ç©ºã容é‡ã«ã¤ã„ã¦æ„è˜ã™ã‚‹ã“ã¨ã‚‚å°‘ãªããªã‚Šã¾ã—ãŸãŒã€ã„ã–低レイヤーã«è§¦ã‚Œãªã‘ã‚Œã°ã„ã‘ãªã„ã‚·ãƒãƒ¥ã‚¨ãƒ¼ã‚·ãƒ§ãƒ³ã«ãªã£ãŸéš›ã«ã€OSã‚’ç›®ã®å‰ã«å‘†ç„¶ã¨ã™ã‚‹äººãŒå¤šã„よã†ã§ã™ã€‚ 基本的ã«Linux ã®ãƒ‘フォーマンスã«ã¤ã„ã¦ã€ãƒ¡ãƒ¢ãƒªã‚’ãŸãã•ã‚“ã¤ã‚ã°ã„ã„ã¨ã‹ã€ã‚¹ãƒ¯ãƒƒãƒ—ã•ã›ãªã„ã»ã†ãŒè‰¯ã„ ã¨ã‹ã€ã“ã®ã‚ãŸã‚Šã¯è‰¯ã知られãŸã“ã¨ã ã¨æ€ã„ã¾ã™ã€‚ ãŸã ã€ãªã‚“ã¨ãªã ps コマンドや free コマンド ãªã©ã®çµæžœã‚’見るã ã‘ã§ãªãã€ã‚‚ã†å°‘ã—メモリã®ã“ã¨ã«ã¤ã„ã¦æŽ˜ã‚Šä¸‹ã’ã¦ã¿ã¦ã¿ãŸã„ã¨æ€ã„ã¾ã™ã€‚ メモリã¨ã‚ャッシュ Linux ã«ãŠã‘るメモリã®çŠ¶æ…‹ã‚’大ãã分ã‘ã‚‹ã¨ã€Œä½¿ç”¨ä¸ã®ãƒ¡ãƒ¢ãƒªã€ã€Œã‚ャッシュã€ã€Œç©ºãメモリã€ã€Œã‚¹ãƒ¯ãƒƒãƒ—ã€ã® 4 ã¤ã«åˆ†
Docker, Cgroups, Memory Constraints, and Java: A Cautionary Tale, or Here be Reapers (sometimes)
Docker, Cgroups, Memory Constraints, and Java: A Cautionary Tale, or Here be Reapers (sometimes) TL;DR: Java and cgroups/Docker memory constraints don’t always behave as you might expect. Always explicitly specify JVM heap sizes. Also be aware that kernel features may not be enabled. And Linux… lies. I’ve recently discovered an interesting “quirk†in potential interactions between Java, cgroups, D
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}