<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/ubifs/debug.c, branch linux-3.6.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.6.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.6.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-07-20T07:27:25Z</updated>
<entry>
<title>UBIFS: add debugfs knob to switch to R/O mode</title>
<updated>2012-07-20T07:27:25Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-07-14T11:19:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=06bef9451a4c5ad882cd15fd7a0df9890c0249f3'/>
<id>urn:sha1:06bef9451a4c5ad882cd15fd7a0df9890c0249f3</id>
<content type='text'>
This patch adds another debugfs knob which switches UBIFS to R/O mode.
I needed it while trying to reproduce the 'first log node is not CS node'
bug. Without this debugfs knob you have to perform a power cut to repruduce
the bug. The knob is named 'ro_error' and all it does is it sets the
'ro_error' UBIFS flag which makes UBIFS disallow any further writes - even
write-back will fail with -EROFS. Useful for debugging.

Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: correct usage of IS_ENABLED()</title>
<updated>2012-06-27T11:22:15Z</updated>
<author>
<name>Brian Norris</name>
</author>
<published>2012-06-18T23:31:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2d4cf5ae123e4a7bd26a88e600581aa809bcad7f'/>
<id>urn:sha1:2d4cf5ae123e4a7bd26a88e600581aa809bcad7f</id>
<content type='text'>
Commit "818039c UBIFS: fix debugfs-less systems support" fixed one
regression but introduced a different regression - the debugfs is now always
compiled out. Root cause: IS_ENABLED() arguments should be used with the
CONFIG_* prefix.

Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: fix debugfs-less systems support</title>
<updated>2012-06-07T07:43:54Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-06-06T13:03:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=818039c7d597db3b1d30964a8f9489ac42c0642d'/>
<id>urn:sha1:818039c7d597db3b1d30964a8f9489ac42c0642d</id>
<content type='text'>
Commit "f70b7e5 UBIFS: remove Kconfig debugging option" broke UBIFS and it
refuses to initialize if debugfs (CONFIG_DEBUG_FS) is disabled. I incorrectly
assumed that debugfs files creation function will return success if debugfs
is disabled, but they actually return -ENODEV. This patch fixes the issue.

Reported-by: Paul Parsons &lt;lost.distance@yahoo.com&gt;
Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
Tested-by: Paul Parsons &lt;lost.distance@yahoo.com&gt;
</content>
</entry>
<entry>
<title>UBI: Kill data type hint</title>
<updated>2012-05-20T17:25:59Z</updated>
<author>
<name>Richard Weinberger</name>
</author>
<published>2012-05-14T15:55:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b36a261e8c0ab323d04db9cdd1f6bb4c273c4b32'/>
<id>urn:sha1:b36a261e8c0ab323d04db9cdd1f6bb4c273c4b32</id>
<content type='text'>
We do not need this feature and to our shame it even was not working
and there was a bug found very recently.
	-- Artem Bityutskiy

Without the data type hint UBI2 (fastmap) will be easier to implement.

Signed-off-by: Richard Weinberger &lt;richard@nod.at&gt;
Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: get rid of dbg_err</title>
<updated>2012-05-16T17:11:23Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-05-16T17:11:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a6aae4dd0ffad299a33d122f8a339b399bee5381'/>
<id>urn:sha1:a6aae4dd0ffad299a33d122f8a339b399bee5381</id>
<content type='text'>
This patch removes the 'dbg_err()' macro and we now use 'ubifs_err()' instead.
The idea of 'dbg_err()' was to compile out some error message to make the
binary a bit smaller - but I think it was a bad idea.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: remove Kconfig debugging option</title>
<updated>2012-05-16T16:53:46Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-05-16T16:53:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f70b7e52aa23c9aea5346b9730b402fb55f9079b'/>
<id>urn:sha1:f70b7e52aa23c9aea5346b9730b402fb55f9079b</id>
<content type='text'>
Have the debugging stuff always compiled-in instead. It simplifies maintanance
a lot.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: rename dumping functions</title>
<updated>2012-05-16T16:15:56Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-05-16T16:15:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=edf6be245fd34a4438646375cecb11f5feb92646'/>
<id>urn:sha1:edf6be245fd34a4438646375cecb11f5feb92646</id>
<content type='text'>
This commit re-names all functions which dump something from "dbg_dump_*()" to
"ubifs_dump_*()". This is done for consistency with UBI and because this way it
will be more logical once we remove the debugging sompilation option.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: get rid of dbg_dump_stack</title>
<updated>2012-05-16T16:04:54Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-05-16T16:04:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7c46d0ae29ba880963db283706950de7aa86c0a0'/>
<id>urn:sha1:7c46d0ae29ba880963db283706950de7aa86c0a0</id>
<content type='text'>
In case of errors we almost always need the stack dump - it makes no sense
to compile it out. Remove the 'dbg_dump_stack()' function completely.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: make the dbg_lock spinlock static</title>
<updated>2012-02-29T14:10:20Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-01-18T14:06:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b06283c7df35b5a49ab141ed38e0280821379096'/>
<id>urn:sha1:b06283c7df35b5a49ab141ed38e0280821379096</id>
<content type='text'>
Remove the usage of the 'dbg_lock' spinlock from 'dbg_err()' and make
it static.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>UBIFS: increase dumps loglevel</title>
<updated>2012-02-29T14:10:20Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-01-18T13:46:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=16c395ca72a79115653892c0724d4928f72520fe'/>
<id>urn:sha1:16c395ca72a79115653892c0724d4928f72520fe</id>
<content type='text'>
Most of the time we use the dumping function to dump something in case
of error. We use 'KERN_DEBUG' printk level, and the drawback is that users
do not see them in the console, while they see the other error messages
in the console. The result is that they send bug reports which does not
contain a lot of useful information. This patch changes the printk level
of the dump functions to 'KERN_ERR' to correct the situation.

I documented it in the MTD web site that people have to send the 'dmesg' output
when submitting bug reposts - it did not help.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
</content>
</entry>
</feed>
