Skip to content

L
linux-davinci
Switch branch/tag
  1. 30 Jul, 2009 1 commit
    • Paul Menage's avatar
      To simplify referring to cgroup hierarchies in mount statements, and to · e2a666dd
      Paul Menage authored 
      allow disambiguation in the presence of empty hierarchies and
multiply-bindable subsystems this patch adds support for naming a new
cgroup hierarchy via the "name=" mount option

A pre-existing hierarchy may be specified by either name or by subsystems;
a hierarchy's name cannot be changed by a remount operation.

Example usage:

# To create a hierarchy called "foo" containing the "cpu" subsystem
mount -t cgroup -oname=foo,cpu cgroup /mnt/cgroup1

# To mount the "foo" hierarchy on a second location
mount -t cgroup -oname=foo cgroup /mnt/cgroup2
Signed-off-by: default avatarPaul Menage <menage@google.com>
Reviewed-by: default avatarLi Zefan <lizf@cn.fujitsu.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Balbir Singh <balbir@in.ibm.com>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      e2a666dd
  3. 24 Jul, 2009 1 commit
  5. 09 Sep, 2009 2 commits
  7. 18 Aug, 2009 1 commit
  9. 14 Aug, 2009 1 commit
  11. 04 Aug, 2009 1 commit
  13. 31 Jul, 2009 3 commits
  15. 24 Aug, 2009 1 commit
    • Zhaolei's avatar
      There are many similar code in kernel for one object: convert time between · 6b2d640d
      Zhaolei authored 
      calendar time and broken-down time.

Here is some source I found:
fs/ncpfs/dir.c
fs/smbfs/proc.c
fs/fat/misc.c
fs/udf/udftime.c
fs/cifs/netmisc.c
net/netfilter/xt_time.c
drivers/scsi/ips.c
drivers/input/misc/hp_sdc_rtc.c
drivers/rtc/rtc-lib.c
arch/ia64/hp/sim/boot/fw-emu.c
arch/m68k/mac/misc.c
arch/powerpc/kernel/time.c
arch/parisc/include/asm/rtc.h
...

We can make a common function for this type of conversoion, At least we
can get following benefit:

1: Make kernel simple and unify
2: Easy to fix bug in converting code
3: Reduce clone of code in future
   For example, I'm trying to make ftrace display walltime,
   this patch will make me easy.

This code is based on code from glibc-2.6
Signed-off-by: default avatarZhao Lei <zhaolei@cn.fujitsu.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Pavel Machek <pavel@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      6b2d640d
  17. 27 Aug, 2009 2 commits
  19. 13 Jul, 2009 1 commit
  21. 21 Nov, 2008 1 commit
    • Warren Turkal's avatar
      This is a patchset to change the way that the HFS+ filesystem detects · 8458ca39
      Warren Turkal authored 
      whether a volume has a journal or not.

The code currently mounts an HFS+ volume read-only by default when a
journal is detected.  One can force a read/write mount by giving the
"force" mount option.  The current code has this behavior since there is
no support for the HFS+ journal.

My problem is that the detection of the journal could be better.  The
current code tests the attribute bit in the volume header that indicates
there is a journal.  If that bit is set, the code assumes that there is a
journal.

Unfortunately, this is not enough to really determine if there is a
journal or not.  When that bit is set, one must also examine the journal
info block field of the volume header.  If this field is 0, there is no
journal, and the volume can be mounted read/write.


This patch:

The HFS+ support in the kernel currently will mount an HFS+ volume
read-only if the volume header has the attribute bit set that indicates
there is a journal.  The kernel does this because there is no support for
a journalled HFS+ volume.

The problem is that this is only half of what needs to be checked to see
if there really is a journal.  There is also an entry in the volume header
that tells you where to find the journal info block.  In the kernel
version of the kernel, this 4 byte block is labeled reserved.  This patch
identifies the journal info block in the header.
Signed-off-by: default avatarWarren Turkal <wt@penguintechs.org>
Cc: Roman Zippel <zippel@linux-m68k.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      8458ca39
  23. 17 Aug, 2009 1 commit
  25. 05 Sep, 2009 1 commit
  27. 18 Jul, 2009 2 commits
    • Andrew Morton's avatar
      ERROR: "(foo*)" should be "(foo *)" · 0d2b07f8
      Andrew Morton authored 
      #62: FILE: fs/minix/dir.c:481:
+		struct inode *inode = (struct inode*)mapping->host;

total: 1 errors, 0 warnings, 46 lines checked

./patches/v3-minixfs-add-missing-directory-type-checking.patch has style problems, please review.  If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.

Please run checkpatch prior to sending patches

Cc: "Doug Graham" <dgraham@nortel.com>
Cc: Doug Graham <dgraham@nortel.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      0d2b07f8
    • Doug Graham's avatar
      There are a few places in the Minix FS code where the "inode" field of a · 9b9bd540
      Doug Graham authored 
      minix_dir_entry is used without checking first to see if the dirent is
really a minix3_dir_entry.  The inode number in a V1/V2 dirent is 16 bits,
whereas that in a V3 dirent is 32 bits.

Accessing it as a 16 bit field when it really should be accessed as a 32
bit field probably kinda sorta works on a little-endian machine, but leads
to some rather odd behaviour on big-endian machines.
Signed-off-by: default avatarDoug Graham <dgraham@nortel.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      9b9bd540
  29. 13 Jul, 2009 1 commit
  31. 03 Sep, 2009 5 commits
  33. 22 Aug, 2009 1 commit
    • Florian Tobias Schandinat's avatar
      At the moment about half of the framebuffer drivers can return an error · 713370f1
      Florian Tobias Schandinat authored 
      code in fb_set_par. Until now it would be silently ignored by fbmem.c
and fbcon.c. This patch fixes fbmem.c to return the error code and
restore var on error.

But it is not clear in which video mode the device is when fb_set_par
fails.  It would be good and reasonable if it were in the old state but
there is no guarantee that this is true for all existing drivers. 
Additionally print a message if a failing fb_set_par is detected in
fbmem.c or fbcon.c.

Although most errors should be caught by the previous fb_check_var some
errors can't as they are dynamic (memory allocations, ...) and can only be
detected while performing the operations which is forbidden in
fb_check_var.

This patch shouldn't have a negative impact on normal operation as all
drivers return 0 on success.  The impact in case of error depends heavily
on the driver and caller but it's expected to be better than before.
Signed-off-by: default avatarFlorian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: Krzysztof Helt <krzysztof.h1@poczta.fm>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      713370f1
  35. 20 Aug, 2009 2 commits
  37. 06 Aug, 2009 1 commit
  39. 03 Aug, 2009 2 commits
  41. 31 Jul, 2009 1 commit
  43. 09 Sep, 2009 7 commits
  45. 05 Sep, 2009 1 commit