linux-dev/fs/jffs2/README.Locking, branch master

jffs2: Fix page lock / f->sem deadlock

2016-02-25T11:11:26Z

With this fix, all code paths should now be obtaining the page lock before f->sem. Reported-by: Szabó Tamás Tested-by: Thomas Betker Signed-off-by: David Woodhouse Cc: stable@vger.kernel.org

[JFFS2] semaphore->mutex conversion

2008-04-22T14:13:40Z

Signed-off-by: David Woodhouse

[JFFS2] Tidy up licensing/copyright boilerplate.

2007-04-25T13:16:47Z

In particular, remove the bit in the LICENCE file about contacting Red Hat for alternative arrangements. Their errant IS department broke that arrangement a long time ago -- the policy of collecting copyright assignments from contributors came to an end when the plug was pulled on the servers hosting the project, without notice or reason. We do still dual-license it for use with eCos, with the GPL+exception licence approved by the FSF as being GPL-compatible. It's just that nobody has the right to license it differently. Signed-off-by: David Woodhouse

[JFFS2][XATTR] Add a description about c->xattr_sem

2006-05-13T06:14:14Z

Add a description about the c->xattr_sem read/write semaphore into README.Locking. [3/10] jffs2-xattr-v5.1-03-append_README.Locking.patch Signed-off-by: KaiGai Kohei

[JFFS2] Fix inode allocation race

2005-05-23T11:17:49Z

Signed-off-by: David Woodhouse Signed-off-by: Thomas Gleixner

Linux-2.6.12-rc2

2005-04-16T22:20:36Z

Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!