summaryrefslogtreecommitdiff
path: root/.gitignore
blob: 117ec38fd7af9940499bd3fa72e89228fd022341 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# Editor crap (emacs, vim, ...)
*.swp
*.orig
\#*\#
.\#*
.*.sw[a-z]
*.un~

# Hidden files, general things
.*
*~

# Compiled object files
*.slo
*.lo
*.o

# Compiled dynamic libraries
*.so

# Compiled static libraries
*.lai
*.la
*.a

# Testing folders
fuzzing/

# Ignore if someone adapts Makefile
Makefile

# Other documentation ignores
*.md
*.ps

# Compressed archives
*.tar.bz2
*.tar.bz
*.tar.xz

# Release related stuff
.MAIL_MSG

# Excluded from ignorance
!.gitignore
ket-loop-back&id=a621bac3044ed6f7ec5fa0326491b2d4838bfa93&id2=97f00905ec98472050d65c46629237b299f29035'>diff)
scsi_lib: correctly retry failed zero length REQ_TYPE_FS commands
When SCSI was written, all commands coming from the filesystem (REQ_TYPE_FS commands) had data. This meant that our signal for needing to complete the command was the number of bytes completed being equal to the number of bytes in the request. Unfortunately, with the advent of flush barriers, we can now get zero length REQ_TYPE_FS commands, which confuse this logic because they satisfy the condition every time. This means they never get retried even for retryable conditions, like UNIT ATTENTION because we complete them early assuming they're done. Fix this by special casing the early completion condition to recognise zero length commands with errors and let them drop through to the retry code. Cc: stable@vger.kernel.org Reported-by: Sebastian Parschauer <s.parschauer@gmx.de> Signed-off-by: James E.J. Bottomley <jejb@linux.vnet.ibm.com> Tested-by: Jack Wang <jinpu.wang@profitbricks.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat