From: Roberto Sassu via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
Cc: ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] ocfs2 xattr
Date: Tue, 07 Mar 2023 08:59:15 +0100 [thread overview]
Message-ID: <e848f2fbff1677023128afe4351e5af28576c058.camel@huaweicloud.com> (raw)
In-Reply-To: <ZAZtYjHlhM6IAVpc@valentin-vidic.from.hr>
On Mon, 2023-03-06 at 23:46 +0100, Valentin Vidić wrote:
> On Mon, Mar 06, 2023 at 10:40:35PM +0100, Valentin Vidić wrote:
> > I suppose the fix would be to change the default value to -EOPNOTSUPP?
>
> Confirmed, new default value fixes the crash. It is essentialy the same
> problem as this one in ceph:
>
> https://github.com/torvalds/linux/commit/7f5056b9e7b71149bf11073f00a57fa1ac2921a9
>
> I'll try to prepare a patch...
Ok, yes. It is a known problem. I tried to fix it several times, but no
luck yet.
https://lore.kernel.org/bpf/20221115175652.3836811-1-roberto.sassu@huaweicloud.com/
https://lore.kernel.org/bpf/20221207172434.435893-1-roberto.sassu@huaweicloud.com/
If you change the default value to -EOPNOTSUPP, that would address the
problem if no eBPF program attaches to the inode_init_security hook. If
one does and returns zero or any positive value, the kernel cannot
handle it.
Roberto
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
prev parent reply other threads:[~2023-03-07 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZASjOpsoM+nEx/o8@valentin-vidic.from.hr>
2023-03-06 9:13 ` [Ocfs2-devel] ocfs2 xattr Roberto Sassu via Ocfs2-devel
2023-03-06 10:45 ` Valentin Vidić via Ocfs2-devel
2023-03-06 16:58 ` Roberto Sassu via Ocfs2-devel
2023-03-06 21:40 ` Valentin Vidić via Ocfs2-devel
2023-03-06 22:46 ` Valentin Vidić via Ocfs2-devel
2023-03-07 7:59 ` Roberto Sassu via Ocfs2-devel [this message]
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=e848f2fbff1677023128afe4351e5af28576c058.camel@huaweicloud.com \
--to=ocfs2-devel@oss.oracle.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=vvidic@valentin-vidic.from.hr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).