1. 16 Jun, 2009 4 commits
    • Alan Cox's avatar
      pty: Narrow the race on ldisc locking · cbcb6d66
      Alan Cox authored
      The pty code has always been buggy on its ldisc handling. The recent
      changes made the window for the race much bigger. Pending fixing it
      properly which is not at all trivial, at least make the race small again so
      we don't disrupt other dev work.
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      cbcb6d66
    • Linus Torvalds's avatar
      printk: add KERN_DEFAULT loglevel to print_modules() · b231125a
      Linus Torvalds authored
      Several WARN_ON() messages omit the '\n' at the end of the string, which
      is a simple (and understandable) error.  The next line printed after
      that warning line is usually the current module list, and that printk
      does not have a log-level marker - resulting in one long mixed-up line.
      
      Adding this loglevel marker will now avoid this unreadable mess.
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      b231125a
    • Linus Torvalds's avatar
      printk: Add KERN_DEFAULT printk log-level · e28d7137
      Linus Torvalds authored
      This adds a KERN_DEFAULT loglevel marker, for when you cannot decide
      which loglevel you want, and just want to keep an existing printk
      with the default loglevel.
      
      The difference between having KERN_DEFAULT and having no log-level
      marker at all is two-fold:
      
       - having the log-level marker will now force a new-line if the
         previous printout had not added one (perhaps because it forgot,
         but perhaps because it expected a continuation)
      
       - having a log-level marker is required if you are printing out a
         message that otherwise itself could perhaps otherwise be mistaken
         for a log-level.
      Signed-of-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      e28d7137
    • Linus Torvalds's avatar
      printk: clean up handling of log-levels and newlines · 5fd29d6c
      Linus Torvalds authored
      It used to be that we would only look at the log-level in a printk()
      after explicit newlines, which can cause annoying problems when the
      previous printk() did not end with a '\n'. In that case, the log-level
      marker would be just printed out in the middle of the line, and be
      seen as just noise rather than change the logging level.
      
      This changes things to always look at the log-level in the first
      bytes of the printout. If a log level marker is found, it is always
      used as the log-level. Additionally, if no newline existed, one is
      added (unless the log-level is the explicit KERN_CONT marker, to
      explicitly show that it's a continuation of a previous line).
      Acked-by: default avatarArjan van de Ven <arjan@infradead.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      5fd29d6c
  2. 15 Jun, 2009 25 commits
  3. 14 Jun, 2009 11 commits