All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Dongsheng Yang" <yangds.fnst@cn.fujitsu.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:49:08 +0200	[thread overview]
Message-ID: <55D57864.7060404@nod.at> (raw)
In-Reply-To: <55D52473.7050209@cn.fujitsu.com>

Am 20.08.2015 um 02:50 schrieb Dongsheng Yang:
> 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.

Yeah, I'm extending my testbed to use xfstests too. :)
I'm sure these tests will uncover some UBIFS issues.

> 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.

Oh. Good find!

Thanks,
//richard

      parent reply	other threads:[~2015-08-20  6:49 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
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     ` Richard Weinberger [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=55D57864.7060404@nod.at \
    --to=richard@nod.at \
    --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=snijsure@grid-net.com \
    --cc=terry.wilcox@ni.com \
    --cc=yangds.fnst@cn.fujitsu.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.