From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH dlm-next 0/2] fs: dlm: dlm lock from user space fixes
Date: Fri, 11 Dec 2020 10:47:16 -0500 [thread overview]
Message-ID: <20201211154718.99346-1-aahringo@redhat.com> (raw)
Hi,
found some issues with the user space fixes and that we don't have
proper aligned dlm messages. I found these issues while having my
pending patches applied which introduced a "hart" assert for this and
dropping messages on such case. With this assert dlm will probably not
backwards compatible anymore...
so here my question/suggestion:
We should queue these patches to stable?
- Alex
btw: these patches can be applied, I will send PATCHv3 for my pending
patches, I added two other patches.
Alexander Aring (2):
fs: dlm: check for invalid namelen
fs: dlm: transparently align name buffer
fs/dlm/user.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-12-11 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 15:47 Alexander Aring [this message]
2020-12-11 15:47 ` [Cluster-devel] [PATCH dlm-next 1/2] fs: dlm: check for invalid namelen Alexander Aring
2020-12-11 15:47 ` [Cluster-devel] [PATCH dlm-next 2/2] fs: dlm: transparently align name buffer Alexander Aring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201211154718.99346-1-aahringo@redhat.com \
--to=aahringo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).