[Bug 823797] New: Kernel Bug triggered by Soft Lockup when using mkfs.ext[2|3|4] to iscsi partition on EQLOGIC 100E-00
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c0 Summary: Kernel Bug triggered by Soft Lockup when using mkfs.ext[2|3|4] to iscsi partition on EQLOGIC 100E-00 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: andrew.holland@nordictelecom.fi QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36 With 64bit Kernel 3.7.10-1.11-default and open-iscsi 2.0.870-47.4.1, using the ext libraries 1.42.6-2.2.1, I trigger a kernel bug whenever I try to format a partition on our EQLOGIC 100E-00 device. This occurs whether the partition is on a GPT or a MS-Dos style partitioning scheme. The bug reported to the server debug console is: kernel:[ 148.953735] BUG: soft lockup - CPU#5 stuck for 22s! [mkfs.ext4:4631] * additional tests: Reiserfs and swap partitions are created without triggering the problem. The disk can be written to, and read, with dd, without triggering the problem. When a filesystem (reiserfs tested) is created, standard filesystem activities (create, append, delete, read) are as normal. I am unsure if the issue lies in the Kernel, open-iscsi, or the ext filesystem library/tools - it may be a combination of all. Reproducible: Always Steps to Reproduce: 1. Attach to iscsi device (using open-iscsi, CHAP authentication. - CHAP authentication requires custom, non-YAST editing of files. - in my case, the device is attached at boot. (config set to automatic, not manual.) 2. Create partition on device using parted. - To assure this occurs every time, I have gone as far as to write zeroes to the entire drive using dd, then created both a GPT and a MS-Dos partitioning scheme. 3. Attempt to format the partition via mkfs.ext[n] where n is 2, 3, or 4. - Occurs no matter which "version" is used. 4. Output will show: mkfs.ext4 /dev/sdc1 mke2fs 1.42.6 (21-Sep-2012) At this point, all output on the associated TTY stops until the Kernel Bug message appears: kernel:[ 148.953735] BUG: soft lockup - CPU#5 stuck for 22s! [mkfs.ext4:4631] * Additional info: - when using tmux or screen or other tty's, journald shows the following messages filling the log: Jun 07 11:25:38 mysql1.nordictele.com kernel: sdc1: rw=129, want=8384512, limit=1951744 Jun 07 11:25:38 mysql1.nordictele.com systemd-journal[379]: Missed 240 kernel messages Actual Results: System slows down as the logs fill with 'access beyond end of device' messages. Formatting process (mkfs.ext[2|3|4]) cannot be killed via control-c or "kill" Other tty's can be opened to perform actions/look at logs, but system eventually locks up. (I have not had a reboot occur; I have powercycled the machine to restore functionality each time.) Expected Results: Partition initialized with ext-style filesystem (and optional journal) System is 64 bit; Muti-core with 24 cores; - model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz results of 'free' command (showing memory:) total used free shared buffers cached Mem: 32967184 3625316 29341868 0 7572 1124664 -/+ buffers/cache: 2493080 30474104 Swap: 33551356 0 33551356 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c1 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@suse.com InfoProvider| |andrew.holland@nordicteleco | |m.fi --- Comment #1 from Jiri Slaby <jslaby@suse.com> 2013-06-24 09:01:00 UTC --- (In reply to comment #0)
At this point, all output on the associated TTY stops until the Kernel Bug message appears: kernel:[ 148.953735] BUG: soft lockup - CPU#5 stuck for 22s! [mkfs.ext4:4631]
Could you grab a photo of the whole report? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c2 Andrew Holland <andrew.holland@nordictelecom.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.holland@nordicteleco | |m.fi --- Comment #2 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-24 09:19:10 UTC --- I can't get a photo, for several reasons: #1. There is no physical display, so everything is over a serial console or network. #2. These spit out far too quickly to capture via a photograph. #3. The hardware in question has needed to be used for production, so unfortunately I can't test on that machine without affecting production. If you can work with a serial console log of the session, I can grab it during a downtime that I will schedule. That said, the information you'll get from it is all in the report above - you'll just have thousands upon thousands of lines of these: Jun 07 11:25:38 mysql1.nordictele.com kernel: sdc1: rw=129, want=8384512, limit=1951744 Jun 07 11:25:38 mysql1.nordictele.com systemd-journal[379]: Missed 240 kernel messages And a few of these, on a seperate tty: kernel:[ 148.953735] BUG: soft lockup - CPU#5 stuck for 22s! [mkfs.ext4:4631] They'll have different time offsets, of course. If the thousands of repeated items help, I'll schedule the maintenance window and grab the console log. Would you need any other info gathered at that time, or would you like any other tests run during the maintenance window? -- actually, systemd's journal would still probably have the logs and I can grab those instead. I will check and if I can retrieve them, I'll attach in a reply. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c3 --- Comment #3 from Jiri Slaby <jslaby@suse.com> 2013-06-24 09:29:59 UTC --- If the system is responsive, grabbind output of dmesg is perfect... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c4 Andrew Holland <andrew.holland@nordictelecom.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|andrew.holland@nordicteleco | |m.fi | --- Comment #4 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-24 10:20:05 UTC --- Created an attachment (id=545365) --> (http://bugzilla.novell.com/attachment.cgi?id=545365) xz compressed dmesg/systemd log of session Dmesg currently doesn't show the initial boot information - so here is a log that includes both dmesg and the entire journalctl stored info (standard journalctl options other than --no-pager ) File is compressed with xz -9, as it is somewhat large and contains a lot of repeated info; xzcat [file] | less or xz -dc [file] | less is probably the most effective way to view. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c5 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jack@suse.com --- Comment #5 from Jiri Slaby <jslaby@suse.com> 2013-06-24 12:51:19 UTC ---
sd 8:0:0:0: Attached scsi generic sg3 type 0 sd 8:0:0:0: [sdc] 2147512320 512-byte logical blocks: (1.09 TB/1.00 TiB) ... sdc1: rw=129, want=8384512, limit=2147508224 attempt to access beyond end of device sdc1: rw=129, want=18446744073709549568, limit=2147508224
Huh? Is this a bug in ext-utils? Honza, any ideas? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c6 --- Comment #6 from Jiri Slaby <jslaby@suse.com> 2013-06-24 12:52:23 UTC --- Created an attachment (id=545374) --> (http://bugzilla.novell.com/attachment.cgi?id=545374) dmesg in plaintext -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c7 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jack@suse.com InfoProvider|jack@suse.com |andrew.holland@nordicteleco | |m.fi --- Comment #7 from Jan Kara <jack@suse.com> 2013-06-24 15:12:48 UTC --- Umm, userspace shouldn't be able to trigger these messages. It is clear they come from mkfs.ext4 trying to discard the whole device (rw=129 is DISCARD command). Apparently something overflows in the discard handling code. Andrew, can you show here contents of: /sys/block/sdc/queue/discard_max_bytes /sys/block/sdc/queue/discard_granularity /sys/block/sdc/discard_alignment /sys/block/sdc/sdc1/discard_alignment /sys/block/sdc/sdc1/alignment_offset Thanks! Btw, workaround for this problem would be to disable discarding using "-E nodiscard" option for mke2fs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c8 Andrew Holland <andrew.holland@nordictelecom.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|andrew.holland@nordicteleco | |m.fi | --- Comment #8 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-25 03:21:50 UTC --- Interestingly, discard_max_bytes does not exist for /sys/block/sdc: mysql1:/home/andrew # cd /sys/block/sdc mysql1:/sys/block/sdc # du 0 ./sdc1/power 0 ./sdc1/trace 0 ./sdc1/holders 0 ./sdc1 0 ./power 0 ./queue/iosched 0 ./queue 0 ./trace 0 ./slaves 0 ./holders 0 . mysql1:/sys/block/sdc # cd queue mysql1:/sys/block/sdc/queue # ls -la total 0 drwxr-xr-x 3 root root 0 Jun 25 14:11 . drwxr-xr-x 8 root root 0 Jun 13 14:56 .. -rw-r--r-- 1 root root 4096 Jun 25 14:11 add_random -r--r--r-- 1 root root 4096 Jun 25 14:11 discard_granularity -r--r--r-- 1 root root 4096 Jun 25 14:11 discard_max_bytes -r--r--r-- 1 root root 4096 Jun 25 14:11 discard_zeroes_data -r--r--r-- 1 root root 4096 Jun 25 14:11 hw_sector_size drwxr-xr-x 2 root root 0 Jun 25 14:11 iosched -rw-r--r-- 1 root root 4096 Jun 25 14:11 iostats -r--r--r-- 1 root root 4096 Jun 25 14:11 logical_block_size -r--r--r-- 1 root root 4096 Jun 25 14:11 max_hw_sectors_kb -r--r--r-- 1 root root 4096 Jun 25 14:11 max_integrity_segments -rw-r--r-- 1 root root 4096 Jun 25 14:11 max_sectors_kb -r--r--r-- 1 root root 4096 Jun 25 14:11 max_segment_size -r--r--r-- 1 root root 4096 Jun 25 14:11 max_segments -r--r--r-- 1 root root 4096 Jun 25 14:11 minimum_io_size -rw-r--r-- 1 root root 4096 Jun 25 14:11 nomerges -rw-r--r-- 1 root root 4096 Jun 25 14:11 nr_requests -r--r--r-- 1 root root 4096 Jun 25 14:11 optimal_io_size -r--r--r-- 1 root root 4096 Jun 25 14:11 physical_block_size -rw-r--r-- 1 root root 4096 Jun 25 14:11 read_ahead_kb -rw-r--r-- 1 root root 4096 Jun 25 14:11 rotational -rw-r--r-- 1 root root 4096 Jun 25 14:11 rq_affinity -rw-r--r-- 1 root root 4096 Jun 25 14:11 scheduler -r--r--r-- 1 root root 4096 Jun 25 14:11 write_same_max_bytes - so there is no "discard_max_bytes" The remainder are: sdc/queue/discard_max_bytes: 15728640 sdc/discard_alignment: 0 sdc1/discard_alignment: 14680064 sdc1/alignment_offset: 0 --- mysql1:/sys/block/sdc/queue # cat discard_granularity 15728640 mysql1:/sys/block/sdc/queue # cd .. mysql1:/sys/block/sdc # cat discard_alignment 0 mysql1:/sys/block/sdc/sdc1 # cat discard_alignment 14680064 mysql1:/sys/block/sdc/sdc1 # cat alignment_offset 0 --- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c9 --- Comment #9 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-25 03:29:15 UTC --- Now that's interesting, it was not there a second ago, but when looking at the journalctl log, I noticed this: Jun 25 14:22:02 mysql1.nordictele.com kernel: FAT-fs (sdc1): bogus number of reserved sectors Then, looking at my submission, it definately shows discard_max_bytes. (It is POSSIBLE I first tried this without root, so I'll assume "user error" here.) sdc/queue/discard_max_bytes: 15728640 sdc/queue/discard_granularity: 15728640 sdc/discard_alignment: 0 sdc1/discard_alignment: 14680064 sdc1/alignment_offset: 0 --- mysql1:/sys/block/sdc/queue # cat discard_max_bytes 15728640 mysql1:/sys/block/sdc/queue # cat discard_granularity 15728640 mysql1:/sys/block/sdc/queue # cd .. mysql1:/sys/block/sdc # cat discard_alignment 0 mysql1:/sys/block/sdc/sdc1 # cat discard_alignment 14680064 mysql1:/sys/block/sdc/sdc1 # cat alignment_offset 0 --- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c10 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jack@suse.com |ovo.novell.com | --- Comment #10 from Jan Kara <jack@suse.com> 2013-06-25 03:49:55 UTC --- Yeah, ok, the values explain the problem. 'discard_granularity' isn't a power of two so the logic and masking in blkdev_issue_discard() starts giving random numbers and eventually tries to trim negative number of blocks which has fancy results. Looking into the upstream code, the problem seems to be fixed there by commit 8dd2cb7e880d2f77fba53b523c99133ad5054cfd. I'll port the patch to our kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c11 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |andrew.holland@nordicteleco | |m.fi --- Comment #11 from Jan Kara <jack@suse.com> 2013-06-25 03:56:35 UTC --- OK, the fix is pushed to openSUSE 12.3 branch (BTW I've checked and SLES11 SP3 branch already has the fix). If you can test the kernel from http://download.opensuse.org/repositories/Kernel:/openSUSE-12.3/standard/ tomorrow (there are daily builds of our kernel tree), it would be nice. Otherwise I'll just close the bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c12 --- Comment #12 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-25 04:07:14 UTC --- I can test starting at Midnight Helsinki time - would that be too early? (What time zone is used for builds - CET? UTC? MDT?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c13 --- Comment #13 from Jiri Slaby <jslaby@suse.com> 2013-06-25 04:34:46 UTC --- (In reply to comment #12)
I can test starting at Midnight Helsinki time - would that be too early?
(What time zone is used for builds - CET? UTC? MDT?)
Around 2 am CET IIRC. You can always check the changelog, it has to contain "block: discard granularity might not be power of 2." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c14 --- Comment #14 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-26 02:43:40 UTC --- I'm sorry, I just cannot find an rpm package that is not built from the 13th of this month in that location, or on the kernel.opensuse.org site, for x86_64. The kernel from the 13th still has the issue (as expected.) I see the patch, and I may just compile it myself to test. I'll keep looking for a package in the meanwhile. Aha - I see one at https://build.opensuse.org/package/binary?arch=x86_64&filename=kernel-defaul... built an hour ago. I shall attempt to test that package. (I've repurposed the machine for testing today.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c15 --- Comment #15 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-26 02:57:56 UTC --- I'm horribly sorry, that is also a false trail. All I find are the kernel-default-3.7.10-33.1.gcfcec53.x86_64.rpm anywhere, which does not have the patch applied. I will build from the git sources provided and report back. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c16 --- Comment #16 from Jiri Slaby <jslaby@suse.com> 2013-06-26 03:04:08 UTC --- It's not built yet... https://build.opensuse.org/project/monitor?project=Kernel%3AopenSUSE-12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c17 --- Comment #17 from Jiri Slaby <jslaby@suse.com> 2013-06-26 03:05:21 UTC --- (In reply to comment #16)
It's not built yet...
Better phrased as "not published yet". https://api.opensuse.org/build/Kernel:openSUSE-12.3/standard/x86_64/kernel-d... should work if you have an OBS account... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c18 Andrew Holland <andrew.holland@nordictelecom.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|andrew.holland@nordicteleco | |m.fi | --- Comment #18 from Andrew Holland <andrew.holland@nordictelecom.fi> 2013-06-26 05:04:26 UTC --- I am happy to say this patch has solved the issue. (As did the workaround, but I didn't want to leave this in a state where if I went on vacation or similar, someone else might bring the box to it's knees by using a standard mkfs command.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c19 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #19 from Jan Kara <jack@suse.com> 2013-06-26 07:52:35 UTC --- Thanks for testing. So I'm closing the bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |obs:running:2034:moderate -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=823797 https://bugzilla.novell.com/show_bug.cgi?id=823797#c20 --- Comment #20 from Swamp Workflow Management <swamp@suse.de> 2013-12-30 20:14:33 UTC --- openSUSE-SU-2013:1971-1: An update that solves 34 vulnerabilities and has 19 fixes is now available. Category: security (moderate) Bug References: 799516,801341,802347,804198,807153,807188,807471,808827,809906,810144,810473,811882,812116,813733,813889,814211,814336,814510,815256,815320,816668,816708,817651,818053,818561,821612,821735,822575,822579,823267,823342,823517,823633,823797,824171,824295,826102,826350,826374,827749,827750,828119,828191,828714,829539,831058,831956,832615,833321,833585,834647,837258,838346 CVE References: CVE-2013-0914,CVE-2013-1059,CVE-2013-1819,CVE-2013-1929,CVE-2013-1979,CVE-2013-2141,CVE-2013-2148,CVE-2013-2164,CVE-2013-2206,CVE-2013-2232,CVE-2013-2234,CVE-2013-2237,CVE-2013-2546,CVE-2013-2547,CVE-2013-2548,CVE-2013-2634,CVE-2013-2635,CVE-2013-2851,CVE-2013-2852,CVE-2013-3222,CVE-2013-3223,CVE-2013-3224,CVE-2013-3226,CVE-2013-3227,CVE-2013-3228,CVE-2013-3229,CVE-2013-3230,CVE-2013-3231,CVE-2013-3232,CVE-2013-3233,CVE-2013-3234,CVE-2013-3235,CVE-2013-3301,CVE-2013-4162 Sources used: openSUSE 12.3 (src): kernel-docs-3.7.10-1.24.1, kernel-source-3.7.10-1.24.1, kernel-syms-3.7.10-1.24.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=823797 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:2034:moderate | -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com