fs: dlm: node address configuration fixes
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 0 repliesNew
- v13 patches 0 repliesSuperseded
changes since v2 from the cover letter
- remove deadlock situation in 3/3
- fix grammar in 1/3 commit msg
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | fs: dlm: cleanup dlm_local_addr properlyfs/ | +3 | 0 replies | |
| 2/3 | fs: dlm: constify addr_comparefs/ | +2 | 0 replies | |
| 3/3 | fs: dlm: check on existing node addressfs/ | +23 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [Cluster-devel] [PATCHv2 dlm/next 0/3] fs: dlm: node address configuration fixes
Hi,
I got reports of:
kernel: dlm: TCP protocol can't handle multi-homed hosts, try SCTP
there was some reconfiguration involed and my guess it that we left some dlm_local_addr array pointers in some dangled state. The first patch should fix the observed behaviour. The other patches is something what I thought can also happen, it just checks if we setup a node address twice, if this is the case we return -EEXIST.
This is based on dlm/next with the previous submitted patch series.
- Alex
changes since v2:
- remove deadlock situation in 3/3
- fix grammar in 1/3 commit msg
Alexander Aring (3):
fs: dlm: cleanup dlm_local_addr properly
fs: dlm: constify addr_compare
fs: dlm: check on existing node address
fs/dlm/lowcomms.c | 30 ++++++++++++++++++++++++++++-- 1 file changed, 28 insertions(+), 2 deletions(-)
Signature · 1 line
2.26.2