From: Manu Abraham <abraham.manu@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
robfitz@273k.net, video4linux-list@redhat.com,
76306.1226@compuserve.com, fork0@t-online.de, greg@kroah.com,
linux-kernel@vger.kernel.org, rdunlap@xenotime.net,
v4l-dvb-maintainer@linuxtv.org, shemminger@osdl.org
Subject: Re: [v4l-dvb-maintainer] Re: [PATCH] V4L: struct video_device corruption
Date: Tue, 25 Jul 2006 11:57:11 +0400 [thread overview]
Message-ID: <44C5CED7.4000801@gmail.com> (raw)
In-Reply-To: <20060724200855.603be3bb.akpm@osdl.org>
Andrew Morton wrote:
> On Sat, 15 Jul 2006 22:31:04 -0300
> Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
>
>> Em Sáb, 2006-07-15 às 23:08 +0000, Robert Fitzsimons escreveu:
>>> The layout of struct video_device would change depending on whether
>>> videodev.h (V4L1) was include or not before v4l2-dev.h, which caused
>>> the structure to get corrupted.
>> Hmm... good point! However, I the proper solution would be to trust on
>> CONFIG_VIDEO_V4L1_COMPAT or CONFIG_VIDEO_V4L1 instead. it makes no sense
>> to keep a pointer to an unsupported callback, when V4L1 is not selected.
>>
>
> So I've lost the plot with all of this. Does the current git-dvb contain
> the desired fixes?
>
> Do we expect this will fix the various DVB crashes which people (including
> Alex) have reported?
I believe you are referring to the "oops in bttv" thread.
As i understood, the case that Alex reported in was a null pointer issue
due to which modprobe bttv crashes, rather than a DVB issue.
Call Trace:
[<c018763c>] sysfs_create_file+0x26/0x28
[<c0220cc3>] class_device_create_file+0x14/0x1a
[<f9bc3073>] bttv_register_video+0x8c/0x147 [bttv]
[<f9bc35de>] bttv_probe+0x4ab/0x593 [bttv]
Therefore the V4L fixes should probably fix the same as well.
Regards,
Manu
next prev parent reply other threads:[~2006-07-25 7:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 4:43 oops in bttv Chuck Ebbert
2006-07-13 5:05 ` Greg KH
2006-07-13 5:24 ` Randy.Dunlap
2006-07-13 5:44 ` Andrew Morton
2006-07-15 23:08 ` [PATCH] V4L: struct video_device corruption Robert Fitzsimons
2006-07-16 1:31 ` Mauro Carvalho Chehab
2006-07-18 0:25 ` [v4l-dvb-maintainer] " Trent Piepho
2006-07-19 11:54 ` Mauro Carvalho Chehab
2006-07-19 15:36 ` Michael Krufky
2006-07-20 21:57 ` Trent Piepho
2006-07-21 12:26 ` Mauro Carvalho Chehab
2006-07-21 20:06 ` Trent Piepho
2006-07-21 20:30 ` Mauro Carvalho Chehab
2006-07-21 22:55 ` Trent Piepho
2006-07-23 9:35 ` Mauro Carvalho Chehab
2006-07-24 2:16 ` Trent Piepho
2006-07-24 12:34 ` Mauro Carvalho Chehab
2006-07-24 22:06 ` Trent Piepho
2006-07-25 17:59 ` Mauro Carvalho Chehab
2006-07-25 3:08 ` Andrew Morton
2006-07-25 7:57 ` Manu Abraham [this message]
2006-07-25 8:42 ` [v4l-dvb-maintainer] " Trent Piepho
2006-07-25 9:06 ` Andrew Morton
2006-07-25 12:28 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C5CED7.4000801@gmail.com \
--to=abraham.manu@gmail.com \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=fork0@t-online.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rdunlap@xenotime.net \
--cc=robfitz@273k.net \
--cc=shemminger@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).