summaryrefslogtreecommitdiff
path: root/include/net/irda/crc.h
diff options
context:
space:
mode:
authorPing-Ke Shih <pkshih@realtek.com>2017-02-06 21:30:00 -0600
committerKalle Valo <kvalo@codeaurora.org>2017-02-07 09:25:08 +0200
commit6f85c03bc34ce7040f0b56eca963be4969b719de (patch)
treea54a5eb43e66796e40c630b5541146ebdecdcfd1 /include/net/irda/crc.h
parent8d0d43e342083c9d2b15542e9a99727c0ef43a7f (diff)
rtlwifi: Add a new enumeration value to btc_set_type
The new value is needed for future capability. Signed-off-by: Ping-Ke Shih <pkshih@realtek.com> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'include/net/irda/crc.h')
0 files changed, 0 insertions, 0 deletions
XT4-fs (dm-1): Delayed block allocation failed for inode 2625094 at logical offset 2032 with max blocks 2 with error 121 EXT4-fs (dm-1): This should not happen!! Data will be lost 121 == EREMOTEIO is what scsi_io_completion() asserts in case of invalid opcodes. Back to the original problem of userspace segfaults: this can be tracked down to ata_format_sct_write_same() overwriting the input page. Sometimes, this page is ZERO_PAGE(0) which ceases to be filled with zeros from that point on. Since ZERO_PAGE(0) is used for userspace .bss mappings, code of the following is doomed: static char *a = NULL; /* .bss */ ... if (a) *a = 'a'; This problem is not solved by disabling SCT Write Same for !ZAC devices only. It can certainly be fixed, but the final release is quite close -- so disable SCT Write Same for all ATA devices rather than introducing some SCT key buffer allocation schemes at this point. Fixes: 7b2030942859 ("libata: Add support for SCT Write Same") Signed-off-by: Nicolai Stange <nicstange@gmail.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'net/9p')