« たこ焼き機新調～ | メイン | Muninのnetstatグラフがうまくでないで格闘してみたり・・・ »
2007年5月26日
Linux Kernel 2.6.21.2, 2.6.21.3がきた >>Linux
Linux Kernel 2.6.21.2, 2.6.21.3がきています。
気になるものいくつか。
[PATCH] x86_64 : Fix vgettimeofday()
vgettimeofday() may return some bad timeval values, (tv_usec = 1000000), because of a wrong compare.
以前にパッチがあったような気がするけども・・・
[PATCH] md: Avoid a possibility that a read error can wrongly propagate through md/raid1 to a filesystem.
When a raid1 has only one working drive, we want read error to propagate up to the filesystem as there is no point failing the last drive in an array.
Currently the code perform this check is racy. If a write and a read a both submitted to a device on a 2-drive raid1, and the write fails followed by the read failing, the read will see that there is only one working drive and will pass the failure up, even though the one working drive is actually the *other* one.
So, tighten up the locking.
[PATCH] TCP: zero out rx_opt in tcp_disconnect()
When the server drops its connection, NFS client reconnects using the same socket after disconnecting. If the new connection's SYN,ACK doesn't contain the TCP timestamp option and the old connection's did,
tp->tcp_header_len is recomputed assuming no timestamp header but
tp->rx_opt.tstamp_ok remains set.
Then tcp_build_and_update_options() adds in a timestamp option past the end of the allocated TCP header,
overwriting TCP data, or when the data is in skb_shinfo(skb)->frags[],
overwriting skb_shinfo(skb) causing a crash soon after.
(The issue was debugged from such a crash.)
Similarly, wscale_ok and sack_ok also get set based on the SYN,ACK packet but not reset on disconnect, since they are zeroed out at initialization. The patch zeroes out the entire tp->rx_opt struct in tcp_disconnect() to avoid this sort of problem.
この記事をTwitterでみんなに教える。トラックバック
現在、この記事はトラックバックを受け付けておりません。
コメント
現在、この記事はコメントを受け付けておりません。