All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: "Richard Weinberger" <richard.weinberger@gmail.com>,
	"Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
Cc: <snijsure@grid-net.com>, Artem Bityutskiy <dedekind1@gmail.com>,
	<ben.shelton@ni.com>, <terry.wilcox@ni.com>, <mkl@pengutronix.de>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	<gratian.crisan@ni.com>, <brad.mouring@ni.com>
Subject: Re: [kernel.org bug 103071] Dead "security.*" xattr code in ubifs
Date: Thu, 20 Aug 2015 08:50:59 +0800	[thread overview]
Message-ID: <55D52473.7050209@cn.fujitsu.com> (raw)
In-Reply-To: <CAFLxGvxPGZoRX3Ft_g59fzfLhoOmEES=q-oPBmYuGVBzn-dRUA@mail.gmail.com>

On 08/19/2015 04:55 AM, Richard Weinberger wrote:
> Andreas,
>
> On Tue, Aug 18, 2015 at 2:15 PM, Andreas Grünbacher
> <andreas.gruenbacher@gmail.com> wrote:
>> Hello,
>>
>> FYI, I've filed the following bug report against ubifs:
>>
>>> ubifs sets sb->s_xattr to ubifs_xattr_handlers which contains a handler for
>>> "security.*" xattrs. The s_xattr handlers are never used because ubifs uses
>>> its own ubifs_{get,set,list,remove}xattr inode operations instead of
>>> generic_{get,set,list,remove}xattr inode operations though.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=103071
>
> Thanks for reporting.
>
> CC'ing authors of commit d7f0b70d30ffb9bbe6b8a3e1035cf0b79965ef53
> Author: Subodh Nijsure <snijsure@grid-net.com>
> Date:   Fri Oct 31 13:50:30 2014 -0500
>
>      UBIFS: Add security.* XATTR support for the UBIFS
>
>
> Also xfstests' generic/062 test seems to fail (with USE_ATTR_SECURE=yes)
> ---cut---
> generic/062 1s ... - output mismatch (see
> /root/xfstests/results//generic/062.out.bad)
>      --- tests/generic/062.out   2015-08-18 20:13:00.714593141 +0000
>      +++ /root/xfstests/results//generic/062.out.bad     2015-08-18
> 20:50:06.450418217 +0000
>      @@ -203,6 +203,292 @@
>       SCRATCH_MNT/dev/p: user.name2: No such attribute or operation not permitted
>       *** final list (strings, type=dev/p, nsp=user)
>
>      +=== TYPE reg; NAMESPACE security
>      +
>      +*** set/get one initially empty attribute
>      +# file: SCRATCH_MNT/reg
>      ...
>      (Run 'diff -u tests/generic/062.out
> /root/xfstests/results//generic/062.out.bad'  to see the entire diff)
> Ran: generic/062
> Failures: generic/062
> Failed 1 of 1 tests

Hi Richard,
	Glad to know you are also using fstests for our ubifs. :)
About this case, I checked it and found it's a bug in fstests.
Because when we are setting USE_ATTR_SECURE=yes, the output
would be different with what it expected currently.
	So, I will send a patch out to fix it. And with a quick
fix, I found ubifs works well in xattr security.

Yang
> ---cut---
>
> Guys, how did you test this feature?
>

  parent reply	other threads:[~2015-08-20  0:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 12:15 [kernel.org bug 103071] Dead "security.*" xattr code in ubifs Andreas Grünbacher
2015-08-18 20:55 ` Richard Weinberger
2015-08-19  1:07   ` Sheng Yong
2015-08-19  1:37     ` Sheng Yong
2015-08-19  6:59       ` Richard Weinberger
2015-08-19  7:36         ` Sheng Yong
2015-08-19  7:51           ` Richard Weinberger
2015-08-20  9:32             ` Andreas Grünbacher
2015-08-20  0:50   ` Dongsheng Yang [this message]
2015-08-20  1:01     ` [PATCH] fstests: link .out to correct output when we set USE_ATTR_SECURE=yes Dongsheng Yang
2015-08-20  1:01       ` Dongsheng Yang
2015-08-20  6:18       ` Andreas Grünbacher
2015-08-20 21:08         ` Dave Chinner
2015-08-20 21:17           ` Andreas Grünbacher
2015-08-21  0:36           ` Dongsheng Yang
2015-08-21  0:36             ` Dongsheng Yang
2015-08-20  6:49     ` [kernel.org bug 103071] Dead "security.*" xattr code in ubifs Richard Weinberger

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=55D52473.7050209@cn.fujitsu.com \
    --to=yangds.fnst@cn.fujitsu.com \
    --cc=andreas.gruenbacher@gmail.com \
    --cc=ben.shelton@ni.com \
    --cc=brad.mouring@ni.com \
    --cc=dedekind1@gmail.com \
    --cc=gratian.crisan@ni.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mkl@pengutronix.de \
    --cc=richard.weinberger@gmail.com \
    --cc=snijsure@grid-net.com \
    --cc=terry.wilcox@ni.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.