print_string: Validate tty before accessing its operations

Close #81

diff --git a/examples/print_string.c b/examples/print_string.c
index 5a70e2f005b75b5ed78a647e1412b9897453ca82..82181257615817d3de9172abe7087aa47ed4e25a 100644 (file)
--- a/examples/print_string.c
+++ b/examples/print_string.c
@@ -11,17 +11,14 @@
 
 static void print_string(char *str)
 {
-    struct tty_struct *my_tty;
-    const struct tty_operations *ttyops;
-
-    /* The tty for the current task, for 2.6.6+ kernels */
-    my_tty = get_current_tty();
-    ttyops = my_tty->driver->ops;
+    /* The tty for the current task */
+    struct tty_struct *my_tty = get_current_tty();
 
     /* If my_tty is NULL, the current task has no tty you can print to (i.e.,
      * if it is a daemon). If so, there is nothing we can do.
      */
     if (my_tty) {
+        const struct tty_operations *ttyops = my_tty->driver->ops;
         /* my_tty->driver is a struct which holds the tty's functions,
          * one of which (write) is used to write strings to the tty.
          * It can be used to take a string either from the user's or