From: Panadero Pizza <panadero_pizza@yahoo•es>
To: netdev@vger•kernel.org
Subject: Putting for discussion "__qdisc_run" bug - strange application-dependant error
Date: Sat, 9 May 2009 19:55:04 +0000 (GMT) [thread overview]
Message-ID: <657221.87331.qm@web28608.mail.ukl.yahoo.com> (raw)
Hello netdev group,
I would like to put for discussion, if a bug in the __qdsic_run function could explain the problem I have described in my post "Kernel networking problem (>=2.6.24.7)" two days ago.
"__qdisc_run" is the last common function in the kernel traces I receive for the kernels:
2.6.24.7
2.6.27.12
with a multi-threaded software, using fputc, putc, puts - calls, mixed with fflush()-calls on a remote file, opened on a cifs-handle. (Errors occur extremely seldom, although the software is running for hours - day after day)
I don't receive the error with other standard software (e.g. "dd"), writing to a file on the same cifs-handle/session and more interesting:
The error does not occur with the afore-mentioned multi-threaded program (or any other software), using a
2.6.16.62
kernel.
I have found that from 2.6.24.x on, the __qdisc_run function has been made preemptible and this feature has been enabled for the realization of the afore-said 2.6.24.7 and 2.6.27.12 kernels.
Though 2.6.16.62 solves my problem, I am offering participation in finding a solution for this (which should be fixed, if it is a kernel bug).
Best regards,
David
next reply other threads:[~2009-05-09 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 19:55 Panadero Pizza [this message]
2009-05-10 7:33 ` Putting for discussion "__qdisc_run" bug - strange application-dependant error Jarek Poplawski
2009-05-10 11:54 ` Jarek Poplawski
2009-05-11 11:33 ` Panadero Pizza
2009-05-11 16:34 ` Jarek Poplawski
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=657221.87331.qm@web28608.mail.ukl.yahoo.com \
--to=panadero_pizza@yahoo$(echo .)es \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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